Network · data from 2026-11-12
AS200070 CZ.NIC, z.s.p.o. (AS200070)
Registry name: CZNIC-AS2 CZ.NIC, z.s.p.o., CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200070, 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.
| 193.29.206.0/24 | Valid | Other origin only | 134 20% |
| 2001:678:1::/48 | Valid | Other origin only | 85 13% |
| 194.0.14.0/24 | Valid | RIR databaseRIPE | 545 81% |
| 2001:678:11::/48 | Valid | RIR databaseRADB, RIPE | 531 83% |
| 212.237.229.0/24 | Valid | RIR databaseRIPE | 160 24% |
| 2001:148f:fffb::/48 | Valid | RIR databaseRIPE | 149 23% |
| 185.43.134.0/24 | Valid | RIR databaseRIPE | 69 10% |
| 2001:148f:fffd::/48 | Valid | RIR databaseRIPE | 67 11% |
| 2001:678:f::/48 | Valid | RIR databaseRIPE | 15 2%low visibility |
| 194.0.12.0/24 | Valid | RIR databaseRIPE | 11 2%low visibility |
AS-SET
PeeringDB's irr_as_set for AS200070: AS-CZNIC-TRANSIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS200070 isn't in the set, or no route object for AS200070 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS200070 in it | Not covered |
|---|---|---|---|---|---|
| AS-CZNIC-TRANSIT | RIPE | 15 | 1 | Yes | 2 |
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.
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 193.29.206.0/24 | Route objects for it name AS25192. Add a route object with origin AS200070 in the RIR database for the space. |
| Route object: none | 2001:678:1::/48 | Route objects for it name AS25192. Add a route object with origin AS200070 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS200070 whose prefix no peer sees AS200070 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.253.250.0/24 | RIPE-NONAUTH | No ROA |
| 2620:10a:80ba::/48 | RIPE-NONAUTH | 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.