bgpreport

Network · data from 2026-11-12

AS52081 The Commercial Real Estate Co. K.S.C.C

Registry name: CRE The Commercial Real Estate Co. K.S.C.C, KW · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52081, 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.
91.221.220.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
91.221.221.0/24 No ROA RIR databaseRADB, RIPE 671 100% 66
62.215.49.0/24 Valid Other IRR onlyRADB 670 100% 67

AS-SET

AS52081'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.

  • ROA: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none91.221.220.0/24No ROA covers it. Add a ROA for AS52081, maxLength 24.672 of 673
ROA: none91.221.221.0/24No ROA covers it. Add a ROA for AS52081, maxLength 24.671 of 673
Route object: RIR62.215.49.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

91.221.220.0/23RADB, RIPENo 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.