asn.dev

Observed topology

AS5503 RMIFL

Education RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS5503: 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
AS2914NTT America, Inc.TransitIPv4 IPv6923
AS6939Hurricane Electric LLCTransitIPv4 IPv6346
AS1299Arelion Sweden ABTransitIPv4200
AS9002RETN LimitedUnclassifiedIPv4 IPv6161
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6121
AS33891Core-Backbone GmbHHostingIPv480
AS50304Blix Solutions ASUnclassifiedIPv480
AS24482SG.GSHostingIPv4 IPv641
AS48185team.blue NVUnclassifiedIPv4 IPv641
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv641

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51704RM Education LtdUnclassifiedIPv4 IPv696
AS29626Staffordshire County CouncilUnclassifiedIPv418

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6951
AS6939Hurricane Electric LLCTransitIPv4 IPv6381
AS1299Arelion Sweden ABTransitIPv4205
AS9002RETN LimitedUnclassifiedIPv4 IPv6166
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6131
AS51704RM Education LtdUnclassifiedIPv4 IPv696
AS33891Core-Backbone GmbHHostingIPv482
AS50304Blix Solutions ASUnclassifiedIPv482
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv644
AS3741Dimension DataUnclassifiedIPv443

Provenance

Where this comes from

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