Network · data from 2026-11-12
AS4883
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4883, 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.
| 70.47.76.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 70.47.84.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS4883 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 10 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 70.47.76.0/22 | No ROA covers it. Add a ROA for AS4883, maxLength 22. |
| Route object: RIR | 70.47.76.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 70.47.84.0/22 | No ROA covers it. Add a ROA for AS4883, maxLength 22. |
| Route object: RIR | 70.47.84.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4883 whose prefix no peer sees AS4883 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.31.14.0/24 | RADB | No ROA |
| 12.42.228.0/24 | RADB | No ROA |
| 12.148.123.0/24 | RADB | No ROA |
| 12.236.229.0/24 | RADB | No ROA |
| 38.109.119.0/24 | RADB | No ROA |
| 74.217.168.0/24 | 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.