Network · data from 2026-11-12
AS35199 ENFORMATEL
Registry name: ENFORMATEL-AS Enformatel Sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35199, 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.207.202.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 91.223.64.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 178.212.152.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 178.219.16.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.214.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.226.98.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.19.164.0/22 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS35199'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 14 are in fix.csv.
- ROA: none3
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.207.202.0/23 | No ROA covers it. Add a ROA for AS35199, maxLength 23. |
| ROA: none | 91.223.64.0/24 | No ROA covers it. Add a ROA for AS35199, maxLength 24. |
| ROA: none | 178.212.152.0/21 | No ROA covers it. Add a ROA for AS35199, maxLength 21. |
Route objects not announced
Route objects with origin AS35199 whose prefix no peer sees AS35199 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.174.22.0/24 | RIPE | Valid |
| 178.219.16.0/24 | RIPE | Invalid: maxLength |
| 178.219.17.0/24 | RIPE | Invalid: maxLength |
| 178.219.18.0/24 | RIPE | Invalid: maxLength |
| 178.219.19.0/24 | RIPE | Invalid: maxLength |
| 193.19.164.0/24 | RIPE | Valid |
| 193.19.165.0/24 | RIPE | Valid |
| 193.19.166.0/24 | RIPE | Valid |
| 193.19.167.0/24 | RIPE | Valid |
| 2a10:f781:10:47cf::/64 | RIPE | No ROA |
| 2a13:2801:2000::/36 | 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.