Network · data from 2026-11-12
AS49863 LITE-TELECOM-AS Lite-Telecom Limited
Registry name: LITE-TELECOM-AS Lite-Telecom Limited, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49863, 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.
| 109.72.240.0/20 | No ROA | RIR databaseRIPE | 671 100% |
| 109.72.240.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 109.72.244.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 109.72.248.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 109.72.248.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.91.180.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.91.180.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.91.182.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 2a0e:e6c0:c000::/36 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS49863 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 9 are in fix.csv.
- ROA: none8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.72.240.0/20 | No ROA covers it. Add a ROA for AS49863, maxLength 20. |
| ROA: none | 109.72.240.0/22 | No ROA covers it. Add a ROA for AS49863, maxLength 22. |
| ROA: none | 109.72.244.0/22 | No ROA covers it. Add a ROA for AS49863, maxLength 22. |
| ROA: none | 109.72.248.0/21 | No ROA covers it. Add a ROA for AS49863, maxLength 21. |
| ROA: none | 109.72.248.0/24 | No ROA covers it. Add a ROA for AS49863, maxLength 24. |
| ROA: none | 185.91.180.0/22 | No ROA covers it. Add a ROA for AS49863, maxLength 22. |
| ROA: none | 185.91.180.0/24 | No ROA covers it. Add a ROA for AS49863, maxLength 24. |
| ROA: none | 185.91.182.0/23 | No ROA covers it. Add a ROA for AS49863, maxLength 23. |
Route objects not announced
Route objects with origin AS49863 whose prefix no peer sees AS49863 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.72.241.0/24 | 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.