bgpreport

Network · data from 2026-11-12

AS208111 baremetal.ae

Registry name: BAREMETAL-AE Falcon FZE LLC, AE · PeeringDB

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

Announced routes

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

45.135.212.0/24 Valid None 672 100% 66
45.135.213.0/24 Valid None 672 100% 66
2a14:9d01::/32 Valid None 635 100% 68
2a14:9d02::/32 Valid None 635 100% 68
185.121.69.0/24 Valid RIR databaseRIPE 672 100% 66
185.13.156.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS208111'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 4 are in fix.csv.

  • Route object: none4
ChangePrefix or setDetailFull-table peers
Route object: none45.135.212.0/24No route object for it. Add a route object with origin AS208111 in the RIR database for the space.672 of 673
Route object: none45.135.213.0/24No route object for it. Add a route object with origin AS208111 in the RIR database for the space.672 of 673
Route object: none2a14:9d01::/32No route object for it. Add a route object with origin AS208111 in the RIR database for the space.635 of 636
Route object: none2a14:9d02::/32No route object for it. Add a route object with origin AS208111 in the RIR database for the space.635 of 636

Route objects not announced

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