Skip to main content

AS41157

NINE-IX-BACKBONE-ASN-L3-EDGE-CACHE

=== UPSTREAMS ===

Registry

Authoritative registration data

AS number
41157
Name
NINE-IX-BACKBONE-ASN-L3-EDGE-CACHE
Organisation
=== UPSTREAMS ===
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS41157
81.201.178.0/24 IPv4 /24 not checked
2a0f:3400:500::/40 IPv6 /40 not checked

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 AS41157
Address families
nine 400,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 AS41157 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS41157 in AS paths

Observed upstreams
Families
AS62000 AS62000 512 862
v4 v6
AS6939 HURRICANE 120 164
v4 v6
AS25091 IP-Max 3 10
v4 v6
AS6204 ZET-NET 1 1
v4
AS6696 VERIXI 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS41157 in AS paths

Observed downstreams
Families
AS31128 SHAZAM-AS 263 354
v6

No rows match “”.

Showing – of

Uncertain adjacencies

10 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS34019 HIVANE 2 9
v4 v6
AS8529 OMANTEL-AS 2 6
v4 v6
AS2027 MilkyWan 2 3
v4 v6
AS3399 OBE-NET 2 3
v4 v6
AS35600 ASN-VEDEGE 2 3
v4 v6
AS44097 AUTONOMOUS-CLOSET 2 3
v4 v6
AS49434 FBWNETWORKS 2 3
v4 v6
AS56987 AS-ABACLOUDA 2 3
v4 v6
AS204092 GRIFON 2 3
v4 v6
AS16347 INHERENT 1 2
v4 v6

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.