bgpreport

Network · data from 2026-11-12

AS201826 era-telecom LLC eratelecom company

Registry name: era-telecom LLC eratelecom company, RU · not in PeeringDB

20IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
20No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS201826, seen from no peer

Announced routes

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

95.172.48.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.49.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.50.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.51.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.52.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.53.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.54.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.55.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.56.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.57.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.58.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.59.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.60.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.61.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.62.0/24 No ROA RIR databaseRIPE 673 100% 66
95.172.63.0/24 No ROA RIR databaseRIPE 673 100% 66
185.36.172.0/24 No ROA RIR databaseRIPE 673 100% 66
185.36.173.0/24 No ROA RIR databaseRIPE 673 100% 66
185.36.174.0/24 No ROA RIR databaseRIPE 673 100% 66
185.36.175.0/24 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS201826 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 20 are in fix.csv.

  • ROA: none20
ChangePrefix or setDetailFull-table peers
ROA: none95.172.48.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.49.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.50.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.51.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.52.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.53.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.54.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.55.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.56.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.57.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.58.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.59.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.60.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.61.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.62.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none95.172.63.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none185.36.172.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none185.36.173.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none185.36.174.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673
ROA: none185.36.175.0/24No ROA covers it. Add a ROA for AS201826, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS201826 is announced.

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.