Network · data from 2026-11-12
AS48209 LANCRONIX-AS OOO LANCRONIX
Registry name: LANCRONIX-AS OOO LANCRONIX, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48209, 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.
| 188.75.0.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 188.75.5.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 188.75.6.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 188.75.11.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 188.75.32.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 188.75.40.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 188.75.48.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 217.79.224.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 217.79.228.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 217.79.231.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.79.232.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 217.79.234.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 217.79.236.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 188.75.31.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 177.111.60.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS48209 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 21 are in fix.csv.
- ROA: none14
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.75.0.0/19 | No ROA covers it. Add a ROA for AS48209, maxLength 19. |
| ROA: none | 188.75.5.0/24 | No ROA covers it. Add a ROA for AS48209, maxLength 24. |
| ROA: none | 188.75.6.0/23 | No ROA covers it. Add a ROA for AS48209, maxLength 23. |
| ROA: none | 188.75.11.0/24 | No ROA covers it. Add a ROA for AS48209, maxLength 24. |
| ROA: none | 188.75.32.0/21 | No ROA covers it. Add a ROA for AS48209, maxLength 21. |
| ROA: none | 188.75.40.0/24 | No ROA covers it. Add a ROA for AS48209, maxLength 24. |
| ROA: none | 188.75.48.0/20 | No ROA covers it. Add a ROA for AS48209, maxLength 20. |
| ROA: none | 217.79.224.0/20 | No ROA covers it. Add a ROA for AS48209, maxLength 20. |
| ROA: none | 217.79.228.0/23 | No ROA covers it. Add a ROA for AS48209, maxLength 23. |
| ROA: none | 217.79.231.0/24 | No ROA covers it. Add a ROA for AS48209, maxLength 24. |
| ROA: none | 217.79.232.0/23 | No ROA covers it. Add a ROA for AS48209, maxLength 23. |
| ROA: none | 217.79.234.0/23 | No ROA covers it. Add a ROA for AS48209, maxLength 23. |
| ROA: none | 217.79.236.0/23 | No ROA covers it. Add a ROA for AS48209, maxLength 23. |
| ROA: none | 188.75.31.0/24 | No ROA covers it. Add a ROA for AS48209, maxLength 24. |
Route objects not announced
Route objects with origin AS48209 whose prefix no peer sees AS48209 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.194.206.0/24 | AFRINIC, RADB | Valid |
| 154.194.243.0/24 | AFRINIC, RADB | Valid |
| 154.196.244.0/24 | AFRINIC, RADB | Valid |
| 188.75.30.0/23 | RIPE | No ROA |
| 188.75.30.0/24 | RIPE | No ROA |
| 217.79.224.0/23 | RIPE | No ROA |
| 217.79.238.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.