bgpreport

Network · data from 2026-11-12

AS394925 OptimERA xG

Registry name: OPTIMERANETWORKS - OptimERA xG, US · PeeringDB

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

Announced routes

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

206.168.84.2/32 No ROA Nonecovered by 206.168.84.0/22 1 0%low visibility 1
206.168.84.228/32 No ROA Nonecovered by 206.168.84.0/22 1 0%low visibility 1
206.168.84.229/32 No ROA Nonecovered by 206.168.84.0/22 1 0%low visibility 1
172.87.232.0/21 No ROA Other IRR onlyRADB 671 100% 67
206.168.84.0/22 No ROA Other IRR onlyRADB 669 99% 67

AS-SET

AS394925's PeeringDB record names no 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none206.168.84.2/32No ROA covers it. Add a ROA for AS394925, maxLength 32.1 of 673
Route object: none206.168.84.2/32No route object for it. A route object for 206.168.84.0/22 with origin AS394925 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS394925 in the RIR database for the space.1 of 673
ROA: none206.168.84.228/32No ROA covers it. Add a ROA for AS394925, maxLength 32.1 of 673
Route object: none206.168.84.228/32No route object for it. A route object for 206.168.84.0/22 with origin AS394925 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS394925 in the RIR database for the space.1 of 673
ROA: none206.168.84.229/32No ROA covers it. Add a ROA for AS394925, maxLength 32.1 of 673
Route object: none206.168.84.229/32No route object for it. A route object for 206.168.84.0/22 with origin AS394925 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS394925 in the RIR database for the space.1 of 673
ROA: none172.87.232.0/21No ROA covers it. Add a ROA for AS394925, maxLength 21.671 of 673
Route object: RIR172.87.232.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none206.168.84.0/22No ROA covers it. Add a ROA for AS394925, maxLength 22.669 of 673
Route object: RIR206.168.84.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

2604:8640::/32RADBNo 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.