Network · data from 2026-11-12
AS207033 DTnet
Registry name: DTnet DTnet Adam Tarkowski Aneta Wyrwas s.c., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207033, 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.
| 78.159.84.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.55.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 188.114.68.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.65.171.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS207033's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS207033 is announced.
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.