bgpreport

Network · data from 2026-11-12

AS207027 Eximius-AS LLC Eximius

Registry name: Eximius-AS LLC Eximius, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207027, 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.
2.59.176.0/22 No ROA None 2 0%low visibility 2
91.212.49.0/24 No ROA None 2 0%low visibility 2
91.212.51.0/24 No ROA None 2 0%low visibility 2
91.212.65.0/24 No ROA None 2 0%low visibility 2
193.37.34.0/24 No ROA None 2 0%low visibility 2
193.176.220.0/24 No ROA None 2 0%low visibility 2
91.227.16.0/22 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none2.59.176.0/22No ROA covers it. Add a ROA for AS207027, maxLength 22.2 of 673
Route object: none2.59.176.0/22No route object for it. Add a route object with origin AS207027 in the RIR database for the space.2 of 673
ROA: none91.212.49.0/24No ROA covers it. Add a ROA for AS207027, maxLength 24.2 of 673
Route object: none91.212.49.0/24No route object for it. Add a route object with origin AS207027 in the RIR database for the space.2 of 673
ROA: none91.212.51.0/24No ROA covers it. Add a ROA for AS207027, maxLength 24.2 of 673
Route object: none91.212.51.0/24No route object for it. Add a route object with origin AS207027 in the RIR database for the space.2 of 673
ROA: none91.212.65.0/24No ROA covers it. Add a ROA for AS207027, maxLength 24.2 of 673
Route object: none91.212.65.0/24No route object for it. Add a route object with origin AS207027 in the RIR database for the space.2 of 673
ROA: none193.37.34.0/24No ROA covers it. Add a ROA for AS207027, maxLength 24.2 of 673
Route object: none193.37.34.0/24No route object for it. Add a route object with origin AS207027 in the RIR database for the space.2 of 673
ROA: none193.176.220.0/24No ROA covers it. Add a ROA for AS207027, maxLength 24.2 of 673
Route object: none193.176.220.0/24No route object for it. Add a route object with origin AS207027 in the RIR database for the space.2 of 673

Route objects not announced

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