Network · data from 2026-11-12
AS206314 STOWARZYSZENIE ZST
Registry name: AS-STOWARZYSZENIE-ZST STOWARZYSZENIE ZST, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206314, 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.
| 91.204.152.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 91.228.156.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 91.238.240.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 193.106.152.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 91.226.236.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 91.238.172.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 91.241.24.0/22 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS206314'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 10 are in fix.csv.
- ROA: none4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.204.152.0/22 | No ROA covers it. Add a ROA for AS206314, maxLength 22. |
| ROA: none | 91.228.156.0/24 | No ROA covers it. Add a ROA for AS206314, maxLength 24. |
| ROA: none | 91.238.240.0/22 | No ROA covers it. Add a ROA for AS206314, maxLength 22. |
| ROA: none | 193.106.152.0/22 | No ROA covers it. Add a ROA for AS206314, maxLength 22. |
Route objects not announced
Route objects with origin AS206314 whose prefix no peer sees AS206314 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.228.156.0/22 | RIPE | No ROA |
| 91.228.159.0/24 | RIPE | No ROA |
| 91.238.172.0/24 | RIPE | Invalid: maxLength |
| 91.238.173.0/24 | RIPE | Invalid: maxLength |
| 91.238.174.0/24 | RIPE | Invalid: maxLength |
| 2a10:f781:10:23b6::/64 | 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.