Observed topology

AS53845 BBDTEL

Unclassified ARIN

Upstreams 8 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

Upstream graph Who carries AS53845, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS53845 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53845: 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.

AS	Network	Type	Families	Paths seen
AS3257	GTT Communications Inc.	Transit	IPv4	149
AS13739	Datacenter IP, LLC	Hosting	IPv4	85
AS812	Rogers Communications Canada Inc.	Mobile	IPv4	59
AS174	Cogent Communications, LLC	Transit	IPv4	58
AS209	CenturyLink Communications, LLC	Residential	IPv4	55
AS3356	Level 3 Parent, LLC	Transit	IPv4	54
AS2914	NTT America, Inc.	Transit	IPv4	40
AS13768	Aptum Technologies	Hosting	IPv4	36

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS397003	Bill Gosling Outsourcing Corp.	Unclassified	IPv4	114

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3257	GTT Communications Inc.	Transit	IPv4	185
AS13768	Aptum Technologies	Hosting	IPv4	114
AS397003	Bill Gosling Outsourcing Corp.	Unclassified	IPv4	114
AS13739	Datacenter IP, LLC	Hosting	IPv4	85
AS812	Rogers Communications Canada Inc.	Mobile	IPv4	59
AS174	Cogent Communications, LLC	Transit	IPv4	58
AS209	CenturyLink Communications, LLC	Residential	IPv4	55
AS3356	Level 3 Parent, LLC	Transit	IPv4	54
AS2914	NTT America, Inc.	Transit	IPv4	40

Provenance

Where this comes from

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