Network · data from 2026-11-12
AS140939 TENPAGE-AS-AP - Tenpage Pte Ltd
Registry name: TENPAGE-AS-AP - Tenpage Pte Ltd, SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140939, 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.
| 103.92.16.0/24 | No ROA | None | 670 100% |
| 103.153.165.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
AS-SET
AS140939 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 3 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.92.16.0/24 | No ROA covers it. Add a ROA for AS140939, maxLength 24. |
| Route object: none | 103.92.16.0/24 | No route object for it. Add a route object with origin AS140939 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140939 whose prefix no peer sees AS140939 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df4:5180::/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.