RIPE Network Coordination Centre incident

Increased error rate with RIPEstat

Resolved after 7 hours 14 minutes, affecting RIPEstat, on March 3, 2026.

resolved Mar 03, 2026, 02:04 PM UTC

The error rates have come back and stayed within typical levels. The issue was caused by the application keeping TCP connections in a non-closed state, exhausting resources. After restarting some backend services those connections were flushed and the issue resolved.

Started
Mar 03, 2026, 06:50 AM UTC
Resolved
Mar 03, 2026, 02:04 PM UTC
Duration
7h 14m
Detected by Pingoru
Mar 03, 2026, 06:50 AM UTC

Affected components

RIPEstat

Update timeline

  1. investigating Mar 03, 2026, 06:50 AM UTC

    We are experiencing issues with RIPEstat since ~02:17 UTC. We are investigating and will update this announcement once we know more.

  2. monitoring Mar 03, 2026, 08:26 AM UTC

    We have mitigated the issue and will continue to monitor the situation closely. We will share an update when it has been fully resolved.

  3. resolved Mar 03, 2026, 02:04 PM UTC

    The error rates have come back and stayed within typical levels. The issue was caused by the application keeping TCP connections in a non-closed state, exhausting resources. After restarting some backend services those connections were flushed and the issue resolved.

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.

Add your stack →