bgpreport

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

25IPv4 routes 12.0% RPKI valid · 80.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
22No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS41403, seen from no peer

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% 67
46.236.152.0/22 No ROA Nonecovered by 46.236.128.0/19 673 100% 67
78.136.246.0/23 No ROA Nonecovered by 78.136.244.0/22 673 100% 67
46.236.128.0/19 No ROA RIR databaseRIPE 673 100% 67
46.236.128.0/22 No ROA RIR databaseRIPE 673 100% 67
46.236.132.0/22 No ROA RIR databaseRIPE 673 100% 67
46.236.136.0/22 No ROA RIR databaseRIPE 673 100% 67
46.236.140.0/22 No ROA RIR databaseRIPE 673 100% 67
78.136.224.0/21 No ROA RIR databaseRIPE 673 100% 67
78.136.228.0/22 No ROA RIR databaseRIPE 673 100% 67
78.136.240.0/21 No ROA RIR databaseRIPE 673 100% 67
84.22.200.0/22 No ROA RIR databaseRIPE 673 100% 66
91.224.102.0/23 No ROA RIR databaseRIPE 673 100% 67
146.247.4.0/22 No ROA RIR databaseRIPE 673 100% 67
176.212.140.0/22 No ROA RIR databaseRIPE 673 100% 67
176.214.192.0/20 No ROA RIR databaseRIPE 673 100% 67
176.214.200.0/22 No ROA RIR databaseRIPE 673 100% 67
176.214.201.0/24 No ROA RIR databaseRIPE 673 100% 67
176.214.202.0/24 No ROA RIR databaseRIPE 673 100% 67
176.214.204.0/22 No ROA RIR databaseRIPE 673 100% 67
176.214.205.0/24 No ROA RIR databaseRIPE 673 100% 67
176.214.206.0/24 No ROA RIR databaseRIPE 670 100% 67
78.136.232.0/22 Valid Nonecovered by 78.136.232.0/21 673 100% 67
78.136.236.0/22 Valid Nonecovered by 78.136.232.0/21 673 100% 67
78.136.232.0/21 Valid RIR databaseRIPE 673 100% 67

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
ChangePrefix or setDetailFull-table peers
ROA: none5.3.27.0/24No ROA covers it. Add a ROA for AS41403, maxLength 24.673 of 673
Route object: none5.3.27.0/24Route objects for it name AS62287. Add a route object with origin AS41403 in the RIR database for the space.673 of 673
ROA: none46.236.152.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
Route object: none46.236.152.0/22No 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.673 of 673
ROA: none78.136.246.0/23No ROA covers it. Add a ROA for AS41403, maxLength 23.673 of 673
Route object: none78.136.246.0/23No 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.673 of 673
ROA: none46.236.128.0/19No ROA covers it. Add a ROA for AS41403, maxLength 19.673 of 673
ROA: none46.236.128.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none46.236.132.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none46.236.136.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none46.236.140.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none78.136.224.0/21No ROA covers it. Add a ROA for AS41403, maxLength 21.673 of 673
ROA: none78.136.228.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none78.136.240.0/21No ROA covers it. Add a ROA for AS41403, maxLength 21.673 of 673
ROA: none84.22.200.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none91.224.102.0/23No ROA covers it. Add a ROA for AS41403, maxLength 23.673 of 673
ROA: none146.247.4.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none176.212.140.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none176.214.192.0/20No ROA covers it. Add a ROA for AS41403, maxLength 20.673 of 673
ROA: none176.214.200.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none176.214.201.0/24No ROA covers it. Add a ROA for AS41403, maxLength 24.673 of 673
ROA: none176.214.202.0/24No ROA covers it. Add a ROA for AS41403, maxLength 24.673 of 673
ROA: none176.214.204.0/22No ROA covers it. Add a ROA for AS41403, maxLength 22.673 of 673
ROA: none176.214.205.0/24No ROA covers it. Add a ROA for AS41403, maxLength 24.673 of 673
ROA: none176.214.206.0/24No ROA covers it. Add a ROA for AS41403, maxLength 24.670 of 673
Route object: none78.136.232.0/22No 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.673 of 673
Route object: none78.136.236.0/22No 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.673 of 673

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/24RIPENo ROA
78.136.224.0/23RIPENo ROA
78.136.226.0/23RIPENo ROA
78.136.240.0/22RIPENo ROA
78.136.240.0/23RIPENo ROA
78.136.242.0/23RIPENo ROA
78.136.244.0/22RIPENo ROA
91.226.178.0/24RADBNo ROA
146.247.2.0/23RIPENo 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.