asn.dev

Observed topology

AS55967 BAIDU Beijing Baidu Netcom Science and Technology Co., Ltd.

Hosting DROP-listed space APNIC

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS55967: 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
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv61,142
AS2914NTT America, Inc.TransitIPv4 IPv6569
AS6939Hurricane Electric LLCTransitIPv4 IPv6309
AS3491PCCW Global (HK) Ltd.TransitIPv4116
AS17497Liasail Global Hongkong LimitedUnclassifiedIPv457
AS24482SG.GSHostingIPv4 IPv636
AS9002RETN LimitedUnclassifiedIPv4 IPv632
AS55720Gigabit Hosting Sdn BhdHostingIPv430
AS9304HGC Global Communications LimitedHostingIPv429
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv417

All 27 upstreams →

Transit

Downstream networks

inferred

Networks for which AS55967 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 27

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

ASNetworkTypeFamiliesPaths seen
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv61,142
AS2914NTT America, Inc.TransitIPv4 IPv6569
AS6939Hurricane Electric LLCTransitIPv4 IPv6309
AS3491PCCW Global (HK) Ltd.TransitIPv4116
AS17497Liasail Global Hongkong LimitedUnclassifiedIPv457
AS24482SG.GSHostingIPv4 IPv636
AS9002RETN LimitedUnclassifiedIPv4 IPv632
AS55720Gigabit Hosting Sdn BhdHostingIPv430
AS9304HGC Global Communications LimitedHostingIPv429
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv417

All 27 adjacent →

Provenance

Where this comes from

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