Skip to main content

AS31561

NINE-IX

-----------------------------------------------------

Registry

Authoritative registration data

AS number
31561
Name
NINE-IX
Organisation
-----------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS31561
Address families
nine 110,000 Mbps IPv4 · IPv6
nine - six in Paris 110,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 AS31561 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

0 networks seen before AS31561 in AS paths

No upstreams observed

No network was seen carrying traffic towards this AS.

Observed downstreams

10 networks seen after AS31561 in AS paths

Observed downstreams
Families
AS3399 OBE-NET 5 120
v4
AS201333 NAQUADRIA-AS 2 24
v4
AS208437 HYPERBIT-AS 2 8
v4
AS6517 LAKENETWORKS-AS 6 7
v4 v6
AS56488 EISIT 1 4
v4 v6
AS212895 ROUTE64_ORG 2 3
v4 v6
AS219092 1 3
v4 v6
AS207530 TIMOSCHAFFERT 1 1
v4
AS216198 ORG-LZY1-RIPE 1 1
v6
AS218569 PODRIL1AK2-AS 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS209823 ENKI-AS 22 172
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.