Network · data from 2026-11-12
AS202923 STW-ACCESS ServeTheWorld AS
Registry name: STW-ACCESS ServeTheWorld AS, NO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202923, 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.
| 212.135.16.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 46.202.97.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 82.29.49.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 178.83.143.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
AS-SET
AS202923 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 8 are in fix.csv.
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 212.135.16.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202923 whose prefix no peer sees AS202923 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.22.143.0/24 | RADB, RIPE | Valid |
| 82.22.157.0/24 | RADB, RIPE | Valid |
| 82.29.70.0/24 | RADB, RIPE | Valid |
| 151.244.62.0/23 | RADB, RIPE | Valid |
| 177.202.116.0/23 | RIPE | Valid |
| 212.114.48.0/23 | RADB, RIPE | Valid |
| 2001:470:296::/48 | ARIN | 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.