Network · data from 2026-11-12
AS51034 DSI-EAS JSC "ER-Telecom Holding"
Registry name: DSI-EAS JSC "ER-Telecom Holding", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51034, 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.
| 84.244.0.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 91.185.40.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 94.137.192.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 2a02:2360::/32 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
AS51034 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 49 are in fix.csv.
- ROA: none4
- Route object: not announced45
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 84.244.0.0/19 | No ROA covers it. Add a ROA for AS51034, maxLength 19. |
| ROA: none | 91.185.40.0/23 | No ROA covers it. Add a ROA for AS51034, maxLength 23. |
| ROA: none | 94.137.192.0/19 | No ROA covers it. Add a ROA for AS51034, maxLength 19. |
| ROA: none | 2a02:2360::/32 | No ROA covers it. Add a ROA for AS51034, maxLength 32. |
Route objects not announced
Route objects with origin AS51034 whose prefix no peer sees AS51034 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 84.244.0.0/24 | RIPE | No ROA |
| 84.244.1.0/24 | RIPE | No ROA |
| 84.244.2.0/24 | RIPE | No ROA |
| 84.244.3.0/24 | RIPE | No ROA |
| 84.244.4.0/24 | RIPE | No ROA |
| 84.244.7.0/24 | RIPE | No ROA |
| 84.244.24.0/24 | RIPE | No ROA |
| 84.244.25.0/24 | RIPE | No ROA |
| 84.244.26.0/24 | RIPE | No ROA |
| 84.244.27.0/24 | RIPE | No ROA |
| 84.244.28.0/24 | RIPE | No ROA |
| 84.244.29.0/24 | RIPE | No ROA |
| 84.244.30.0/24 | RIPE | No ROA |
| 84.244.31.0/24 | RIPE | No ROA |
| 84.244.48.0/23 | RIPE | No ROA |
| 84.244.60.192/26 | RIPE | No ROA |
| 94.137.192.0/23 | RIPE | No ROA |
| 94.137.192.0/24 | RIPE | No ROA |
| 94.137.194.0/24 | RIPE | No ROA |
| 94.137.195.0/24 | RIPE | No ROA |
| 94.137.196.0/24 | RIPE | No ROA |
| 94.137.197.0/24 | RIPE | No ROA |
| 94.137.198.0/24 | RIPE | No ROA |
| 94.137.200.0/24 | RIPE | No ROA |
| 94.137.201.0/24 | RIPE | No ROA |
| 94.137.202.0/24 | RIPE | No ROA |
| 94.137.203.0/24 | RIPE | No ROA |
| 94.137.204.0/24 | RIPE | No ROA |
| 94.137.205.0/24 | RIPE | No ROA |
| 94.137.206.0/24 | RIPE | No ROA |
| 94.137.207.0/24 | RIPE | No ROA |
| 94.137.208.0/23 | RIPE | No ROA |
| 94.137.210.0/24 | RIPE | No ROA |
| 94.137.211.0/24 | RIPE | No ROA |
| 94.137.212.0/24 | RIPE | No ROA |
| 94.137.213.0/24 | RIPE | No ROA |
| 94.137.214.0/24 | RIPE | No ROA |
| 94.137.215.0/24 | RIPE | No ROA |
| 94.137.216.0/24 | RIPE | No ROA |
| 94.137.217.0/24 | RIPE | No ROA |
| 94.137.218.0/24 | RIPE | No ROA |
| 94.137.219.0/24 | RIPE | No ROA |
| 94.137.220.0/24 | RIPE | No ROA |
| 94.137.221.0/24 | RIPE | No ROA |
| 94.137.222.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.