bgpreport

Network · data from 2026-11-12

AS206879 MEW-KW-ASN Ministry of Electricity and Water

Registry name: MEW-KW-ASN Ministry of Electricity and Water, KW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206879, 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.
185.173.40.0/23 No ROA Nonecovered by 185.173.40.0/22 672 100% 67
185.173.40.0/22 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS206879 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none185.173.40.0/23No ROA covers it. Add a ROA for AS206879, maxLength 23.672 of 673
Route object: none185.173.40.0/23No route object for it. A route object for 185.173.40.0/22 with origin AS206879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206879 in the RIR database for the space.672 of 673
ROA: none185.173.40.0/22No ROA covers it. Add a ROA for AS206879, maxLength 22.672 of 673
Route object: RIR185.173.40.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

185.173.40.0/24RADB, RIPENo ROA
185.173.41.0/24RADBNo ROA
185.173.42.0/24RADBNo ROA
185.173.43.0/24RADBNo 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.