RIPE Network Coordination Centre incident
Issues affecting RIPEstat (including rpki and routing registry based datasets)
Resolved after 4 hours 8 minutes, affecting RIPEstat, on April 23, 2026.
Our IRRd instances that we use to have a local copy of internet routing registry data have recovered. This final recovery resolves this incident for RIPEstat.
Affected components
Update timeline
- monitoring Apr 23, 2026, 05:28 AM UTC
RIPEstat experienced partial unavailability between 03:00 and 05:30 UTC due to a widespread Docker infrastructure issue at RIPE NCC. Because the issue also affected our monitoring infrastructure during this window, we cannot fully determine the scope of the impact. Services have recovered. We are investigating the root cause.
- monitoring Apr 23, 2026, 05:28 AM UTC
We are continuing to monitor for any further issues.
- resolved Apr 23, 2026, 09:37 AM UTC
Our IRRd instances that we use to have a local copy of internet routing registry data have recovered. This final recovery resolves this incident for RIPEstat.
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