Network · data from 2026-11-12
AS200415 NFORCE-US NForce Entertainment B.V.
Registry name: NFORCE-US NForce Entertainment B.V., NL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200415, 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.
| 185.114.31.0/24 | No ROA | Other origin only | 667 99% |
| 194.180.34.0/24 | Valid | None | 669 99% |
| 194.180.32.0/24 | Valid | None | 666 99% |
| 194.180.33.0/24 | Valid | None | 666 99% |
AS-SET
AS200415 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 5 are in fix.csv.
- ROA: none1
- Route object: none4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.114.31.0/24 | No ROA covers it. Add a ROA for AS200415, maxLength 24. |
| Route object: none | 185.114.31.0/24 | Route objects for it name AS23470. Add a route object with origin AS200415 in the RIR database for the space. |
| Route object: none | 194.180.34.0/24 | No route object for it. Add a route object with origin AS200415 in the RIR database for the space. |
| Route object: none | 194.180.32.0/24 | No route object for it. Add a route object with origin AS200415 in the RIR database for the space. |
| Route object: none | 194.180.33.0/24 | No route object for it. Add a route object with origin AS200415 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS200415 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.