asn.dev

Observed topology

AS26954 NETZR

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS26954: 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
AS213753InterEdge B.V.UnclassifiedIPv4144
AS6939Hurricane Electric LLCTransitIPv648
AS11967Hop179 OUUnclassifiedIPv4 IPv628
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv65
AS401753BIXCE IncUnclassifiedIPv4 IPv65
AS3216PJSC "Vimpelcom"MobileIPv43

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS402536NETZRUnclassifiedIPv637
AS202301Mikhail FedorovUnclassifiedIPv66
AS112DNS-OARCUnclassifiedIPv62

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS213753InterEdge B.V.UnclassifiedIPv4144
AS6939Hurricane Electric LLCTransitIPv677
AS11967Hop179 OUUnclassifiedIPv4 IPv639
AS402536NETZRUnclassifiedIPv637
AS24482SG.GSHostingIPv4 IPv66
AS202301Mikhail FedorovUnclassifiedIPv66
AS401753BIXCE IncUnclassifiedIPv4 IPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65

All 18 adjacent →

Provenance

Where this comes from

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