asn.dev

Observed topology

AS150436 BYTEPLUS-AS-AP Byteplus Pte. Ltd.

Hosting APNIC

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS150436: 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
AS138699TIKTOK PTE. LTD.HostingIPv4 IPv65,035
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv61,674
AS21859Zenlayer IncHostingIPv4 IPv6996
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6816
AS1299Arelion Sweden ABTransitIPv4639
AS7713PT Telekomunikasi IndonesiaResidentialIPv4 IPv6591
AS6939Hurricane Electric LLCTransitIPv4 IPv6587
AS4229Zenlayer IncHostingIPv4315
AS396986Bytedance Inc.HostingIPv4 IPv6163
AS35819Etihad Etisalat, a joint stock companyMobileIPv4 IPv692

All 20 upstreams →

Transit

Downstream networks

inferred

Networks for which AS150436 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 20

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

ASNetworkTypeFamiliesPaths seen
AS138699TIKTOK PTE. LTD.HostingIPv4 IPv65,035
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv61,674
AS21859Zenlayer IncHostingIPv4 IPv6996
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6816
AS1299Arelion Sweden ABTransitIPv4639
AS7713PT Telekomunikasi IndonesiaResidentialIPv4 IPv6591
AS6939Hurricane Electric LLCTransitIPv4 IPv6587
AS4229Zenlayer IncHostingIPv4315
AS396986Bytedance Inc.HostingIPv4 IPv6163
AS35819Etihad Etisalat, a joint stock companyMobileIPv4 IPv692

All 20 adjacent →

Provenance

Where this comes from

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