Network · data from 2026-11-12
AS216063 TWENTYFOURFIRE
Registry name: TWENTYFOURFIRE 24fire GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216063, 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.
| 2a12:de40:20::/48 | No ROA | RIR databaseRIPE | 634 100% |
| 2a12:de40:21::/48 | No ROA | RIR databaseRIPE | 634 100% |
| 2a12:de40:200::/40 | No ROA | RIR databaseRIPE | 634 100% |
| 62.129.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 62.129.151.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.117.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.10.226.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.10.227.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.56.244.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.84.196.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.137.202.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.147.7.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a01:bc1::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a01:bc2::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS216063'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 4 are in fix.csv.
- ROA: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a12:de40:20::/48 | No ROA covers it. Add a ROA for AS216063, maxLength 48. |
| ROA: none | 2a12:de40:21::/48 | No ROA covers it. Add a ROA for AS216063, maxLength 48. |
| ROA: none | 2a12:de40:200::/40 | No ROA covers it. Add a ROA for AS216063, maxLength 40. |
Route objects not announced
Route objects with origin AS216063 whose prefix no peer sees AS216063 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a01:bc0::/29 | RIPE | 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.