RIPE Network Coordination Centre incident
TLSA records on our email MX servers
Resolved after 1 day 16 hours, affecting Email to/from the RIPE NCC, on June 5, 2026.
We have received confirmed reports of email delivery issues affecting messages sent to the RIPE NCC. Some senders may have received temporary delivery failure notifications, but affected messages are expected to be retried and delivered automatically.
Affected components
Update timeline
- investigating Jun 05, 2026, 02:18 PM UTC
The certificate authority we use changed the intermediate certificate of the certificates we use on our email MX servers, which we missed. This led to the TLSA records for our email MX servers to be incorrect. The TLSA records have been updated today around 16:00 Amsterdam time, but people verifying these may experience issues for the TTL duration of the records, which is 86400 seconds after the update in the worst case scenario.
- monitoring Jun 05, 2026, 02:19 PM UTC
Jun 5, 16:18 CEST Investigating - The certificate authority we use changed the intermediate certificate of the certificates we use on our email MX servers, which we missed. This led to the TLSA records for our email MX servers to be incorrect. The TLSA records have been updated today around 16:00 Amsterdam time, but people verifying these may experience issues for the TTL duration of the records, which is 86400 seconds after the update in the worst case scenario.
- identified Jun 05, 2026, 06:02 PM UTC
We have received confirmed reports of email delivery issues affecting messages sent to the RIPE NCC. Some senders may have received temporary delivery failure notifications, but affected messages are expected to be retried and delivered automatically.
- resolved Jun 07, 2026, 07:02 AM UTC
This incident has been 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.
Amazon Web Services