Network · data from 2026-11-12
AS50911 AS-ELECTRON LLC "Electron-Telecom"
Registry name: AS-ELECTRON LLC "Electron-Telecom", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50911, 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.
| 176.112.224.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 176.112.240.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 185.170.52.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.170.54.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 194.28.28.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 194.28.30.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 176.112.224.0/19 | No ROA | RIR databaseRIPE | 671 100% |
| 176.112.224.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 176.112.240.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 185.170.52.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.170.52.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.28.28.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 194.28.31.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a0a:8300::/29 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS50911 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 38 are in fix.csv.
- ROA: none14
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 176.112.224.0/20 | No ROA covers it. Add a ROA for AS50911, maxLength 20. |
| ROA: none | 176.112.240.0/20 | No ROA covers it. Add a ROA for AS50911, maxLength 20. |
| ROA: none | 185.170.52.0/23 | No ROA covers it. Add a ROA for AS50911, maxLength 23. |
| ROA: none | 185.170.54.0/23 | No ROA covers it. Add a ROA for AS50911, maxLength 23. |
| ROA: none | 194.28.28.0/23 | No ROA covers it. Add a ROA for AS50911, maxLength 23. |
| ROA: none | 194.28.30.0/23 | No ROA covers it. Add a ROA for AS50911, maxLength 23. |
| ROA: none | 176.112.224.0/19 | No ROA covers it. Add a ROA for AS50911, maxLength 19. |
| ROA: none | 176.112.224.0/21 | No ROA covers it. Add a ROA for AS50911, maxLength 21. |
| ROA: none | 176.112.240.0/21 | No ROA covers it. Add a ROA for AS50911, maxLength 21. |
| ROA: none | 185.170.52.0/22 | No ROA covers it. Add a ROA for AS50911, maxLength 22. |
| ROA: none | 185.170.52.0/24 | No ROA covers it. Add a ROA for AS50911, maxLength 24. |
| ROA: none | 194.28.28.0/22 | No ROA covers it. Add a ROA for AS50911, maxLength 22. |
| ROA: none | 194.28.31.0/24 | No ROA covers it. Add a ROA for AS50911, maxLength 24. |
| ROA: none | 2a0a:8300::/29 | No ROA covers it. Add a ROA for AS50911, maxLength 29. |
Route objects not announced
Route objects with origin AS50911 whose prefix no peer sees AS50911 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 176.112.224.0/23 | RIPE | No ROA |
| 176.112.226.0/23 | RIPE | No ROA |
| 176.112.228.0/23 | RIPE | No ROA |
| 176.112.230.0/23 | RIPE | No ROA |
| 176.112.232.0/21 | RIPE | No ROA |
| 176.112.232.0/23 | RIPE | No ROA |
| 176.112.234.0/23 | RIPE | No ROA |
| 176.112.236.0/23 | RIPE | No ROA |
| 176.112.238.0/23 | RIPE | No ROA |
| 176.112.240.0/23 | RIPE | No ROA |
| 176.112.242.0/23 | RIPE | No ROA |
| 176.112.244.0/23 | RIPE | No ROA |
| 176.112.246.0/23 | RIPE | No ROA |
| 176.112.248.0/21 | RIPE | No ROA |
| 176.112.248.0/23 | RIPE | No ROA |
| 176.112.250.0/23 | RIPE | No ROA |
| 176.112.252.0/23 | RIPE | No ROA |
| 176.112.254.0/23 | RIPE | No ROA |
| 185.170.53.0/24 | RIPE | No ROA |
| 185.170.54.0/24 | RIPE | No ROA |
| 185.170.55.0/24 | RIPE | No ROA |
| 194.28.28.0/24 | RIPE | No ROA |
| 194.28.29.0/24 | RIPE | No ROA |
| 194.28.30.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.