Network · data from 2026-11-12
AS41046 Nej TV a.s.
Registry name: NEJTV-AS O2 Czech Republic, a.s., CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41046, 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.
| 77.242.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 81.200.48.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 81.200.48.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 81.200.56.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 82.114.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 178.72.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 178.72.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 178.72.224.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 2001:67c:2d90::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a07:b5c0::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS41046'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 AS41046 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.