asn.dev

Observed topology

AS5378 Vodafone Limited

Unclassified RIPE

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS5378: 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
AS1273IDDQD-ASBusinessIPv4 IPv6561
AS6939Hurricane Electric LLCTransitIPv4 IPv6206
AS3356Level 3 Parent, LLCTransitIPv4 IPv690
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv668
AS33891Core-Backbone GmbHHostingIPv444
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv623
AS24482SG.GSHostingIPv4 IPv623
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv623
AS48185team.blue NVUnclassifiedIPv4 IPv623
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv623

All 23 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25135Vodafone LimitedMobileIPv4 IPv61,506
AS25310Vodafone LimitedUnclassifiedIPv4232

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS25135Vodafone LimitedMobileIPv4 IPv65,485
AS1273IDDQD-ASBusinessIPv4 IPv63,267
AS6939Hurricane Electric LLCTransitIPv4 IPv61,025
AS3356Level 3 Parent, LLCTransitIPv4 IPv6530
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6324
AS25310Vodafone LimitedUnclassifiedIPv4232
AS33891Core-Backbone GmbHHostingIPv4219
AS7575Australian Academic and Research Network (AARNet)EducationIPv4120
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv6116
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6114

All 25 adjacent →

Provenance

Where this comes from

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