Network · data from 2026-11-12
AS56377 MGSK-AS JSC "ER-Telecom Holding"
Registry name: MGSK-AS JSC "ER-Telecom Holding", RU · not in PeeringDB
17IPv4 routes
0.0% RPKI valid · 100.0% with a route object
3IPv6 routes
100.0% RPKI valid · 33.3% with a route object
0RPKI invalid
0 origin · 0 maxLength
17No ROA
2 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
29Route objects not announced
registered with origin AS56377, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS56377, 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.164.48.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.48.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.52.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.56.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.60.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 109.163.240.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 109.163.240.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 109.195.208.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 109.195.220.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.215.192.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 176.215.192.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.215.200.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.215.204.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.215.208.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 176.215.208.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.215.212.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.187.231.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a02:2698:402a::/48 | Valid | Nonecovered by 2a02:2698:4000::/38 | 635 100% |
| 2a02:2698:402b::/48 | Valid | Nonecovered by 2a02:2698:4000::/38 | 635 100% |
| 2a02:2698:4000::/38 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS56377 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 48 are in fix.csv.
- ROA: none17
- Route object: none2
- Route object: not announced29
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.164.48.0/20 | No ROA covers it. Add a ROA for AS56377, maxLength 20. |
| ROA: none | 5.164.48.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 5.164.52.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 5.164.56.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 5.164.60.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 109.163.240.0/21 | No ROA covers it. Add a ROA for AS56377, maxLength 21. |
| ROA: none | 109.163.240.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 109.195.208.0/20 | No ROA covers it. Add a ROA for AS56377, maxLength 20. |
| ROA: none | 109.195.220.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 176.215.192.0/20 | No ROA covers it. Add a ROA for AS56377, maxLength 20. |
| ROA: none | 176.215.192.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 176.215.200.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 176.215.204.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 176.215.208.0/21 | No ROA covers it. Add a ROA for AS56377, maxLength 21. |
| ROA: none | 176.215.208.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 176.215.212.0/22 | No ROA covers it. Add a ROA for AS56377, maxLength 22. |
| ROA: none | 188.187.231.0/24 | No ROA covers it. Add a ROA for AS56377, maxLength 24. |
| Route object: none | 2a02:2698:402a::/48 | No route object for it. A route object for 2a02:2698:4000::/38 with origin AS56377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56377 in the RIR database for the space. |
| Route object: none | 2a02:2698:402b::/48 | No route object for it. A route object for 2a02:2698:4000::/38 with origin AS56377 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56377 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56377 whose prefix no peer sees AS56377 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.164.48.0/21 | RIPE | No ROA |
| 5.164.56.0/21 | RIPE | No ROA |
| 37.113.80.0/21 | RIPE | No ROA |
| 78.136.208.0/21 | RIPE | No ROA |
| 109.163.244.0/22 | RIPE | No ROA |
| 109.195.208.0/21 | RIPE | No ROA |
| 109.195.212.0/22 | RIPE | No ROA |
| 109.195.212.0/23 | RIPE | No ROA |
| 109.195.212.0/24 | RIPE | No ROA |
| 109.195.213.0/24 | RIPE | No ROA |
| 109.195.214.0/23 | RIPE | No ROA |
| 109.195.214.0/24 | RIPE | No ROA |
| 109.195.215.0/24 | RIPE | No ROA |
| 109.195.216.0/21 | RIPE | No ROA |
| 109.195.216.0/22 | RIPE | No ROA |
| 109.195.216.0/23 | RIPE | No ROA |
| 109.195.218.0/23 | RIPE | No ROA |
| 109.195.220.0/23 | RIPE | No ROA |
| 109.195.222.0/23 | RIPE | No ROA |
| 176.215.196.0/22 | RIPE | No ROA |
| 188.235.236.0/22 | RIPE | No ROA |
| 188.235.240.0/22 | RIPE | No ROA |
| 188.235.244.0/22 | RIPE | No ROA |
| 188.235.248.0/22 | RIPE | No ROA |
| 2a03:1ac0:5a4:3000::/52 | RIPE | No ROA |
| 2a03:1ac0:6da3:f000::/53 | RIPE | No ROA |
| 2a03:1ac0:6dc3:d000::/52 | RIPE | No ROA |
| 2a03:1ac0:b0d7:c000::/52 | RIPE | No ROA |
| 2a03:1ac0:b0d7:d000::/53 | 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.