AS4837China Unicom Backbone
As of 10th November 2026, AS4837 (China Unicom Backbone), a transit carrier registered in China with APNIC, originates 1,526 IPv4 prefixes covering 59.3M addresses and 652 IPv6 prefixes. By IPv4 address space that makes it the 9th-largest of the 80,723 networks we see originating IPv4, and the 2nd-largest of 617 in China. It is seen behind 34 upstream networks, most often AS1299 (Arelion (fka. Telia Carrier)) and AS3356 (Lumen (Level 3)), and in front of 96 downstream networks. 98% of its announcements have a valid RPKI ROA; 5 are RPKI-invalid. 98% of its routes reach at least 90% of full-feed peers.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS4837 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS4837 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.
Neighbouring networks
313
adjacent networks
- Upstreams
- 3411%
- Peers
- 18358%
- Downstreams
- 9631%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS1299Arelion (fka. Telia Carrier) | Peer | 228,062 | 60 | |
| AS3356Lumen (Level 3) | Peer | 87,044 | 63 | |
| AS6453TATA Communications (America) Inc | Peer | 74,455 | 32 | |
| AS2497Internet Initiative Japan Inc. | Peer | 74,140 | 6 | |
| AS2914NTT America, Inc. | Peer | 73,603 | 25 | |
| AS174Cogent Communications, LLC | Peer | 63,699 | 72 | |
| AS701Verizon Business | Peer | 55,297 | 92 | |
| AS6939Hurricane Electric LLC | Peer | 54,455 | 19 | |
| AS6762Telecom Italia Sparkle (Seabone) | Peer | 51,478 | 21 | |
| AS3320Deutsche Telekom AG | Peer | 39,405 | 36 |
Prefixes
All 2,178The largest blocks AS4837 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 27.192.0.0/11 | 2.1M | 75/76 |
| 39.64.0.0/11 | 2.1M | 75/76 |
| 112.224.0.0/11 | 2.1M | 75/76 |
| 42.224.0.0/12 | 1M | 75/76 |
| 101.16.0.0/12 | 1M | 74/76 |
| 110.240.0.0/12 | 1M | 74/76 |
| 113.224.0.0/12 | 1M | 74/76 |
| 115.48.0.0/12 | 1M | 75/76 |
| 119.176.0.0/12 | 1M | 75/76 |
| 120.0.0.0/12 | 1M | 74/76 |
Routing health
How AS4837's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.
RPKI origin validation
- Valid97.8%2,129
- Invalid0.2%5
- No ROA2.0%44
Propagation
- Globally propagated90% of full-feed peers or more98.3%2,141
- Partially propagated40% to 90%<0.1%1
- Seen by few peersUnder 40%1.7%36
Prefix sizes
IPv4 — 1,526 prefixes
- /112.1M addresses0.2%3
- /121M addresses0.6%9
- /13524k addresses1.8%27
- /14262k addresses2.6%39
- /15131k addresses3.8%58
- /1665.5k addresses7.4%113
- /1732.8k addresses3.1%48
- /1816.4k addresses4.8%73
- /198.2k addresses5.2%80
- /204.1k addresses4.3%66
- /212k addresses4.4%67
- /221k addresses11.2%171
- /23512 addresses4.8%74
- /24256 addresses45.7%698
IPv6 — 652 prefixes
- /3017.2B × /640.8%5
- /324.3B × /6457.5%375
- /332.1B × /640.6%4
- /341.1B × /640.5%3
- /35537M × /640.6%4
- /36268M × /647.1%46
- /4016.8M × /641.8%12
- /418.4M × /640.3%2
- /424.2M × /640.2%1
- /441M × /640.6%4
- /47131k × /640.6%4
- /4865.5k × /6429.4%192
Recent changes
Announcements that started or stopped since 11th Oct 2026.
- Announced221.214.140.0/249th Nov 2026
- Announced42.228.50.0/246th Nov 2026
- Announced61.163.245.0/246th Nov 2026
- Announced61.53.71.0/246th Nov 2026
- Announced119.187.151.0/245th Nov 2026
- Announced103.197.1.0/243rd Nov 2026
- Announced43.241.50.0/233rd Nov 2026
- Announced58.83.17.0/243rd Nov 2026
- Withdrawn218.28.2.0/243rd Nov 2026
- Withdrawn103.239.247.0/242nd Nov 2026
- Announced103.239.247.0/242nd Nov 2026
- Withdrawn103.45.161.0/242nd Nov 2026
26 announced and 16 withdrawn in all; the most recent are shown.
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.