Network · data from 2026-11-12
AS201476 Wolfnet ISP Alliance a.s.
Registry name: Wolfnet ISP Alliance a.s., CZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201476, 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:112c::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 5.183.12.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 94.138.116.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 94.138.120.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.73.100.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.73.104.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.73.108.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.167.184.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 77.104.194.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.104.210.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.104.216.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.104.223.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.104.240.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.104.245.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a03:4260::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS201476 isn't in PeeringDB, where networks name their 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 23 are in fix.csv.
- ROA: none1
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:678:112c::/48 | No ROA covers it. Add a ROA for AS201476, maxLength 48. |
Route objects not announced
Route objects with origin AS201476 whose prefix no peer sees AS201476 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.183.12.0/24 | RIPE | Invalid: maxLength |
| 5.183.13.0/24 | RIPE | Invalid: maxLength |
| 5.183.14.0/24 | RIPE | Invalid: maxLength |
| 5.183.15.0/24 | RIPE | Invalid: maxLength |
| 94.138.123.0/24 | RIPE | Invalid: maxLength |
| 185.73.100.0/24 | RIPE | Valid |
| 185.73.101.0/24 | RIPE | Valid |
| 185.73.102.0/24 | RIPE | Valid |
| 185.73.103.0/24 | RIPE | Valid |
| 185.73.104.0/24 | RIPE | Valid |
| 185.73.105.0/24 | RIPE | Valid |
| 185.73.106.0/24 | RIPE | Valid |
| 185.73.107.0/24 | RIPE | Valid |
| 185.73.108.0/24 | RIPE | Valid |
| 185.73.109.0/24 | RIPE | Valid |
| 185.73.110.0/24 | RIPE | Valid |
| 185.73.111.0/24 | RIPE | Valid |
| 185.167.184.0/24 | RIPE | Valid |
| 185.167.185.0/24 | RIPE | Valid |
| 185.167.186.0/24 | RIPE | Valid |
| 185.167.187.0/24 | RIPE | Valid |
| 2a03:4260::/32 | RIPE | Valid |
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.