RIPE Network Coordination Centre incident

Elevated error rate for prefix-routing-consistency call of RIPEstat

Minor Resolved View vendor source →

RIPE Network Coordination Centre experienced a minor incident on August 28, 2025 affecting RIPEstat, lasting 14h 29m. The incident has been resolved; the full update timeline is below.

Started
Aug 28, 2025, 03:07 PM UTC
Resolved
Aug 29, 2025, 05:36 AM UTC
Duration
14h 29m
Detected by Pingoru
Aug 28, 2025, 03:07 PM UTC

Affected components

RIPEstat

Update timeline

  1. identified Aug 28, 2025, 03:07 PM UTC

    We are aware of an elevated error rate for the `prefix-routing-consistency` for some prefixes. The root cause is a performance issue with the underlying PostgreSQL server used for our IRR data. We are working on a mitigation.

  2. monitoring Aug 28, 2025, 03:50 PM UTC

    We have deployed a fix. We are monitoring the performance.

  3. monitoring Aug 28, 2025, 03:50 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Aug 29, 2025, 05:36 AM UTC

    The issue has been resolved. Our configuration change has led to a performance improvements in two areas. First, the p99 latency is now about 80% of what it was before the change. Additionally, some lookups that were previously failing are now completing successfully.