Network · data from 2026-11-12
AS396930 OPUS-INTERACTIVE-VA1 - Opus Interactive
Registry name: OPUS-INTERACTIVE-VA1 - Opus Interactive, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS396930, 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.
| 198.176.207.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2605:1e80:3000::/36 | No ROA | RIR databaseARIN | 633 100% |
| 144.208.116.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 148.51.132.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.48.82.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS396930 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: none2
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 198.176.207.0/24 | No ROA covers it. Add a ROA for AS396930, maxLength 24. |
| Route object: RIR | 198.176.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2605:1e80:3000::/36 | No ROA covers it. Add a ROA for AS396930, maxLength 36. |
Route objects not announced
Every route object with origin AS396930 is announced.
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.