Network · data from 2026-11-12
AS47114 ZlinNet
Registry name: ZLINNET SychrovNET s.r.o, CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47114, 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.
| 188.246.96.0/21 | No ROA | Nonecovered by 188.246.96.0/20 | 672 100% |
| 188.246.104.0/21 | No ROA | Nonecovered by 188.246.96.0/20 | 671 100% |
| 188.246.96.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 188.246.120.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 195.10.234.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 2a00:c580::/32 | No ROA | RIR databaseRIPE | 633 100% |
| 2a0d:db40::/29 | No ROA | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS47114: RIPE::RS-ZLINNET. 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 (AS47114 isn't in the set, or no route object for AS47114 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 | AS47114 in it | Not covered | |
|---|---|---|---|---|---|---|
| RIPE::RS-ZLINNET | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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 9 are in fix.csv.
- ROA: none7
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.246.96.0/21 | No ROA covers it. Add a ROA for AS47114, maxLength 21. |
| Route object: none | 188.246.96.0/21 | No route object for it. A route object for 188.246.96.0/20 with origin AS47114 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47114 in the RIR database for the space. |
| ROA: none | 188.246.104.0/21 | No ROA covers it. Add a ROA for AS47114, maxLength 21. |
| Route object: none | 188.246.104.0/21 | No route object for it. A route object for 188.246.96.0/20 with origin AS47114 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47114 in the RIR database for the space. |
| ROA: none | 188.246.96.0/20 | No ROA covers it. Add a ROA for AS47114, maxLength 20. |
| ROA: none | 188.246.120.0/21 | No ROA covers it. Add a ROA for AS47114, maxLength 21. |
| ROA: none | 195.10.234.0/23 | No ROA covers it. Add a ROA for AS47114, maxLength 23. |
| ROA: none | 2a00:c580::/32 | No ROA covers it. Add a ROA for AS47114, maxLength 32. |
| ROA: none | 2a0d:db40::/29 | No ROA covers it. Add a ROA for AS47114, maxLength 29. |
Route objects not announced
Every route object with origin AS47114 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.