asn.dev

Observed topology

AS51263 COUNTYBB

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS51263: 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 IPv6272
AS174Cogent Communications, LLCTransitIPv4264
AS41847Daniel O'MahonyUnclassifiedIPv4133
AS6461Zayo BandwidthTransitIPv476
AS3356Level 3 Parent, LLCTransitIPv4 IPv674
AS24482SG.GSHostingIPv4 IPv615
AS48185team.blue NVUnclassifiedIPv4 IPv615
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv615
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv614
AS8943Jump Networks LtdHostingIPv64

All 23 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6272
AS174Cogent Communications, LLCTransitIPv4264
AS41847Daniel O'MahonyUnclassifiedIPv4133
AS6461Zayo BandwidthTransitIPv476
AS3356Level 3 Parent, LLCTransitIPv4 IPv674
AS24482SG.GSHostingIPv4 IPv615
AS48185team.blue NVUnclassifiedIPv4 IPv615
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv615
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv614
AS8943Jump Networks LtdHostingIPv64

All 23 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.