Network · data from 2026-11-12
AS152700 NUUK-AS-AP - NUUK COMMUNICATIONS PTE. LTD.
Registry name: NUUK-AS-AP - NUUK COMMUNICATIONS PTE. LTD., SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS152700, 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.
| 2602:ffe4:c17::/48 | No ROA | Other origin only | 635 100% |
AS-SET
AS152700 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 14 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:ffe4:c17::/48 | No ROA covers it. Add a ROA for AS152700, maxLength 48. |
| Route object: none | 2602:ffe4:c17::/48 | Route objects for it name AS21859. Add a route object with origin AS152700 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS152700 whose prefix no peer sees AS152700 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 14.192.49.0/24 | APNIC | Valid |
| 45.149.6.0/24 | RADB, RIPE | Valid |
| 45.157.137.0/24 | RADB, RIPE | Valid |
| 103.116.45.0/24 | APNIC | Valid |
| 103.120.12.0/24 | APNIC | Valid |
| 103.120.15.0/24 | APNIC | Valid |
| 103.136.148.0/24 | APNIC | Valid |
| 103.230.10.0/24 | APNIC | Valid |
| 203.32.30.0/23 | APNIC | Valid |
| 203.32.30.0/24 | APNIC | Valid |
| 203.32.31.0/24 | APNIC | Valid |
| 2001:df3:ae40::/48 | APNIC | Valid |
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.