asn.dev

Observed topology

AS31221 NLT-

Unclassified RIPE

Upstreams 3 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 2
Upstream graph Who carries AS31221, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS31221 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31221: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6213
AS8218Zayo Infrastructure France SAUnclassifiedIPv4182
AS3356Level 3 Parent, LLCTransitIPv4 IPv6126

Transit

Downstream networks

inferred

Networks for which AS31221 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS209468nLighten France SASUnclassifiedIPv462
AS51269HEXATOM s.a.r.l.UnclassifiedIPv461
AS205939LNW Gaming and Systems FranceUnclassifiedIPv461
AS207100SOLUSQUARE SASUnclassifiedIPv461
AS210255Strong Blue Conseil & Telecom SASUUnclassifiedIPv436

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS31221 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6375
AS8218Zayo Infrastructure France SAUnclassifiedIPv4268
AS3356Level 3 Parent, LLCTransitIPv4 IPv6179
AS209468nLighten France SASUnclassifiedIPv482
AS51269HEXATOM s.a.r.l.UnclassifiedIPv461
AS205939LNW Gaming and Systems FranceUnclassifiedIPv461
AS207100SOLUSQUARE SASUnclassifiedIPv461
AS210255Strong Blue Conseil & Telecom SASUUnclassifiedIPv436

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.22M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.