Network · data from 2026-11-12
AS201041 OBLTELECOM-AS Obltelecom LLC
Registry name: OBLTELECOM-AS Obltelecom LLC, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201041, 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.235.102.0/24 | No ROA | Other origin only | 672 100% |
| 213.110.124.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 91.207.104.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 93.171.163.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.110.127.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.229.60.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS201041 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 5 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.235.102.0/24 | No ROA covers it. Add a ROA for AS201041, maxLength 24. |
| Route object: none | 91.235.102.0/24 | Route objects for it name AS57830. Add a route object with origin AS201041 in the RIR database for the space. |
| ROA: none | 213.110.124.0/24 | No ROA covers it. Add a ROA for AS201041, maxLength 24. |
Route objects not announced
Route objects with origin AS201041 whose prefix no peer sees AS201041 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.207.104.0/24 | RIPE | Invalid: maxLength |
| 91.207.105.0/24 | RIPE | Invalid: maxLength |
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.