On 20 May 2026, between 11:29 and 12:40 UTC, a partial outage affected access to different RIPE NCC services. Primarily, users on the RIPE Meeting network experienced “Access denied” responses served by Akamai, our CDN and security layer, when attempting to access RIPE NCC services.
At the time of the incident, we observed unusual traffic patterns reaching RIPE NCC Access accounts. In parallel, an existing Akamai rate-limiting configuration for static resources became active, temporarily blocking legitimate traffic alongside the suspicious traffic. We can confirm that there was no malicious traffic originating from within the RIPE Meeting network itself. The issue was mitigated by adjusting the Akamai configuration, after which access to services was restored.
We are reviewing our rate-limiting configuration and monitoring procedures to help us respond more quickly and effectively to similar situations in the future.