asn.dev

Observed topology

AS396986 BYTEDANCE - Bytedance Inc.

Hosting ARIN

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

Transit

Upstream networks

All 112

Networks observed carrying traffic for AS396986: 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
AS1299Arelion Sweden ABTransitIPv4 IPv63,192
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,029
AS174Cogent Communications, LLCTransitIPv4 IPv61,367
AS21859Zenlayer IncHostingIPv4 IPv61,257
AS6939Hurricane Electric LLCTransitIPv4 IPv61,133
AS24203PT XL AxiataMobileIPv4 IPv6464
AS2914NTT America, Inc.TransitIPv4 IPv6431
AS7552Viettel GroupMobileIPv4 IPv6345
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6344
AS151552PT Threego Technology IndonesiaUnclassifiedIPv4 IPv6303

All 112 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150436Byteplus Pte. Ltd.HostingIPv4151

Adjacency

Adjacent networks

All 113

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv63,234
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,029
AS174Cogent Communications, LLCTransitIPv4 IPv61,367
AS21859Zenlayer IncHostingIPv4 IPv61,257
AS6939Hurricane Electric LLCTransitIPv4 IPv61,133
AS24203PT XL AxiataMobileIPv4 IPv6464
AS2914NTT America, Inc.TransitIPv4 IPv6431
AS7552Viettel GroupMobileIPv4 IPv6345
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6344
AS151552PT Threego Technology IndonesiaUnclassifiedIPv4 IPv6309

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