Network · data from 2026-11-12
AS204666 Jiri Tlapak
Registry name: TLAPNET-CZ Jiri Tlapak, CZ · PeeringDB
38IPv4 routes
100.0% RPKI valid · 86.8% with a route object
11IPv6 routes
100.0% RPKI valid · 90.9% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
6 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
13Route objects not announced
registered with origin AS204666, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS204666, 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.
| 185.64.220.0/24 | Valid | Other origin onlycovered by 185.64.220.0/22 | 673 100% |
| 185.74.60.0/24 | Valid | Other origin only | 673 100% |
| 185.87.140.0/22 | Valid | Other origin only | 673 100% |
| 185.188.100.0/24 | Valid | Other origin only | 673 100% |
| 185.87.143.0/24 | Valid | Other origin onlycovered by 185.87.142.0/23 | 672 100% |
| 2a03:d840:fe02::/48 | Valid | Nonecovered by 2a03:d840::/32 | 635 100% |
| 5.59.102.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 37.221.240.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 45.153.192.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.255.88.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.224.90.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.119.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.19.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.64.220.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.64.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.87.142.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.97.24.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.97.24.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.97.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.97.26.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.188.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.188.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.230.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.243.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 213.108.162.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 37.221.241.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.242.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.243.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.245.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.247.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.248.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.250.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.251.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.153.192.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.153.194.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.153.195.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.108.162.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.249.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a03:d840::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:c740::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a04:f940::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a05:aa00::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a06:400::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0a:10c0::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0d:1880::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0d:3140::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:9300::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:fec0::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS204666's PeeringDB record names no 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 19 are in fix.csv.
- Route object: none6
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.64.220.0/24 | Route objects for it name AS201761. A route object for 185.64.220.0/22 with origin AS204666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204666 in the RIR database for the space. |
| Route object: none | 185.74.60.0/24 | Route objects for it name AS198668. Add a route object with origin AS204666 in the RIR database for the space. |
| Route object: none | 185.87.140.0/22 | Route objects for it name AS198668. Add a route object with origin AS204666 in the RIR database for the space. |
| Route object: none | 185.188.100.0/24 | Route objects for it name AS198668, AS206270. Add a route object with origin AS204666 in the RIR database for the space. |
| Route object: none | 185.87.143.0/24 | Route objects for it name AS198668. A route object for 185.87.142.0/23 with origin AS204666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204666 in the RIR database for the space. |
| Route object: none | 2a03:d840:fe02::/48 | No route object for it. A route object for 2a03:d840::/32 with origin AS204666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204666 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS204666 whose prefix no peer sees AS204666 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.221.240.0/24 | RIPE | Valid |
| 37.221.244.0/24 | RIPE | Valid |
| 37.221.246.0/24 | RIPE | Valid |
| 37.221.253.0/24 | RIPE | Valid |
| 37.221.254.0/24 | RIPE | Valid |
| 37.221.255.0/24 | RIPE | Valid |
| 91.224.91.0/24 | RIPE | Valid |
| 185.19.0.0/24 | RIPE | Valid |
| 185.19.1.0/24 | RIPE | Valid |
| 185.19.2.0/24 | RIPE | Valid |
| 185.19.3.0/24 | RIPE | Valid |
| 213.108.163.0/24 | RIPE | Valid |
| 2a03:d840::/29 | RIPE | 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.