Network · data from 2026-11-12
AS214319 blackpoint blackpoint GmbH
Registry name: blackpoint blackpoint GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214319, 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.
| 149.13.77.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 149.13.92.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.56.104.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.56.105.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.56.106.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.56.107.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2001:978:90f::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 213.198.78.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 213.198.91.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 185.125.143.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:e680::/38 | Valid | RIR databaseRIPE | 635 100% |
| 2a01:e680:fc00::/38 | Valid | RIR databaseRIPE | 635 100% |
| 2a01:e687:fc00::/38 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS214319 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 19 are in fix.csv.
- ROA: none7
- Route object: RIR9
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.13.77.0/24 | No ROA covers it. Add a ROA for AS214319, maxLength 24. |
| Route object: RIR | 149.13.77.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.13.92.0/24 | No ROA covers it. Add a ROA for AS214319, maxLength 24. |
| Route object: RIR | 149.13.92.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.56.104.0/24 | No ROA covers it. Add a ROA for AS214319, maxLength 24. |
| Route object: RIR | 154.56.104.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.56.105.0/24 | No ROA covers it. Add a ROA for AS214319, maxLength 24. |
| Route object: RIR | 154.56.105.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.56.106.0/24 | No ROA covers it. Add a ROA for AS214319, maxLength 24. |
| Route object: RIR | 154.56.106.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.56.107.0/24 | No ROA covers it. Add a ROA for AS214319, maxLength 24. |
| Route object: RIR | 154.56.107.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:978:90f::/48 | No ROA covers it. Add a ROA for AS214319, maxLength 48. |
| Route object: RIR | 2001:978:90f::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 213.198.78.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 213.198.91.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS214319 whose prefix no peer sees AS214319 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.56.104.0/22 | RADB | No ROA |
| 212.119.25.0/24 | NTTCOM | Valid |
| 2001:728:1010:300::/56 | NTTCOM | Valid |
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.