Failing TCP connections to whois & RPKI

Incident Report for RIPE NCC

Resolved

This incident has been resolved.
Posted Mar 19, 2025 - 07:39 CET

Monitoring

The issues seem to have recovered between 20:30-20:45 UTC. We are monitoring the situation
Posted Mar 18, 2025 - 22:11 CET

Update

We have updated the status of the rpki dashboard. The RPKI dashboard is still affected, but is put in maintenance mode when it is part of an issue on statuspage, causing it to be fully unavailable while in fact it is mostly available.
Posted Mar 18, 2025 - 21:39 CET

Identified

We are still investigating the issue with the upstream providers.

We switched CDNs for rrdp.ripe.net and later changed the CDN configuration. rrdp.ripe.net is now using an origin outside our network, that is unaffected by the current issue.
Posted Mar 18, 2025 - 20:36 CET

Update

We are continuing to investigate this issue.
Posted Mar 18, 2025 - 20:32 CET

Investigating

We see a low rate (estimate: 5-10%) of failing TCP connections to multiple RIPE NCC services in our external monitoring. Paths via multiple of our upstream providers are affected.We are investigating the issue.
Posted Mar 18, 2025 - 19:25 CET
This incident affected: RIPE Database and RPKI (RPKI Dashboard, RRDP Repository, rsync Repository, Publication as a Service (API endpoints)).