AS55990 · CN — HWCSNET Huawei Cloud Service data center

· View prefixes · Compare ASN · Export prefixes

HWCSNET Huawei Cloud Service data center · · CN

Identity source

AS55990 ·

CN HWCSNET Huawei Cloud Service data center

NRO allocation data

388IPv4 prefixes

20IPv6 prefixes

12Observed neighbors

RPKIValid: 382 Invalid: 0 Not found: 26 Unknown: 0

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

Address space details

Overlapping originated prefixes counted once. IPv4 addresses: 1,606,400

IPv6 addresses: 299583907358701255783937474560

Loading public source data…

Observed originated prefixes

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

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

Prefix	RPKI	Last observed	Details
1.92.0.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.92.64.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.92.128.0/19	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.92.160.0/19	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.92.192.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.94.0.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.94.64.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.94.128.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.94.192.0/19	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.94.224.0/19	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.0.0/19	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.31.0/24	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.32.0/19	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.64.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.128.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.192.0/18	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.248.0/24	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.249.0/24	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
1.95.250.0/24	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
43.254.0.0/22	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
43.254.0.0/24	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
43.254.1.0/24	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
43.254.2.0/24	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
43.254.3.0/24	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid
49.4.0.0/20	Valid	11 Oct 08:00 UTC	2 source observations ris-rrc00 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid routeviews2 · 2026-10-11T08:00:00+00:00 · 1 selected peers · RPKI valid

Next rows

Export observed prefixes: TXT · CSV · JSON

AS connectivity

12 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.

Open AS Graph Explorer

Loading topology…

Darker nodes = larger inferred customer cone. CAIDA IPv4 customer cone (includes the AS itself); unknown / IPv6 cone is gray.
Arrow = provider → customer, not traffic direction. Purple: provider/customer · teal: peer · gray: unknown/mixed. Solid: observed BGP adjacency · dashed: inferred only. A graph path is not an observed BGP route or a promise of transit.

Find node (also searches grouped networks)

12 matching neighbors · 1–12 shown

Network	IPv4/IPv6	Seen in	Last observed	Details
AS4808 · CN CHINA169-BJ China Unicom Beijing Province Network	IPv4, IPv6	ris-rrc00, routeviews2, routeviews6	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 08:00 UTC routeviews2 · IPv4 · 11 Oct 08:00 UTC routeviews6 · IPv6 · 11 Oct 08:00 UTC
AS4811 · CN CHINANET-SHANGHAI-MAN China Telecom Group	IPv4, IPv6	ris-rrc00, routeviews2, routeviews6	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 08:00 UTC routeviews2 · IPv4 · 11 Oct 08:00 UTC ris-rrc00 · IPv6 · 11 Oct 08:00 UTC routeviews6 · IPv6 · 11 Oct 08:00 UTC
AS9808 · CN China Mobile Communications Group Co., Ltd	IPv4	ris-rrc00	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 08:00 UTC
AS23724 · CN CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation	IPv4, IPv6	ris-rrc00, routeviews2	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 08:00 UTC routeviews2 · IPv4 · 11 Oct 08:00 UTC ris-rrc00 · IPv6 · 11 Oct 08:00 UTC
AS24400 · CN CMNET-V4SHANGHAI-AS-AP Shanghai Mobile Communications Co.,Ltd.	IPv4	ris-rrc00	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 08:00 UTC
AS58466 · CN CT-GUANGZHOU-IDC CHINANET Guangdong province network	IPv4, IPv6	ris-rrc00, routeviews2	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 08:00 UTC routeviews2 · IPv4 · 11 Oct 08:00 UTC ris-rrc00 · IPv6 · 11 Oct 08:00 UTC
AS131574 · CN HIDDOS Beijing Haiyu Technology Co. Ltd..	IPv4	ris-rrc00, routeviews2	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 08:00 UTC routeviews2 · IPv4 · 11 Oct 08:00 UTC
AS133111 · CN CNT-NORTHCHINA CERNET New Technology Co., Ltd	IPv6	routeviews6	11 Oct 08:00 UTC	Source observations routeviews6 · IPv6 · 11 Oct 08:00 UTC
AS134542 · CN UNICOM-GUIAN China Unicom IP network	IPv6	routeviews6	11 Oct 08:00 UTC	Source observations routeviews6 · IPv6 · 11 Oct 08:00 UTC
AS136958 · CN UNICOM-GUANGZHOU-IDC China Unicom Guangdong IP network	IPv6	ris-rrc00, routeviews6	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv6 · 11 Oct 08:00 UTC routeviews6 · IPv6 · 11 Oct 08:00 UTC
AS138421 · CN CU-CN-AS China Unicom	IPv6	routeviews6	11 Oct 08:00 UTC	Source observations routeviews6 · IPv6 · 11 Oct 08:00 UTC
AS139203 · CN CHINANET-GUIZHOU-GUIAN-IDC Guizhou GuiAn IDC	IPv4, IPv6	ris-rrc00, routeviews2	11 Oct 08:00 UTC	Source observations ris-rrc00 · IPv4 · 11 Oct 08:00 UTC routeviews2 · IPv4 · 11 Oct 08:00 UTC ris-rrc00 · IPv6 · 11 Oct 08:00 UTC

Clear neighbor filters

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.

AS55956–AS56015 · apnic · assigned · ASN allocation country: CN · Allocation date: 2010-12-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
routeviews6	11 Oct 08:00 UTC	IPv6	20	2406:840:feed:2::1/IPv6
ris-rrc00	11 Oct 08:00 UTC	IPv4	388	2a00:5884::6/IPv6, 89.234.186.6/IPv4
ris-rrc00	11 Oct 08:00 UTC	IPv6	20	2a00:5884::6/IPv6, 89.234.186.6/IPv4
routeviews2	11 Oct 08:00 UTC	IPv4	385	140.192.8.16/IPv4
routeviews2	11 Oct 06:00 UTC	IPv4	385	140.192.8.16/IPv4
routeviews6	11 Oct 06:00 UTC	IPv6	20	2406:840:feed:2::1/IPv6
ris-rrc00	11 Oct 00:00 UTC	IPv4	388	2a00:5884::6/IPv6, 89.234.186.6/IPv4
ris-rrc00	11 Oct 00:00 UTC	IPv6	20	2a00:5884::6/IPv6, 89.234.186.6/IPv4