Network · data from 2026-11-12
AS55639 ASIAWEB-SERVICE-HK - Asia Web Service Ltd
Registry name: ASIAWEB-SERVICE-HK - Asia Web Service Ltd, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55639, 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.
| 202.53.148.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.53.150.0/23 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.15.28.0/22 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 180.235.132.0/22 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.52.136.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 2401:c700::/44 | No ROA | RIR databaseAPNIC | 636 100% |
| 2401:c700:10::/44 | No ROA | RIR databaseAPNIC | 636 100% |
| 2401:c700:20::/44 | No ROA | RIR databaseAPNIC | 636 100% |
| 111.90.157.0/24 | Valid | RIR databaseAPNIC | 666 99% |
AS-SET
AS55639 isn't in PeeringDB, where networks name their 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 27 are in fix.csv.
- ROA: none8
- Route object: RIR2
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.53.148.0/23 | No ROA covers it. Add a ROA for AS55639, maxLength 23. |
| Route object: RIR | 202.53.148.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.53.150.0/23 | No ROA covers it. Add a ROA for AS55639, maxLength 23. |
| Route object: RIR | 202.53.150.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.15.28.0/22 | No ROA covers it. Add a ROA for AS55639, maxLength 22. |
| ROA: none | 180.235.132.0/22 | No ROA covers it. Add a ROA for AS55639, maxLength 22. |
| ROA: none | 202.52.136.0/24 | No ROA covers it. Add a ROA for AS55639, maxLength 24. |
| ROA: none | 2401:c700::/44 | No ROA covers it. Add a ROA for AS55639, maxLength 44. |
| ROA: none | 2401:c700:10::/44 | No ROA covers it. Add a ROA for AS55639, maxLength 44. |
| ROA: none | 2401:c700:20::/44 | No ROA covers it. Add a ROA for AS55639, maxLength 44. |
Route objects not announced
Route objects with origin AS55639 whose prefix no peer sees AS55639 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.15.28.0/23 | NTTCOM, RADB | No ROA |
| 103.15.28.0/24 | NTTCOM, RADB | No ROA |
| 103.15.29.0/24 | NTTCOM, RADB | No ROA |
| 103.15.30.0/23 | NTTCOM, RADB | No ROA |
| 103.15.30.0/24 | NTTCOM, RADB | No ROA |
| 103.15.31.0/24 | NTTCOM, RADB | No ROA |
| 180.235.132.0/23 | NTTCOM, RADB | No ROA |
| 180.235.132.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 180.235.133.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 180.235.134.0/23 | APNIC, NTTCOM, RADB | No ROA |
| 180.235.134.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 180.235.135.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 202.53.148.0/22 | APNIC, NTTCOM, RADB | No ROA |
| 202.53.148.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 202.53.149.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 202.53.150.0/24 | APNIC, NTTCOM, RADB | No ROA |
| 202.53.151.0/24 | APNIC, NTTCOM, RADB | 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.