Network · data from 2026-11-12
AS205376 DINOEX Dirk Meyer
Registry name: DINOEX Dirk Meyer, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205376, 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.
| 2001:678:303::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 185.220.148.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.220.150.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.141.67.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.45.71.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.120.16.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 2a0b:f847::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:2e58::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:f840::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS205376 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 4 are in fix.csv.
- ROA: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:678:303::/48 | No ROA covers it. Add a ROA for AS205376, maxLength 48. |
Route objects not announced
Route objects with origin AS205376 whose prefix no peer sees AS205376 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.220.149.0/24 | RIPE | Valid |
| 185.220.151.0/24 | RIPE | Valid |
| 2a0b:f841::/32 | 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.