Network · data from 2026-11-12
AS8082 WORLDSITE - Worldsite Networks
Registry name: WORLDSITE - Worldsite Networks, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8082, 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.
| 209.134.0.0/19 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS8082 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.
- ROA: none1
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.134.0.0/19 | No ROA covers it. Add a ROA for AS8082, maxLength 19. |
| Route object: RIR | 209.134.0.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS8082 whose prefix no peer sees AS8082 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.211.214.0/23 | ALTDB | No ROA |
| 206.82.244.0/23 | ALTDB | No ROA |
| 207.151.235.0/24 | ALTDB | No ROA |
| 207.151.236.0/24 | ALTDB | No ROA |
| 209.134.0.0/20 | RADB | No ROA |
| 209.134.16.0/20 | 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.