Network · data from 2026-11-12
AS8520 DUNKEL SITS Deutschland GmbH
Registry name: DUNKEL SITS Deutschland GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8520, 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.
| 88.215.192.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 185.126.212.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:14c0::/33 | No ROA | RIR databaseRIPE | 635 100% |
| 62.93.212.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 62.93.246.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS8520 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 18 are in fix.csv.
- ROA: none3
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 88.215.192.0/19 | No ROA covers it. Add a ROA for AS8520, maxLength 19. |
| ROA: none | 185.126.212.0/22 | No ROA covers it. Add a ROA for AS8520, maxLength 22. |
| ROA: none | 2001:14c0::/33 | No ROA covers it. Add a ROA for AS8520, maxLength 33. |
Route objects not announced
Route objects with origin AS8520 whose prefix no peer sees AS8520 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 88.215.224.0/19 | RIPE | No ROA |
| 88.215.224.0/20 | RIPE | No ROA |
| 88.215.240.0/20 | RIPE | No ROA |
| 192.76.141.0/24 | RIPE | No ROA |
| 194.55.246.0/23 | RIPE | No ROA |
| 194.55.246.0/24 | RIPE | No ROA |
| 194.55.247.0/24 | RIPE | No ROA |
| 194.55.254.0/24 | RIPE | No ROA |
| 195.246.160.0/19 | RIPE | No ROA |
| 195.246.160.0/20 | RIPE | No ROA |
| 195.246.176.0/20 | RIPE | No ROA |
| 195.246.188.0/24 | RIPE | No ROA |
| 2001:14c0:8000::/33 | RIPE | No ROA |
| 2001:14c0:8000::/34 | RIPE | No ROA |
| 2001:14c0:c000::/34 | 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.