Skip to main content

AS48596

INWX

InterNetworX Management GmbH

Registry

Authoritative registration data

AS number
48596
Name
INWX
Organisation
InterNetworX Management GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

4

Total announced

7

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS48596
185.181.104.0/22 IPv4 /22 not checked
45.87.156.0/23 IPv4 /23 not checked
45.87.158.0/23 IPv4 /23 not checked
2a02:d500::/29 IPv6 /29 not checked
2a0a:c980::/29 IPv6 /29 not checked
2a0a:c986:be01::/48 IPv6 /48 RPKI valid
2a0a:c986:be02::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS48596
Address families
BCIX: BCIX Peering LAN 2,000 Mbps IPv4 · IPv6
NL-ix: Main 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS48596 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS48596 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 131 655
v4 v6
AS9136 WOBCOM 117 270
v4 v6
AS39614 DAWICO 53 119
v4 v6
AS20562 OPEN-PEERING-AS 26 49
v4 v6
AS24785 JOINTTRANSIT-AS 7 14
v4 v6
AS8218 NEO-ASN 3 14
v4 v6
AS29632 NASSIST-AS 2 6
v6
AS39351 ESAB-AS 1 5
v4 v6
AS6204 ZET-NET 1 2
v4
AS20485 TRANSTELECOM 1 2
v4
AS37100 ORG-SL75-AFRINIC 1 2
v4
AS37468 ORG-AC4-AFRINIC 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS48596 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

16 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.