bgpreport

Network · data from 2026-11-12

AS215290 BEA-AS Bezhin Evgenii Alekseevich

Registry name: BEA-AS Bezhin Evgenii Alekseevich, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215290, 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.
2a12:bc80::/32 No ROA None 1 0%low visibility 1
2a0d:ad44::/32 Valid RIR databaseRIPE 636 100% 67
2a11:b4c0::/32 Valid RIR databaseRIPE 634 100% 67
2a12:6482::/32 Valid RIR databaseRIPE 634 100% 67
2a12:bc84::/32 Valid RIR databaseRIPE 634 100% 67
2a12:d801::/32 Valid RIR databaseRIPE 634 100% 67
2a12:f986::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a12:bc80::/32No ROA covers it. Add a ROA for AS215290, maxLength 32.1 of 636
Route object: none2a12:bc80::/32No route object for it. Add a route object with origin AS215290 in the RIR database for the space.1 of 636

Route objects not announced

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