asn.dev

Observed topology

AS4811 CHINANET-SHANGHAI-MAN China Telecom Group

Upstreams 2 carry this network
Downstreams 12 this network carries
Adjacent (IPv4) 14
Adjacent (IPv6) 8

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4811: 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
AS4134No.31,Jin-rong StreetResidentialIPv4 IPv690,848
AS4812China Telecom (Group)ResidentialIPv412

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.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45090Shenzhen Tencent Computer Systems Company LimitedHostingIPv4 IPv648,522
AS37963Hangzhou Alibaba Advertising Co.,Ltd.HostingIPv4 IPv614,472
AS55990Huawei Cloud Service data centerHostingIPv4 IPv67,020
AS1742821Vianet.Co.,LtdUnclassifiedIPv41,062
AS9809SHENZHEN NOVA TECHNOLOGIES DEVELOPMENT.,LTD.UnclassifiedIPv4991
AS23848Shenzhen Ping An Communication Technology Co.,LtdUnclassifiedIPv4 IPv6821
AS45079GDS CHANGAN SERVICES Ltd.UnclassifiedIPv4 IPv6723
AS137718Beijing Volcano Engine Technology Co., Ltd.HostingIPv4 IPv6663
AS58593Shanghai Blue Cloud Technology Co.,LtdUnclassifiedIPv4 IPv6212
AS59019Beijing Kingsoft Cloud Internet Technology Co., LtdUnclassifiedIPv4185
AS137801AIPO Cloud (Guizhou) Technology Co., Ltd.UnclassifiedIPv451
AS55992Beijing Qihu Technology Company LimitedUnclassifiedIPv46

Adjacency

Adjacent networks

22 shown

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

ASNetworkTypeFamiliesPaths seen
AS4134No.31,Jin-rong StreetResidentialIPv4 IPv6165,562
AS45090Shenzhen Tencent Computer Systems Company LimitedHostingIPv4 IPv648,522
AS37963Hangzhou Alibaba Advertising Co.,Ltd.HostingIPv4 IPv614,472
AS55990Huawei Cloud Service data centerHostingIPv4 IPv67,020
AS1742821Vianet.Co.,LtdUnclassifiedIPv41,062
AS9809SHENZHEN NOVA TECHNOLOGIES DEVELOPMENT.,LTD.UnclassifiedIPv4991
AS23848Shenzhen Ping An Communication Technology Co.,LtdUnclassifiedIPv4 IPv6821
AS45079GDS CHANGAN SERVICES Ltd.UnclassifiedIPv4 IPv6723
AS137718Beijing Volcano Engine Technology Co., Ltd.HostingIPv4 IPv6663
AS58593Shanghai Blue Cloud Technology Co.,LtdUnclassifiedIPv4 IPv6212
AS59019Beijing Kingsoft Cloud Internet Technology Co., LtdUnclassifiedIPv4185
AS137801AIPO Cloud (Guizhou) Technology Co., Ltd.UnclassifiedIPv451
AS4812China Telecom (Group)ResidentialIPv426
AS55992Beijing Qihu Technology Company LimitedUnclassifiedIPv46

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS4811, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it.

No exchange membership on file. That is not the same as peering nowhere: the dataset records what PCH has collected, and many exchanges publish no participant list at all.

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.