bgpreport

Network · data from 2026-11-12

AS208944 Qatar General Electricity and Water

Registry name: KM Qatar General Electricty and Water Corporation, QA · PeeringDB

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

Announced routes

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

5.180.36.0/23 No ROA Other IRR onlyRADB 671 100% 67
2a09:3740::/29 No ROA RIR databaseRIPE 1 0%low visibility 1
5.180.38.0/23 Valid Other IRR onlyRADB 670 100% 67

AS-SET

AS208944'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 5 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none5.180.36.0/23No ROA covers it. Add a ROA for AS208944, maxLength 23.671 of 673
Route object: RIR5.180.36.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2a09:3740::/29No ROA covers it. Add a ROA for AS208944, maxLength 29.1 of 636
Route object: RIR5.180.38.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

5.180.36.0/22RIPENo 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.