Network · data from 2026-11-12
AS12871 NL-ix_Enterprise_Services KPN B.V.
Registry name: NL-ix_Enterprise_Services KPN B.V., NL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12871, 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.
| 146.104.251.0/24 | No ROA | RIR databaseRIPE | 30 4%low visibility |
| 94.229.51.0/24 | Valid | RIR databaseRIPE | 434 64% |
| 37.188.67.0/24 | Valid | RIR databaseRIPE | 126 19% |
| 37.188.65.0/24 | Valid | RIR databaseRIPE | 124 18% |
| 37.188.66.0/24 | Valid | RIR databaseRIPE | 124 18% |
| 37.188.69.0/24 | Valid | RIR databaseRIPE | 124 18% |
| 37.188.76.0/24 | Valid | RIR databaseRIPE | 11 2%low visibility |
| 94.229.48.0/24 | Valid | RIR databaseRIPE | 3 0%low visibility |
AS-SET
AS12871 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 13 are in fix.csv.
- ROA: none1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 146.104.251.0/24 | No ROA covers it. Add a ROA for AS12871, maxLength 24. |
Route objects not announced
Route objects with origin AS12871 whose prefix no peer sees AS12871 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.188.64.0/24 | RIPE | Valid |
| 37.188.68.0/24 | RIPE | Valid |
| 37.188.70.0/24 | RIPE | Valid |
| 37.188.71.0/24 | RIPE | Valid |
| 37.188.72.0/24 | RIPE | Valid |
| 37.188.73.0/24 | RIPE | Valid |
| 37.188.77.0/24 | RIPE | Valid |
| 37.188.78.0/24 | RIPE | Valid |
| 94.229.49.0/24 | RIPE | Valid |
| 94.229.50.0/24 | RIPE | Valid |
| 145.78.29.0/24 | RIPE | Valid |
| 2002::/16 | RIPE-NONAUTH | 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.