RIPE Network Coordination Centre incident

informational: ASPA objects close to expiry

Resolved after 7 hours 10 minutes, affecting RRDP Repository and rsync Repository, on June 30, 2026.

resolved Jun 30, 2026, 07:14 PM UTC

The affected ASPA objects (287 ASPA objects for 232 hosted CAs signed in 2025) were re-signed and published around 14:50 UTC. The underlying software bug has been fixed. This incident has been resolved.

Started
Jun 30, 2026, 12:03 PM UTC
Resolved
Jun 30, 2026, 07:14 PM UTC
Duration
7h 10m
Detected by Pingoru
Jun 30, 2026, 12:03 PM UTC

Affected components

RRDP Repositoryrsync Repository

Update timeline

  1. monitoring Jun 30, 2026, 12:03 PM UTC

    Jun 30, 14:03 CEST Identified - We have noticed that a number of ASPA are approaching their expiry date. The ASPA objects were not re-issued when the CA certificate that signed them was re-issued on 1 January. We have identified the issue and are implementing a fix. The fix will be rolled out before objects expire. We do not expect any impact.

  2. identified Jun 30, 2026, 12:03 PM UTC

    We have noticed that a number of ASPA are approaching their expiry date. The ASPA objects were not re-issued when the CA certificate that signed them was re-issued on 1 January. We have identified the issue and are implementing a fix. The fix will be rolled out before objects expire. We do not expect any impact.

  3. resolved Jun 30, 2026, 07:14 PM UTC

    The affected ASPA objects (287 ASPA objects for 232 hosted CAs signed in 2025) were re-signed and published around 14:50 UTC. The underlying software bug has been fixed. 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.

Add your stack →