Network · data from 2026-11-12
AS50477 SV-EN-AS Svyaz-Energo Ltd.
Registry name: SV-EN-AS Svyaz-Energo Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50477, 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.
| 5.149.200.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 5.149.204.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 5.149.204.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.149.205.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.149.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.19.112.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 46.19.114.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.19.115.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.19.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 109.236.208.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 109.236.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.236.211.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.236.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 109.236.216.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 134.19.144.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 134.19.152.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 134.19.153.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 134.19.154.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 134.19.154.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 134.19.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 134.19.156.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 178.57.56.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.34.244.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.188.96.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.188.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.58.168.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.58.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.58.184.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 5.149.201.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a04:6007::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:6000::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a04:6006::/32 | Valid | RIR databaseRIPE | 547 86% |
AS-SET
AS50477 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 23 are in fix.csv.
- Route object: not announced23
Route objects not announced
Route objects with origin AS50477 whose prefix no peer sees AS50477 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.149.207.0/24 | RIPE | Invalid: maxLength |
| 46.19.112.0/21 | RIPE | No ROA |
| 46.19.112.0/22 | RIPE | No ROA |
| 46.19.114.0/23 | RIPE | No ROA |
| 109.236.208.0/20 | RIPE | No ROA |
| 109.236.208.0/21 | RIPE | No ROA |
| 109.236.216.0/22 | RIPE | Invalid: maxLength |
| 134.19.144.0/20 | RIPE | No ROA |
| 134.19.144.0/23 | RIPE | Invalid: maxLength |
| 134.19.144.0/24 | RIPE | Invalid: maxLength |
| 134.19.145.0/24 | RIPE | Invalid: maxLength |
| 134.19.146.0/23 | RIPE | Invalid: maxLength |
| 134.19.148.0/22 | RIPE | Invalid: maxLength |
| 134.19.149.0/24 | RIPE | Invalid: maxLength |
| 134.19.155.0/24 | RIPE | Invalid: maxLength |
| 134.19.158.0/23 | RIPE | Invalid: maxLength |
| 185.34.244.0/23 | RIPE | Invalid: maxLength |
| 185.34.246.0/23 | RIPE | Invalid: maxLength |
| 185.188.96.0/23 | RIPE | Invalid: maxLength |
| 185.188.97.0/24 | RIPE | Invalid: maxLength |
| 185.188.98.0/23 | RIPE | Invalid: maxLength |
| 185.188.98.0/24 | RIPE | Invalid: maxLength |
| 185.188.99.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.