AS24547 · CN — CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited

· View prefixes · Compare ASN · Export prefixes

CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited · · CN

Identity source

AS24547 ·

CN CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited

NRO allocation data

976IPv4 prefixes

2,126IPv6 prefixes

1Observed neighbors

RPKIValid: 3026 Invalid: 0 Not found: 76 Unknown: 0

Selected local snapshot coverage; not the whole Internet. BGP snapshots: ris-rrc00 11 Oct 00:00 UTC; routeviews2 11 Oct 06:00 UTC; routeviews6 11 Oct 06:00 UTC. Validator: 11 Oct 07:43 UTC. Publication-point issues: 91

Address space details

Overlapping originated prefixes counted once. IPv4 addresses: 725,504

IPv6 addresses: 1904344681312289617276632563712

Loading public source data…

Observed originated prefixes

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

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

Prefix	RPKI	Last observed	Details
36.134.82.0/23	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.137.88.0/23	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.139.40.0/23	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.139.42.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.139.249.0/24	Not Found	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI not_found routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI not_found
36.140.1.0/24	Not Found	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI not_found routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI not_found
36.140.2.0/23	Not Found	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI not_found routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI not_found
36.140.194.0/23	Not Found	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI not_found routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI not_found
36.140.212.0/22	Not Found	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI not_found routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI not_found
36.140.243.0/24	Not Found	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI not_found routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI not_found
36.143.0.0/18	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.0.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.1.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.2.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.3.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.4.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.5.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.6.0/23	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.12.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.13.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.14.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.18.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.19.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.20.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid
36.143.21.0/24	Valid	11 Oct 06:00 UTC	2 source observations ris-rrc00 · 2026-10-11T00:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T06:00:00+00:00 · 1 selected peers · RPKI valid

Next rows

Export observed prefixes: TXT · CSV · JSON

Observed AS neighbors

1 unique neighbors in the selected local snapshots. This is the available collector dataset, not a complete map of the Internet. Adjacency does not establish upstream service or peering.

1 matching neighbors · 1–1 shown

Network	IPv4/IPv6	Seen in	Last observed	Details
AS9808 · CN China Mobile Communications Group Co., Ltd	IPv4, IPv6	ris-rrc00, routeviews2, routeviews6	11 Oct 06:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 00:00 UTC routeviews2 · IPv4 · 11 Oct 06:00 UTC ris-rrc00 · IPv6 · 11 Oct 00:00 UTC routeviews6 · IPv6 · 11 Oct 06:00 UTC

Clear neighbor filters

View observed neighbor graph (up to 15 AS nodes)

Lines mean observed adjacency, with no commercial direction inferred. The table above provides the same evidence and source times.

Showing 1 of 1 matching neighbors, in table sort order, independent of table page.

Peering & locations

Loading public source data…

Registry information

No cached registry response is available yet. Routing origins above are not a substitute for registry ownership.

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.

AS24547–AS24547 · apnic · assigned · ASN allocation country: CN · Allocation date: 2006-01-24 — 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 06:00 UTC	IPv4	976	140.192.8.16/IPv4
routeviews6	11 Oct 06:00 UTC	IPv6	2126	2406:840:feed:2::1/IPv6
routeviews2	11 Oct 04:00 UTC	IPv4	976	140.192.8.16/IPv4
routeviews6	11 Oct 04:00 UTC	IPv6	2126	2406:840:feed:2::1/IPv6
ris-rrc00	11 Oct 00:00 UTC	IPv4	976	2a00:5884::6/IPv6, 89.234.186.6/IPv4
ris-rrc00	11 Oct 00:00 UTC	IPv6	2126	2a00:5884::6/IPv6, 89.234.186.6/IPv4
ris-rrc00	10 Oct 16:00 UTC	IPv4	976	2a00:5884::6/IPv6, 89.234.186.6/IPv4
ris-rrc00	10 Oct 16:00 UTC	IPv6	2126	2a00:5884::6/IPv6, 89.234.186.6/IPv4