asn.dev

Observed topology

AS31029 M-REAL

Unclassified RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS31029: 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
AS57344Telehouse EADResidentialIPv4440
AS1299Arelion Sweden ABTransitIPv4 IPv6143
AS6939Hurricane Electric LLCTransitIPv4120
AS9002RETN LimitedUnclassifiedIPv4 IPv6104
AS3356Level 3 Parent, LLCTransitIPv4 IPv6101
AS1273IDDQD-ASBusinessIPv480
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv641
AS3257GTT Communications Inc.TransitIPv440
AS24482SG.GSHostingIPv4 IPv621
AS34019Hivane AssociationUnclassifiedIPv4 IPv621

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20750NetLan Ltd.UnclassifiedIPv4175
AS203312Global Pharma Centre JSCUnclassifiedIPv451

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS57344Telehouse EADResidentialIPv4545
AS20750NetLan Ltd.UnclassifiedIPv4203
AS1299Arelion Sweden ABTransitIPv4 IPv6152
AS3356Level 3 Parent, LLCTransitIPv4 IPv6134
AS6939Hurricane Electric LLCTransitIPv4125
AS9002RETN LimitedUnclassifiedIPv4 IPv6125
AS1273IDDQD-ASBusinessIPv498
AS3257GTT Communications Inc.TransitIPv457
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv653
AS203312Global Pharma Centre JSCUnclassifiedIPv451

All 23 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.