asn.dev

Observed topology

AS25220 GLOBALNOC-AS equada network GmbH

Hosting RIPE Content

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

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS25220: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6174
AS33891Core-Backbone GmbHHostingIPv4 IPv6165
AS62336PURtel.com GmbHResidentialIPv4 IPv687
AS3356Level 3 Parent, LLCTransitIPv470
AS1299Arelion Sweden ABTransitIPv4 IPv668
AS2914NTT America, Inc.TransitIPv460
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv634
AS29551Aixit GmbHHostingIPv4 IPv624
AS24482SG.GSHostingIPv4 IPv617
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv614

All 31 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201066eGroup Technologies AGUnclassifiedIPv4123
AS29658HeureCom GmbHUnclassifiedIPv462

Adjacency

Adjacent networks

All 34

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv6201
AS6939Hurricane Electric LLCTransitIPv4 IPv6192
AS201066eGroup Technologies AGUnclassifiedIPv4123
AS3356Level 3 Parent, LLCTransitIPv491
AS62336PURtel.com GmbHResidentialIPv4 IPv687
AS1299Arelion Sweden ABTransitIPv4 IPv686
AS2914NTT America, Inc.TransitIPv478
AS29658HeureCom GmbHUnclassifiedIPv462
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv643
AS29551Aixit GmbHHostingIPv4 IPv629

All 34 adjacent →

Provenance

Where this comes from

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