Network · data from 2026-11-12
AS39028 ULSK-AS JSC "ER-Telecom Holding"
Registry name: ULSK-AS JSC "ER-Telecom Holding", RU · not in PeeringDB
33IPv4 routes
0.0% RPKI valid · 100.0% with a route object
3IPv6 routes
100.0% RPKI valid · 66.7% with a route object
0RPKI invalid
0 origin · 0 maxLength
33No ROA
1 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
34Route objects not announced
registered with origin AS39028, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS39028, 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.3.64.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 5.3.64.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.3.68.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.3.72.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.3.76.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.0.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.0.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.4.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.8.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.164.12.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.166.240.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 5.166.244.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.167.56.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 5.167.60.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 94.181.16.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 94.181.16.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 94.181.20.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 109.195.192.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 146.247.0.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 176.212.240.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 176.212.240.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.212.244.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.213.104.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 176.213.104.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.213.104.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 176.213.108.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.213.108.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 188.187.227.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 188.233.192.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 188.233.192.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.233.196.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 188.233.204.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.167.56.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 2a02:2698:842b::/48 | Valid | Nonecovered by 2a02:2698:8400::/38 | 635 100% |
| 2a02:2698:8400::/38 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:2698:842a::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS39028 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 68 are in fix.csv.
- ROA: none33
- Route object: none1
- Route object: not announced34
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.3.64.0/20 | No ROA covers it. Add a ROA for AS39028, maxLength 20. |
| ROA: none | 5.3.64.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.3.68.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.3.72.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.3.76.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.164.0.0/20 | No ROA covers it. Add a ROA for AS39028, maxLength 20. |
| ROA: none | 5.164.0.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.164.4.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.164.8.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.164.12.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.166.240.0/21 | No ROA covers it. Add a ROA for AS39028, maxLength 21. |
| ROA: none | 5.166.244.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.167.56.0/21 | No ROA covers it. Add a ROA for AS39028, maxLength 21. |
| ROA: none | 5.167.60.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 94.181.16.0/21 | No ROA covers it. Add a ROA for AS39028, maxLength 21. |
| ROA: none | 94.181.16.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 94.181.20.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 109.195.192.0/20 | No ROA covers it. Add a ROA for AS39028, maxLength 20. |
| ROA: none | 146.247.0.0/23 | No ROA covers it. Add a ROA for AS39028, maxLength 23. |
| ROA: none | 176.212.240.0/21 | No ROA covers it. Add a ROA for AS39028, maxLength 21. |
| ROA: none | 176.212.240.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 176.212.244.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 176.213.104.0/21 | No ROA covers it. Add a ROA for AS39028, maxLength 21. |
| ROA: none | 176.213.104.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 176.213.104.0/24 | No ROA covers it. Add a ROA for AS39028, maxLength 24. |
| ROA: none | 176.213.108.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 176.213.108.0/24 | No ROA covers it. Add a ROA for AS39028, maxLength 24. |
| ROA: none | 188.187.227.0/24 | No ROA covers it. Add a ROA for AS39028, maxLength 24. |
| ROA: none | 188.233.192.0/20 | No ROA covers it. Add a ROA for AS39028, maxLength 20. |
| ROA: none | 188.233.192.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 188.233.196.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 188.233.204.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| ROA: none | 5.167.56.0/22 | No ROA covers it. Add a ROA for AS39028, maxLength 22. |
| Route object: none | 2a02:2698:842b::/48 | No route object for it. A route object for 2a02:2698:8400::/38 with origin AS39028 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39028 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39028 whose prefix no peer sees AS39028 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.3.64.0/21 | RIPE | No ROA |
| 5.3.72.0/21 | RIPE | No ROA |
| 5.164.0.0/21 | RIPE | No ROA |
| 5.164.8.0/21 | RIPE | No ROA |
| 5.166.240.0/22 | RIPE | No ROA |
| 37.113.80.0/21 | RIPE | No ROA |
| 78.136.208.0/21 | RIPE | No ROA |
| 109.194.222.0/23 | RIPE | No ROA |
| 109.195.192.0/21 | RIPE | No ROA |
| 109.195.196.0/24 | RIPE | No ROA |
| 109.195.197.0/24 | RIPE | No ROA |
| 109.195.198.0/24 | RIPE | No ROA |
| 109.195.199.0/24 | RIPE | No ROA |
| 109.195.200.0/23 | RIPE | No ROA |
| 109.195.202.0/23 | RIPE | No ROA |
| 109.195.204.0/23 | RIPE | No ROA |
| 109.195.204.0/24 | RIPE | No ROA |
| 109.195.205.0/24 | RIPE | No ROA |
| 109.195.206.0/23 | RIPE | No ROA |
| 109.195.206.0/24 | RIPE | No ROA |
| 109.195.207.0/24 | RIPE | No ROA |
| 188.233.200.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:503:4000::/52 | RIPE | No ROA |
| 2a03:1ac0:5a4::/52 | RIPE | No ROA |
| 2a03:1ac0:5a6:f000::/53 | RIPE | No ROA |
| 2a03:1ac0:5a7:3800::/53 | RIPE | No ROA |
| 2a03:1ac0:5eb5:1000::/53 | RIPE | No ROA |
| 2a03:1ac0:6dc3:c000::/52 | RIPE | No ROA |
| 2a03:1ac0:b0d4:f000::/53 | RIPE | No ROA |
| 2a03:1ac0:bce9:c000::/52 | 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.