PKI Signing Outage History
PKI Signing is up right nowPKI Signing had 5 outages in the last 2 years totaling 110h 15m of downtime — averaging 0.2 incidents per month.
There were 5 PKI Signing outages since November 10, 2025 totaling 110h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.
PKIsigning eSeal degraded performance
Timeline · 2 updates
- investigating Feb 26, 2026, 01:34 PM UTC
Signatures actions using PKIsigning as signature provider might take longer than usual. We are investigating the issue.
- resolved Feb 26, 2026, 02:22 PM UTC
The supplier had a technical issue in their infrastructure. The incident has been resolved.
PKIsigning eSeal unavailable
Timeline · 3 updates
- investigating Feb 03, 2026, 02:59 PM UTC
The PKisigning eSeal is unavailable. This means all signatures using PKIsigning as signature provider currently cannot be completed. We are investigating the issue.
- monitoring Feb 03, 2026, 03:06 PM UTC
The eSeal is available again and all signature services are operational. We will keep monitoring the situation.
- resolved Feb 03, 2026, 03:20 PM UTC
The incident has been resolved.
Digipoort availability issues
Timeline · 2 updates
- identified Feb 02, 2026, 11:02 AM UTC
Digipoort has availability issues, which may impact services. This means that some requests have been rejected with reason ALS100. These requests will have to be resubmitted. The Logius mobile app shows the current status.
- resolved Feb 02, 2026, 08:35 PM UTC
Logius has reported that the issue is resolved. Requests with digipoort status ALS100 will have to be resubmitted.
DigiCert ONE degraded performance
Timeline · 3 updates
- investigating Nov 12, 2025, 07:54 AM UTC
DigiCert is still experiencing issues with their DigiCert ONE solution. Users with certificates from DigiCert might be unable to sign at the moment. If your signature is urgent, please retry several times.
- investigating Nov 13, 2025, 09:24 AM UTC
DigiCert has implemented a fix and the issue is resolved.
- resolved Nov 13, 2025, 09:24 AM UTC
This incident has been resolved.