Country
—
ASN LANDING PAGE
CHINA169-BJ - China Unicom Beijing Province Network
Last updated · Jul 20, 2026
Country
—
Total prefixes
2420
IPv4 prefixes
0
IPv6 prefixes
0
CHINA169-BJ - China Unicom Beijing Province Network currently reports 2420 prefixes and 42 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
CHINA169-BJ - China Unicom Beijing Province Network is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS55990
AS55990
—
AS58448
AS58448
—
AS58811
AS58811
—
AS139148
AS139148
—
AS37963
AS37963
—
AS18239
AS18239
—
AS24151
AS24151
—
AS139178
AS139178
—
AS10212
AS10212
—
AS24147
AS24147
—
AS9802
AS9802
—
AS10100
AS10100
—
AS55960
AS55960
—
AS23844
AS23844
—
AS9811
AS9811
—
AS45083
AS45083
—
AS45075
AS45075
—
AS37937
AS37937
—
AS37970
AS37970
—
AS137764
AS137764
—
AS9810
AS9810
—
AS131497
AS131497
—
AS59034
AS59034
—
AS59012
AS59012
—
AS37942
AS37942
—
AS139138
AS139138
—
AS9805
AS9805
—
AS9818
AS9818
—
AS38027
AS38027
—
AS7653
AS7653
—
AS24430
AS24430
—
AS58536
AS58536
—
AS131578
AS131578
—
AS55966
AS55966
—
AS137735
AS137735
—
AS38381
AS38381
—
AS59073
AS59073
—
AS56002
AS56002
—
AS17428
AS17428
—
AS55468
AS55468
—
| Prefix | Name | Country |
|---|---|---|
| 1.119.178.0/23 | AS4808 | — |
| 1.119.192.0/21 | AS4808 | — |
| 1.119.200.0/22 | AS4808 | — |
| 1.119.208.0/23 | AS4808 | — |
| 1.119.210.0/23 | AS4808 | — |
| 101.124.0.0/20 | AS4808 | — |
| 101.124.19.0/24 | AS4808 | — |
| 101.124.22.0/24 | AS4808 | — |
| 101.124.62.0/24 | AS4808 | — |
| 101.199.128.0/24 | AS4808 | — |
| 101.199.129.0/24 | AS4808 | — |
| 101.199.252.0/24 | AS4808 | — |
| 101.199.253.0/24 | AS4808 | — |
| 101.199.254.0/24 | AS4808 | — |
| 101.199.255.0/24 | AS4808 | — |
| 101.236.0.0/21 | AS4808 | — |
| 101.236.16.0/21 | AS4808 | — |
| 101.236.24.0/21 | AS4808 | — |
| 101.236.32.0/21 | AS4808 | — |
| 101.236.40.0/21 | AS4808 | — |
| 101.236.48.0/21 | AS4808 | — |
| 101.236.56.0/21 | AS4808 | — |
| 101.236.64.0/21 | AS4808 | — |
| 101.236.72.0/21 | AS4808 | — |
| 101.236.8.0/21 | AS4808 | — |
| 101.237.0.0/19 | AS4808 | — |
| 101.251.192.0/23 | AS4808 | — |
| 101.251.194.0/24 | AS4808 | — |
| 101.251.196.0/22 | AS4808 | — |
| 101.251.200.0/24 | AS4808 | — |
| 101.251.201.0/24 | AS4808 | — |
| 101.251.203.0/24 | AS4808 | — |
| 101.251.204.0/22 | AS4808 | — |
| 101.251.208.0/20 | AS4808 | — |
| 101.251.224.0/24 | AS4808 | — |
| 101.251.225.0/24 | AS4808 | — |
| 101.251.226.0/24 | AS4808 | — |
| 101.251.228.0/24 | AS4808 | — |
| 101.251.230.0/23 | AS4808 | — |
| 101.251.233.0/24 | AS4808 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS4808 is an autonomous system number. The current source associates it with CHINA169-BJ - China Unicom Beijing Province Network and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS4808. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS4808, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.