bgpreport

Network · data from 2026-11-12

AS56384 AVANTEL JSC "ER-Telecom Holding"

Registry name: AVANTEL JSC "ER-Telecom Holding", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56384, 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.
62.68.149.0/24 No ROA Nonecovered by 62.68.148.0/22 673 100% 67
62.68.150.0/24 No ROA Nonecovered by 62.68.148.0/22 672 100% 67
195.208.216.0/22 No ROA None 2 0%low visibility 2
62.68.148.0/22 No ROA RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: none4
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none62.68.149.0/24No ROA covers it. Add a ROA for AS56384, maxLength 24.673 of 673
Route object: none62.68.149.0/24No route object for it. A route object for 62.68.148.0/22 with origin AS56384 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56384 in the RIR database for the space.673 of 673
ROA: none62.68.150.0/24No ROA covers it. Add a ROA for AS56384, maxLength 24.672 of 673
Route object: none62.68.150.0/24No route object for it. A route object for 62.68.148.0/22 with origin AS56384 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56384 in the RIR database for the space.672 of 673
ROA: none195.208.216.0/22No ROA covers it. Add a ROA for AS56384, maxLength 22.2 of 673
Route object: none195.208.216.0/22No route object for it. Add a route object with origin AS56384 in the RIR database for the space.2 of 673
ROA: none62.68.148.0/22No ROA covers it. Add a ROA for AS56384, maxLength 22.673 of 673

Route objects not announced

Every route object with origin AS56384 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.