RIPE Network Coordination Centre incident
Issue accessing RIPE NCC Services
Resolved after 1 hour 19 minutes, affecting Billing & Payments and RPKI Dashboard and 1 more, on May 20, 2026.
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.
Affected components
Update timeline
- investigating May 20, 2026, 01:00 PM UTC
We are experiencing issues with a number of our services. We are investigating and will update this announcement once we know more.
- resolved May 20, 2026, 01:01 PM UTC
May 20, 15:01 CEST Resolved - We experienced issues with accessing the LIR Portal, SSO and other services were login was required. Access has now been restored. May 20, 13:42 CEST Investigating - We are experiencing issues with a number of our services. We are investigating and will update this announcement once we know more.
- resolved May 20, 2026, 01:01 PM UTC
We experienced issues with accessing the LIR Portal, SSO and other services were login was required. Access has now been restored.
- postmortem May 21, 2026, 01:49 PM UTC
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.
Your product runs on more than RIPE Network Coordination Centre
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services