asn.dev

Observed topology

AS53407 UTOPIA-FIBER

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53407: 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 IPv61,317
AS3356Level 3 Parent, LLCTransitIPv4 IPv6212

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS393429Bertram Communications LLCUnclassifiedIPv4384
AS20248Take 2 Hosting, Inc.HostingIPv4319
AS26765Bountiful CityUnclassifiedIPv464
AS54362Ogden City CorporationUnclassifiedIPv455
AS398412WEBER COUNTYUnclassifiedIPv451
AS394662Unified Fire AuthorityUnclassifiedIPv446
AS62494UTOPIAUnclassifiedIPv445
AS5048FIBERNET Corp.HostingIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,175
AS393429Bertram Communications LLCUnclassifiedIPv4384
AS3356Level 3 Parent, LLCTransitIPv4 IPv6358
AS20248Take 2 Hosting, Inc.HostingIPv4319
AS62494UTOPIAUnclassifiedIPv475
AS26765Bountiful CityUnclassifiedIPv464
AS54362Ogden City CorporationUnclassifiedIPv455
AS398412WEBER COUNTYUnclassifiedIPv451
AS394662Unified Fire AuthorityUnclassifiedIPv446
AS5048FIBERNET Corp.HostingIPv410

Provenance

Where this comes from

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