asn.dev

Observed topology

AS51055 BRIDGEP-AS Bridge Fibre Limited

Residential RIPE

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS51055: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6140
AS2914NTT America, Inc.TransitIPv4 IPv6103
AS6939Hurricane Electric LLCTransitIPv4 IPv685
AS34549meerfarbig GmbH & Co. KGHostingIPv421
AS33891Core-Backbone GmbHHostingIPv414
AS50304Blix Solutions ASUnclassifiedIPv414
AS24482SG.GSHostingIPv4 IPv69
AS48185team.blue NVUnclassifiedIPv4 IPv69
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv69
AS3216PJSC "Vimpelcom"MobileIPv47

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11939THE MATHWORKS, INC.UnclassifiedIPv470

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6140
AS2914NTT America, Inc.TransitIPv4 IPv6136
AS6939Hurricane Electric LLCTransitIPv4 IPv693
AS11939THE MATHWORKS, INC.UnclassifiedIPv470
AS34549meerfarbig GmbH & Co. KGHostingIPv427
AS33891Core-Backbone GmbHHostingIPv416
AS50304Blix Solutions ASUnclassifiedIPv416
AS24482SG.GSHostingIPv4 IPv611
AS48185team.blue NVUnclassifiedIPv4 IPv610
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv610

All 22 adjacent →

Provenance

Where this comes from

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