Network · data from 2026-11-12
AS206998 New Relic (AS206998)
Registry name: NEW-2 NEW RELIC INTERNATIONAL LIMITED, IE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206998, 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.32.9.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2a0d:8000::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 185.221.85.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS206998's PeeringDB record names no 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: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 212.32.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a0d:8000::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206998 whose prefix no peer sees AS206998 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.221.84.0/22 | RADB | No ROA |
| 185.221.86.0/24 | RADB, RIPE | Valid |
| 212.32.4.0/24 | RIPE | Valid |
| 212.32.5.0/24 | RIPE | Valid |
| 212.32.8.0/24 | RADB | Valid |
| 2a0d:8000::/29 | 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.