asn.dev

Observed topology

AS399772 YOTTABIT

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS399772: 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
AS32621Twin City VoIP, Inc.HostingIPv450
AS63318Infotec ManitobaUnclassifiedIPv634
AS18451LES.NETUnclassifiedIPv4 IPv618

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS16543Gate West Communications Inc.UnclassifiedIPv4260
AS63318Infotec ManitobaUnclassifiedIPv4 IPv6208

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS32621Twin City VoIP, Inc.HostingIPv4 IPv6494
AS16543Gate West Communications Inc.UnclassifiedIPv4260
AS63318Infotec ManitobaUnclassifiedIPv4 IPv6242
AS18451LES.NETUnclassifiedIPv4 IPv642

Provenance

Where this comes from

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