Network · data from 2026-11-12
AS23881 UDomain Web Hosting Company Limited
Registry name: UDOMAIN-AS-AP - UDomain Web Hosting Company Ltd, HK · PeeringDB
75IPv4 routes
96.0% RPKI valid · 100.0% with a route object
2IPv6 routes
0.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
5No ROA
0 with no route object for this origin
4Low visibility
seen by under 10% of full-table peers
122Route objects not announced
registered with origin AS23881, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS23881, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 203.135.128.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 11 2%low visibility |
| 203.135.134.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 11 2%low visibility |
| 203.135.138.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 11 2%low visibility |
| 2400:c300::/48 | No ROA | RIR databaseAPNIC | 636 100% |
| 2400:c300:1::/48 | No ROA | RIR databaseAPNIC | 636 100% |
| 23.226.0.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 23.226.1.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 23.226.2.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 23.226.3.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 23.226.4.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 23.226.6.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 23.226.7.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 23.226.8.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 23.226.11.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.15.180.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.15.181.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.15.183.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.15.194.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.15.195.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.15.196.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.15.197.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.15.199.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.19.25.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.19.26.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.19.27.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 162.247.0.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 162.247.2.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 162.247.3.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.90.224.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.90.225.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.90.226.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.90.227.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.90.228.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.90.229.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.90.230.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.90.254.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.128.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.129.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.130.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.131.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.133.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.134.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.135.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.136.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.137.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.138.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.139.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.140.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.141.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.142.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.143.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.146.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.147.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.148.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.149.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.150.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.151.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.153.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.154.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.155.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.156.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.157.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.158.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.135.159.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.121.192.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.121.193.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.121.194.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.121.196.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.121.197.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.121.198.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.121.199.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.121.200.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 45.121.203.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.15.192.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.135.132.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.121.201.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 103.15.198.0/24 | Valid | RIR databaseAPNIC, RADB | 11 2%low visibility |
AS-SET
AS23881's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 130 are in fix.csv.
- ROA: none5
- Route object: RIR3
- Route object: not announced122
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.135.128.0/23 | No ROA covers it. Add a ROA for AS23881, maxLength 23. |
| Route object: RIR | 203.135.128.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.135.134.0/23 | No ROA covers it. Add a ROA for AS23881, maxLength 23. |
| Route object: RIR | 203.135.134.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.135.138.0/23 | No ROA covers it. Add a ROA for AS23881, maxLength 23. |
| Route object: RIR | 203.135.138.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 2400:c300::/48 | No ROA covers it. Add a ROA for AS23881, maxLength 48. |
| ROA: none | 2400:c300:1::/48 | No ROA covers it. Add a ROA for AS23881, maxLength 48. |
Route objects not announced
Route objects with origin AS23881 whose prefix no peer sees AS23881 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.226.0.0/20 | RADB | No ROA |
| 23.226.5.0/24 | APNIC, RADB | Valid |
| 23.226.9.0/24 | APNIC, RADB | Valid |
| 23.226.10.0/24 | APNIC, RADB | Valid |
| 23.226.12.0/24 | APNIC, RADB | Valid |
| 23.226.13.0/24 | APNIC, RADB | Valid |
| 23.226.14.0/24 | APNIC, RADB | Valid |
| 23.226.15.0/24 | APNIC, RADB | Valid |
| 45.121.192.0/21 | NTTCOM, RADB | No ROA |
| 45.121.192.0/22 | NTTCOM, RADB | No ROA |
| 45.121.192.0/23 | NTTCOM, RADB | No ROA |
| 45.121.194.0/23 | NTTCOM, RADB | No ROA |
| 45.121.195.0/24 | APNIC, NTTCOM, RADB | Valid |
| 45.121.196.0/22 | NTTCOM, RADB | No ROA |
| 45.121.196.0/23 | NTTCOM, RADB | No ROA |
| 45.121.198.0/23 | NTTCOM, RADB | No ROA |
| 45.121.200.0/22 | NTTCOM, RADB | No ROA |
| 45.121.200.0/23 | NTTCOM, RADB | No ROA |
| 45.121.202.0/23 | NTTCOM, RADB | No ROA |
| 103.15.180.0/22 | NTTCOM, RADB | No ROA |
| 103.15.180.0/23 | NTTCOM, RADB | No ROA |
| 103.15.182.0/23 | NTTCOM, RADB | No ROA |
| 103.15.192.0/21 | NTTCOM, RADB | No ROA |
| 103.15.192.0/22 | NTTCOM, RADB | No ROA |
| 103.15.192.0/23 | NTTCOM, RADB | No ROA |
| 103.15.194.0/23 | NTTCOM, RADB | No ROA |
| 103.15.196.0/22 | NTTCOM, RADB | No ROA |
| 103.15.196.0/23 | NTTCOM, RADB | No ROA |
| 103.15.198.0/23 | NTTCOM, RADB | No ROA |
| 103.19.24.0/22 | NTTCOM, RADB | No ROA |
| 103.19.24.0/23 | NTTCOM, RADB | No ROA |
| 103.19.24.0/24 | APNIC, RADB | Valid |
| 103.19.26.0/23 | NTTCOM, RADB | No ROA |
| 103.92.86.0/24 | APNIC, NTTCOM, RADB | Valid |
| 162.247.0.0/22 | RADB | No ROA |
| 162.247.1.0/24 | APNIC, RADB | Valid |
| 203.90.224.0/19 | RADB | No ROA |
| 203.90.224.0/20 | RADB | No ROA |
| 203.90.224.0/21 | RADB | No ROA |
| 203.90.224.0/22 | NTTCOM, RADB | No ROA |
| 203.90.224.0/23 | NTTCOM, RADB | No ROA |
| 203.90.226.0/23 | NTTCOM, RADB | No ROA |
| 203.90.228.0/22 | RADB | No ROA |
| 203.90.228.0/23 | NTTCOM, RADB | No ROA |
| 203.90.230.0/23 | RADB | No ROA |
| 203.90.231.0/24 | RADB | No ROA |
| 203.90.232.0/21 | RADB | No ROA |
| 203.90.232.0/22 | RADB | No ROA |
| 203.90.232.0/23 | RADB | No ROA |
| 203.90.232.0/24 | RADB | No ROA |
| 203.90.233.0/24 | RADB | No ROA |
| 203.90.234.0/23 | RADB | No ROA |
| 203.90.234.0/24 | RADB | No ROA |
| 203.90.235.0/24 | RADB | No ROA |
| 203.90.236.0/22 | RADB | No ROA |
| 203.90.236.0/23 | RADB | No ROA |
| 203.90.236.0/24 | RADB | No ROA |
| 203.90.237.0/24 | RADB | No ROA |
| 203.90.238.0/23 | RADB | No ROA |
| 203.90.238.0/24 | RADB | No ROA |
| 203.90.239.0/24 | RADB | No ROA |
| 203.90.240.0/20 | RADB | No ROA |
| 203.90.240.0/21 | RADB | No ROA |
| 203.90.240.0/22 | RADB | No ROA |
| 203.90.240.0/23 | RADB | No ROA |
| 203.90.240.0/24 | RADB | No ROA |
| 203.90.241.0/24 | RADB | No ROA |
| 203.90.242.0/23 | RADB | No ROA |
| 203.90.242.0/24 | RADB | No ROA |
| 203.90.243.0/24 | RADB | No ROA |
| 203.90.244.0/22 | RADB | No ROA |
| 203.90.244.0/23 | RADB | No ROA |
| 203.90.244.0/24 | RADB | No ROA |
| 203.90.245.0/24 | RADB | No ROA |
| 203.90.246.0/23 | RADB | No ROA |
| 203.90.246.0/24 | RADB | No ROA |
| 203.90.247.0/24 | RADB | No ROA |
| 203.90.248.0/21 | RADB | No ROA |
| 203.90.248.0/22 | RADB | No ROA |
| 203.90.248.0/23 | RADB | No ROA |
| 203.90.248.0/24 | RADB | No ROA |
| 203.90.249.0/24 | RADB | No ROA |
| 203.90.250.0/23 | RADB | No ROA |
| 203.90.250.0/24 | RADB | No ROA |
| 203.90.251.0/24 | RADB | No ROA |
| 203.90.252.0/22 | RADB | No ROA |
| 203.90.252.0/23 | NTTCOM, RADB | No ROA |
| 203.90.252.0/24 | APNIC, RADB | Valid |
| 203.90.254.0/23 | RADB | No ROA |
| 203.90.255.0/24 | RADB | No ROA |
| 203.135.128.0/19 | NTTCOM, RADB | No ROA |
| 203.135.128.0/20 | NTTCOM, RADB | No ROA |
| 203.135.128.0/21 | NTTCOM, RADB | No ROA |
| 203.135.128.0/22 | NTTCOM, RADB | No ROA |
| 203.135.130.0/23 | NTTCOM, RADB | No ROA |
| 203.135.132.0/22 | NTTCOM, RADB | No ROA |
| 203.135.132.0/23 | NTTCOM, RADB | No ROA |
| 203.135.136.0/21 | NTTCOM, RADB | No ROA |
| 203.135.136.0/22 | NTTCOM, RADB | No ROA |
| 203.135.136.0/23 | NTTCOM, RADB | No ROA |
| 203.135.140.0/22 | NTTCOM, RADB | No ROA |
| 203.135.140.0/23 | NTTCOM, RADB | No ROA |
| 203.135.142.0/23 | NTTCOM, RADB | No ROA |
| 203.135.144.0/20 | NTTCOM, RADB | No ROA |
| 203.135.144.0/21 | NTTCOM, RADB | No ROA |
| 203.135.144.0/22 | NTTCOM, RADB | No ROA |
| 203.135.144.0/23 | NTTCOM, RADB | No ROA |
| 203.135.144.0/24 | APNIC, RADB | Valid |
| 203.135.145.0/24 | APNIC, RADB | Valid |
| 203.135.146.0/23 | NTTCOM, RADB | No ROA |
| 203.135.148.0/22 | NTTCOM, RADB | No ROA |
| 203.135.148.0/23 | NTTCOM, RADB | No ROA |
| 203.135.150.0/23 | NTTCOM, RADB | No ROA |
| 203.135.152.0/21 | NTTCOM, RADB | No ROA |
| 203.135.152.0/22 | NTTCOM, RADB | No ROA |
| 203.135.152.0/23 | NTTCOM, RADB | No ROA |
| 203.135.152.0/24 | APNIC, RADB | Valid |
| 203.135.154.0/23 | NTTCOM, RADB | No ROA |
| 203.135.156.0/22 | NTTCOM, RADB | No ROA |
| 203.135.156.0/23 | NTTCOM, RADB | No ROA |
| 203.135.158.0/23 | NTTCOM, RADB | No ROA |
| 2400:db00::/32 | APNIC | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.