Network · data from 2026-11-12
AS15935 ha-vel internet s.r.o.
Registry name: HA-VEL-LOCAL-AS ha-vel internet s.r.o., CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15935, 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.
| 2001:678:1064::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 217.66.178.0/24 | Valid | Nonecovered by 217.66.160.0/19 | 279 41% |
| 217.66.179.0/24 | Valid | Nonecovered by 217.66.160.0/19 | 279 41% |
| 217.66.190.0/24 | Valid | Nonecovered by 217.66.160.0/19 | 279 41% |
| 95.173.64.0/23 | Valid | Nonecovered by 95.173.64.0/19 | 262 39% |
| 217.66.191.0/24 | Valid | Nonecovered by 217.66.160.0/19 | 262 39% |
| 45.146.108.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 81.30.224.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.48.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 95.173.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 109.238.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.188.102.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.195.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 217.66.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 2001:678:368::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:570::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS15935: RIPE::AS-HA-VEL-COMPLETE. 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 (AS15935 isn't in the set, or no route object for AS15935 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 | AS15935 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-HA-VEL-COMPLETE | RIPE | 65 | 12 | Yes | 0 |
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 8 are in fix.csv.
- ROA: none1
- Route object: none5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:678:1064::/48 | No ROA covers it. Add a ROA for AS15935, maxLength 48. |
| Route object: none | 217.66.178.0/24 | No route object for it. A route object for 217.66.160.0/19 with origin AS15935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15935 in the RIR database for the space. |
| Route object: none | 217.66.179.0/24 | No route object for it. A route object for 217.66.160.0/19 with origin AS15935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15935 in the RIR database for the space. |
| Route object: none | 217.66.190.0/24 | No route object for it. A route object for 217.66.160.0/19 with origin AS15935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15935 in the RIR database for the space. |
| Route object: none | 95.173.64.0/23 | No route object for it. A route object for 95.173.64.0/19 with origin AS15935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15935 in the RIR database for the space. |
| Route object: none | 217.66.191.0/24 | No route object for it. A route object for 217.66.160.0/19 with origin AS15935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15935 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15935 whose prefix no peer sees AS15935 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:67c:26c::/48 | RIPE | Invalid: origin |
| 2001:67c:1bc4::/48 | RIPE | Invalid: origin |
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.