Network · data from 2026-11-12
AS197217 Shentel
Registry name: Shentel_AS Shentel Sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197217, 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.200.78.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 91.217.40.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 91.217.161.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.88.224.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 195.248.88.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS197217'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 12 are in fix.csv.
- ROA: none5
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.200.78.0/23 | No ROA covers it. Add a ROA for AS197217, maxLength 23. |
| ROA: none | 91.217.40.0/23 | No ROA covers it. Add a ROA for AS197217, maxLength 23. |
| ROA: none | 91.217.161.0/24 | No ROA covers it. Add a ROA for AS197217, maxLength 24. |
| ROA: none | 194.88.224.0/23 | No ROA covers it. Add a ROA for AS197217, maxLength 23. |
| ROA: none | 195.248.88.0/24 | No ROA covers it. Add a ROA for AS197217, maxLength 24. |
Route objects not announced
Route objects with origin AS197217 whose prefix no peer sees AS197217 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.200.78.0/24 | RIPE | No ROA |
| 91.200.79.0/24 | RIPE | No ROA |
| 91.217.40.0/24 | RIPE | No ROA |
| 91.217.41.0/24 | RIPE | No ROA |
| 194.88.224.0/24 | RIPE | No ROA |
| 194.88.225.0/24 | RIPE | No ROA |
| 2a10:f781:10:1de6::/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.