Network · data from 2026-11-12
AS41403 ULAN-UDE-AS JSC "ER-Telecom Holding"
Registry name: ULAN-UDE-AS JSC "ER-Telecom Holding", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41403, 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.27.0/24 | No ROA | Other origin only | 673 100% |
| 46.236.152.0/22 | No ROA | Nonecovered by 46.236.128.0/19 | 673 100% |
| 78.136.246.0/23 | No ROA | Nonecovered by 78.136.244.0/22 | 673 100% |
| 46.236.128.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 46.236.128.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 46.236.132.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 46.236.136.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 46.236.140.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 78.136.224.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 78.136.228.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 78.136.240.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 84.22.200.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.224.102.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 146.247.4.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.212.140.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.214.192.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 176.214.200.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.214.201.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 176.214.202.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 176.214.204.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 176.214.205.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 176.214.206.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 78.136.232.0/22 | Valid | Nonecovered by 78.136.232.0/21 | 673 100% |
| 78.136.236.0/22 | Valid | Nonecovered by 78.136.232.0/21 | 673 100% |
| 78.136.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS41403 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 36 are in fix.csv.
- ROA: none22
- Route object: none5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.3.27.0/24 | No ROA covers it. Add a ROA for AS41403, maxLength 24. |
| Route object: none | 5.3.27.0/24 | Route objects for it name AS62287. Add a route object with origin AS41403 in the RIR database for the space. |
| ROA: none | 46.236.152.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| Route object: none | 46.236.152.0/22 | No route object for it. A route object for 46.236.128.0/19 with origin AS41403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41403 in the RIR database for the space. |
| ROA: none | 78.136.246.0/23 | No ROA covers it. Add a ROA for AS41403, maxLength 23. |
| Route object: none | 78.136.246.0/23 | No route object for it. A route object for 78.136.244.0/22 with origin AS41403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41403 in the RIR database for the space. |
| ROA: none | 46.236.128.0/19 | No ROA covers it. Add a ROA for AS41403, maxLength 19. |
| ROA: none | 46.236.128.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 46.236.132.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 46.236.136.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 46.236.140.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 78.136.224.0/21 | No ROA covers it. Add a ROA for AS41403, maxLength 21. |
| ROA: none | 78.136.228.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 78.136.240.0/21 | No ROA covers it. Add a ROA for AS41403, maxLength 21. |
| ROA: none | 84.22.200.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 91.224.102.0/23 | No ROA covers it. Add a ROA for AS41403, maxLength 23. |
| ROA: none | 146.247.4.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 176.212.140.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 176.214.192.0/20 | No ROA covers it. Add a ROA for AS41403, maxLength 20. |
| ROA: none | 176.214.200.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 176.214.201.0/24 | No ROA covers it. Add a ROA for AS41403, maxLength 24. |
| ROA: none | 176.214.202.0/24 | No ROA covers it. Add a ROA for AS41403, maxLength 24. |
| ROA: none | 176.214.204.0/22 | No ROA covers it. Add a ROA for AS41403, maxLength 22. |
| ROA: none | 176.214.205.0/24 | No ROA covers it. Add a ROA for AS41403, maxLength 24. |
| ROA: none | 176.214.206.0/24 | No ROA covers it. Add a ROA for AS41403, maxLength 24. |
| Route object: none | 78.136.232.0/22 | No route object for it. A route object for 78.136.232.0/21 with origin AS41403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41403 in the RIR database for the space. |
| Route object: none | 78.136.236.0/22 | No route object for it. A route object for 78.136.232.0/21 with origin AS41403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41403 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41403 whose prefix no peer sees AS41403 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.77.25.0/24 | RIPE | No ROA |
| 78.136.224.0/23 | RIPE | No ROA |
| 78.136.226.0/23 | RIPE | No ROA |
| 78.136.240.0/22 | RIPE | No ROA |
| 78.136.240.0/23 | RIPE | No ROA |
| 78.136.242.0/23 | RIPE | No ROA |
| 78.136.244.0/22 | RIPE | No ROA |
| 91.226.178.0/24 | RADB | No ROA |
| 146.247.2.0/23 | 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.