bgpreport

Network · data from 2026-11-12

AS31483 ERTELECOM-DC-AS JSC "ER-Telecom Holding"

Registry name: ERTELECOM-DC-AS JSC "ER-Telecom Holding", RU · not in PeeringDB

22IPv4 routes 0.0% RPKI valid · 90.9% with a route object
6IPv6 routes 16.7% RPKI valid · 83.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
27No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS31483, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31483, 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.

188.186.152.0/23 No ROA Nonecovered by 188.186.152.0/22 673 100% 67
46.146.236.0/23 No ROA None 671 100% 67
2a01:54e0:fc00::/39 No ROA Nonecovered by 2a01:54e0:f000::/36 636 100% 68
5.3.0.0/24 No ROA RIR databaseRIPE 673 100% 66
5.3.1.0/24 No ROA RIR databaseRIPE 673 100% 66
5.3.2.0/24 No ROA RIR databaseRIPE 673 100% 66
5.3.3.0/24 No ROA RIR databaseRIPE 673 100% 66
5.3.4.0/24 No ROA RIR databaseRIPE 673 100% 66
5.3.5.0/24 No ROA RIR databaseRIPE 673 100% 66
5.3.6.0/23 No ROA RIR databaseRIPE 673 100% 66
5.3.8.0/24 No ROA RIR databaseRIPE 673 100% 66
79.136.172.0/22 No ROA RIR databaseRIPE 673 100% 66
79.141.49.0/24 No ROA RIR databaseRIPE 673 100% 66
109.194.152.0/24 No ROA RIR databaseRIPE 673 100% 66
109.194.153.0/24 No ROA RIR databaseRIPE 673 100% 66
109.194.158.0/24 No ROA RIR databaseRIPE 673 100% 66
109.194.159.0/24 No ROA RIR databaseRIPE 673 100% 66
188.186.144.0/20 No ROA RIR databaseRIPE 673 100% 66
188.186.144.0/22 No ROA RIR databaseRIPE 673 100% 66
188.186.148.0/22 No ROA RIR databaseRIPE 673 100% 66
188.186.152.0/22 No ROA RIR databaseRIPE 673 100% 66
188.186.156.0/23 No ROA RIR databaseRIPE 673 100% 66
79.141.48.0/24 No ROA RIR databaseRIPE 670 100% 66
2a01:54e0:ec00::/38 No ROA RIR databaseRIPE 636 100% 68
2a01:54e0:f000::/38 No ROA RIR databaseRIPE 636 100% 68
2a01:54e0:f400::/38 No ROA RIR databaseRIPE 636 100% 67
2a01:54e0:f800::/38 No ROA RIR databaseRIPE 636 100% 68
2a02:2698:a002::/48 Valid RIR databaseRIPE 636 100% 68

AS-SET

AS31483 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 38 are in fix.csv.

  • ROA: none27
  • Route object: none3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none188.186.152.0/23No ROA covers it. Add a ROA for AS31483, maxLength 23.673 of 673
Route object: none188.186.152.0/23No route object for it. A route object for 188.186.152.0/22 with origin AS31483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31483 in the RIR database for the space.673 of 673
ROA: none46.146.236.0/23No ROA covers it. Add a ROA for AS31483, maxLength 23.671 of 673
Route object: none46.146.236.0/23No route object for it. Add a route object with origin AS31483 in the RIR database for the space.671 of 673
ROA: none2a01:54e0:fc00::/39No ROA covers it. Add a ROA for AS31483, maxLength 39.636 of 636
Route object: none2a01:54e0:fc00::/39No route object for it. A route object for 2a01:54e0:f000::/36 with origin AS31483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31483 in the RIR database for the space.636 of 636
ROA: none5.3.0.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none5.3.1.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none5.3.2.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none5.3.3.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none5.3.4.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none5.3.5.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none5.3.6.0/23No ROA covers it. Add a ROA for AS31483, maxLength 23.673 of 673
ROA: none5.3.8.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none79.136.172.0/22No ROA covers it. Add a ROA for AS31483, maxLength 22.673 of 673
ROA: none79.141.49.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none109.194.152.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none109.194.153.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none109.194.158.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none109.194.159.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.673 of 673
ROA: none188.186.144.0/20No ROA covers it. Add a ROA for AS31483, maxLength 20.673 of 673
ROA: none188.186.144.0/22No ROA covers it. Add a ROA for AS31483, maxLength 22.673 of 673
ROA: none188.186.148.0/22No ROA covers it. Add a ROA for AS31483, maxLength 22.673 of 673
ROA: none188.186.152.0/22No ROA covers it. Add a ROA for AS31483, maxLength 22.673 of 673
ROA: none188.186.156.0/23No ROA covers it. Add a ROA for AS31483, maxLength 23.673 of 673
ROA: none79.141.48.0/24No ROA covers it. Add a ROA for AS31483, maxLength 24.670 of 673
ROA: none2a01:54e0:ec00::/38No ROA covers it. Add a ROA for AS31483, maxLength 38.636 of 636
ROA: none2a01:54e0:f000::/38No ROA covers it. Add a ROA for AS31483, maxLength 38.636 of 636
ROA: none2a01:54e0:f400::/38No ROA covers it. Add a ROA for AS31483, maxLength 38.636 of 636
ROA: none2a01:54e0:f800::/38No ROA covers it. Add a ROA for AS31483, maxLength 38.636 of 636

Route objects not announced

Route objects with origin AS31483 whose prefix no peer sees AS31483 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.3.6.0/24RIPENo ROA
5.3.7.0/24RIPENo ROA
109.194.149.0/24RIPENo ROA
109.194.154.0/23RIPENo ROA
109.194.154.0/24RIPENo ROA
188.186.156.0/24RIPENo ROA
188.186.157.0/24RIPENo ROA
2a01:54e0:f000::/36RIPENo 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.