Network · data from 2026-11-12
AS44229 DTST_AS_01 nfon AG
Registry name: DTST_AS_01 nfon AG, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44229, 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.
| 92.60.208.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 2a00:a780::/32 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS44229 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 14 are in fix.csv.
- ROA: none2
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 92.60.208.0/22 | No ROA covers it. Add a ROA for AS44229, maxLength 22. |
| ROA: none | 2a00:a780::/32 | No ROA covers it. Add a ROA for AS44229, maxLength 32. |
Route objects not announced
Route objects with origin AS44229 whose prefix no peer sees AS44229 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 92.60.208.0/24 | RIPE | No ROA |
| 92.60.209.0/24 | RIPE | No ROA |
| 92.60.210.0/24 | RIPE | No ROA |
| 92.60.212.0/22 | RIPE | No ROA |
| 92.60.216.0/22 | RIPE | No ROA |
| 92.60.220.0/22 | RIPE | No ROA |
| 134.101.8.0/21 | RIPE | No ROA |
| 178.20.0.0/21 | RIPE | No ROA |
| 185.58.168.0/22 | RIPE | No ROA |
| 2a00:a780::/34 | RIPE | No ROA |
| 2a00:a780:4::/48 | RIPE | No ROA |
| 2a00:a780:800::/40 | RIPE | 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.