Network · data from 2026-11-12
AS39101 PITEL Piter-telecom Ltd.
Registry name: PITEL Piter-telecom Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39101, 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.
| 185.250.128.0/24 | No ROA | Nonecovered by 185.250.128.0/23 | 671 100% |
| 80.254.16.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 185.250.128.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 80.254.17.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 80.254.19.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 80.254.16.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 185.250.128.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 185.250.130.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 80.254.23.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 2a00:cd00::/32 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS39101 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 13 are in fix.csv.
- ROA: none10
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.250.128.0/24 | No ROA covers it. Add a ROA for AS39101, maxLength 24. |
| Route object: none | 185.250.128.0/24 | No route object for it. A route object for 185.250.128.0/23 with origin AS39101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39101 in the RIR database for the space. |
| ROA: none | 80.254.16.0/20 | No ROA covers it. Add a ROA for AS39101, maxLength 20. |
| ROA: none | 185.250.128.0/22 | No ROA covers it. Add a ROA for AS39101, maxLength 22. |
| ROA: none | 80.254.17.0/24 | No ROA covers it. Add a ROA for AS39101, maxLength 24. |
| ROA: none | 80.254.19.0/24 | No ROA covers it. Add a ROA for AS39101, maxLength 24. |
| ROA: none | 80.254.16.0/21 | No ROA covers it. Add a ROA for AS39101, maxLength 21. |
| ROA: none | 185.250.128.0/23 | No ROA covers it. Add a ROA for AS39101, maxLength 23. |
| ROA: none | 185.250.130.0/23 | No ROA covers it. Add a ROA for AS39101, maxLength 23. |
| ROA: none | 80.254.23.0/24 | No ROA covers it. Add a ROA for AS39101, maxLength 24. |
| ROA: none | 2a00:cd00::/32 | No ROA covers it. Add a ROA for AS39101, maxLength 32. |
Route objects not announced
Route objects with origin AS39101 whose prefix no peer sees AS39101 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.254.24.0/21 | RIPE | No ROA |
| 2a00:cd00::/48 | 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.