Network · data from 2026-11-12
AS29031 LTC Lugansk Telephone Company LLC
Registry name: LTC Lugansk Telephone Company LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29031, 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.
| 195.69.203.0/24 | Invalid: maxLength | Nonecovered by 195.69.200.0/22 | 82 12% |
| 195.69.200.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 91.201.108.0/23 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 91.201.109.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 91.201.110.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 91.201.111.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 193.239.24.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 193.239.25.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 193.239.26.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 193.239.27.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 195.3.134.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 195.3.135.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS29031 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 11 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 195.69.203.0/24 | ROA 195.69.200.0/22 AS29031 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 195.69.203.0/24. |
| Route object: none | 195.69.203.0/24 | No route object for it. A route object for 195.69.200.0/22 with origin AS29031 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29031 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29031 whose prefix no peer sees AS29031 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.201.108.0/22 | RIPE | Valid |
| 91.201.108.0/24 | RIPE | Valid |
| 91.201.110.0/23 | RIPE | Invalid: maxLength |
| 193.239.24.0/22 | RIPE | No ROA |
| 195.3.132.0/22 | RIPE | No ROA |
| 195.3.132.0/23 | RIPE | Valid |
| 195.3.132.0/24 | RIPE | Invalid: maxLength |
| 195.3.133.0/24 | RIPE | Invalid: maxLength |
| 195.3.134.0/23 | RIPE | Valid |
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.