AS38365· CN— BAIDU Beijing Baidu Netcom Science and Technology Co., Ltd.

· Graph Explorer · View prefixes · Compare ASN · Export prefixes

BAIDU Beijing Baidu Netcom Science and Technology Co., Ltd. · · CN

Identity source

AS38365 ·

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

NRO allocation data

138IPv4 prefixes

12IPv6 prefixes

7Observed neighbors

RPKIValid: 150 Invalid: 0 Not found: 0 Unknown: 0

Selected local snapshot coverage; not the whole Internet. BGP snapshots: ris-rrc00 11 Oct 08:00 UTC; routeviews2 11 Oct 10:00 UTC; routeviews6 11 Oct 10:00 UTC. Validator: 11 Oct 11:44 UTC. Publication-point issues: 88

Address space details

Overlapping originated prefixes counted once. IPv4 addresses: 347,136

IPv6 addresses: 81208866577120946033382549094400

Loading public source data…

Observed originated prefixes

These are observed BGP origins, not an inventory of registered allocations or transit reachability.

150 matching prefix–origin pairs. Each pair appears once; source observations are in Details.

Prefix	RPKI	Last observed	Details
42.199.240.0/22	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.0.0/18	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.0.0/19	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.32.0/19	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.64.0/18	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.64.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.80.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.96.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.112.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.128.0/18	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.128.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.144.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.160.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.176.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.192.0/19	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.192.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.208.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.224.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.224.0/21	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.232.0/21	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.240.0/21	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.12.240.0/23	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.13.0.0/18	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.13.0.0/19	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid
106.13.32.0/20	Valid	11 Oct 10:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T10:00:00+00:00 · 1 selected peers · RPKI valid

Next rows

Export observed prefixes: TXT · CSV · JSON

AS connectivity

7 observed neighbors · 9 direct networks including inferred relationships (excludes this AS).

Open in Graph Explorer

9 matching networks · 1–9 shown

Network	Relationship to AS38365	IPv4/IPv6	Evidence
AS4808 · CN CHINA169-BJ China Unicom Beijing Province Network	v6: peer	IPv6	Observed + inferred IPv6 · peer · CAIDA 2026-10-01 · routeviews6 11 Oct 10:00 UTC
AS4837 · CN CHINA169-Backbone	v4: upstream / v6: upstream	IPv4, IPv6	Observed + inferred IPv6 · upstream · CAIDA 2026-10-01 · ris-rrc00 11 Oct 08:00 UTC IPv4 · upstream · CAIDA 2026-10-01 · ris-rrc00 11 Oct 08:00 UTC
AS9808 · CN China Mobile Communications Group Co., Ltd	v4: upstream	IPv4	Inferred IPv4 · upstream · CAIDA 2026-10-01 · No BGP observation
AS23724 · CN CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation	v4: upstream / v6: upstream	IPv4, IPv6	Observed + inferred IPv4 · upstream · CAIDA 2026-10-01 · ris-rrc00 11 Oct 08:00 UTC; routeviews2 11 Oct 10:00 UTC IPv6 · upstream · CAIDA 2026-10-01 · ris-rrc00 11 Oct 08:00 UTC; routeviews6 11 Oct 10:00 UTC
AS56046 · CN CMNET-JIANGSU-AP China Mobile communications corporation	v4: upstream	IPv4	Inferred IPv4 · upstream · CAIDA 2026-10-01 · No BGP observation
AS58466 · CN CT-GUANGZHOU-IDC CHINANET Guangdong province network	v4: upstream / v6: upstream	IPv4, IPv6	Observed + inferred IPv4 · upstream · CAIDA 2026-10-01 · ris-rrc00 11 Oct 08:00 UTC; routeviews2 11 Oct 10:00 UTC IPv6 · upstream · CAIDA 2026-10-01 · ris-rrc00 11 Oct 08:00 UTC; routeviews6 11 Oct 10:00 UTC
AS134756 · CN CHINANET-NANJING-JISHAN-IDC CHINANET Nanjing Jishan IDC network	v4: upstream / v6: unknown	IPv4, IPv6	Observed + inferred IPv6 · unknown · Relationship unknown · ris-rrc00 11 Oct 08:00 UTC; routeviews6 11 Oct 10:00 UTC IPv4 · upstream · CAIDA 2026-10-01 · ris-rrc00 11 Oct 08:00 UTC; routeviews2 11 Oct 10:00 UTC
AS139080 · CN CMNET-SCIDC-CN The Internet Data Center of Sichuan Mobile Communication Company Limited	v4: upstream	IPv4	Observed + inferred IPv4 · upstream · CAIDA 2026-10-01 · ris-rrc00 11 Oct 08:00 UTC
AS140903 · CN CHINANET-HEBEI-BAODING-MAN CHINA TELECOM	v6: unknown	IPv6	Observed IPv6 · unknown · Relationship unknown · ris-rrc00 11 Oct 08:00 UTC; routeviews6 11 Oct 10:00 UTC

Clear filters

Peering & locations

Loading public source data…

Registry information

Registry data is unavailable in the local cache. Routing origins are not a substitute for registry ownership.

Refresh registry status

Allocation statistics

NRO/RIR delegated-extended records describe allocation or assignment ranges. They do not prove a BGP announcement or replace more-specific RDAP registration information. Country is the allocation record’s registration country, not the physical location of every address.

AS38335–AS38384 · apnic · assigned · ASN allocation country: CN · Allocation date: 2007-01-25 — NRO/RIR data · snapshot 10 Oct 00:00 UTC

NRO data and format

Prefix count history

Local observation changes

Only comparable successful snapshots are compared. First imports, changed peer coverage and collection gaps are baselines, not new global routes or withdrawals. RPKI transition history is not available before it has been recorded.

No retained changes are available for this resource.

Retained local prefix-count observations

Separate collector series. Missing rows are not zero. Peer-set changes are separate coverage, not a continuous trend.

Source	Snapshot	Family	Prefixes	Peer coverage
routeviews2	11 Oct 10:00 UTC	IPv4	120	140.192.8.16/IPv4
routeviews6	11 Oct 10:00 UTC	IPv6	11	2406:840:feed:2::1/IPv6
ris-rrc00	11 Oct 08:00 UTC	IPv6	12	2a00:5884::6/IPv6, 89.234.186.6/IPv4
routeviews6	11 Oct 08:00 UTC	IPv6	11	2406:840:feed:2::1/IPv6
routeviews2	11 Oct 08:00 UTC	IPv4	120	140.192.8.16/IPv4
ris-rrc00	11 Oct 08:00 UTC	IPv4	138	2a00:5884::6/IPv6, 89.234.186.6/IPv4
ris-rrc00	11 Oct 00:00 UTC	IPv4	138	2a00:5884::6/IPv6, 89.234.186.6/IPv4
ris-rrc00	11 Oct 00:00 UTC	IPv6	12	2a00:5884::6/IPv6, 89.234.186.6/IPv4