PKI Signing Outage History

PKI Signing is up right now

PKI Signing had 15 outages in the last 2 years totaling 150h 28m of downtime — averaging 0.6 incidents per month.

There were 15 PKI Signing outages since November 15, 2024 totaling 150h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pkisigning.nl

Critical July 24, 2026

PKIsigning signature provider not working

Detected by Pingoru
Jul 24, 2026, 08:03 AM UTC
Resolved
Jul 24, 2026, 12:00 PM UTC
Duration
3h 57m
Affected: Signing service
Timeline · 4 updates
  1. investigating Jul 24, 2026, 08:03 AM UTC

    All signatures using the PKisigning eSeal certificate are currently not working. We are investigating the issue.

  2. identified Jul 24, 2026, 09:55 AM UTC

    There seems to be an issue at DigiCert causing the eSeal to not work correctly. DigiCert has published it's own incident which can be followed here: https://status.digicert.com/incidents/mwtlmhnjq6m4

  3. monitoring Jul 24, 2026, 11:27 AM UTC

    DigiCert has identified the issue and implemented a fix. We see signatures on our end working again. We are monitoring the situation.

  4. resolved Jul 24, 2026, 12:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 26, 2026

PKIsigning eSeal degraded performance

Detected by Pingoru
Feb 26, 2026, 01:34 PM UTC
Resolved
Feb 26, 2026, 02:22 PM UTC
Duration
48m
Affected: Signing serviceDigiCert cloud certificate service
Timeline · 2 updates
  1. 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.

  2. resolved Feb 26, 2026, 02:22 PM UTC

    The supplier had a technical issue in their infrastructure. The incident has been resolved.

Read the full incident report →

Major February 3, 2026

PKIsigning eSeal unavailable

Detected by Pingoru
Feb 03, 2026, 02:59 PM UTC
Resolved
Feb 03, 2026, 03:20 PM UTC
Duration
21m
Affected: Signing serviceDigiCert eSeal service
Timeline · 3 updates
  1. 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.

  2. 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.

  3. resolved Feb 03, 2026, 03:20 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor February 2, 2026

Digipoort availability issues

Detected by Pingoru
Feb 02, 2026, 11:01 AM UTC
Resolved
Feb 02, 2026, 08:35 PM UTC
Duration
9h 33m
Affected: Logius Digipoort
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Minor November 12, 2025

DigiCert ONE degraded performance

Detected by Pingoru
Nov 12, 2025, 07:54 AM UTC
Resolved
Nov 13, 2025, 09:24 AM UTC
Duration
1d 1h
Affected: DigiCert cloud certificate service
Timeline · 3 updates
  1. 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.

  2. investigating Nov 13, 2025, 09:24 AM UTC

    DigiCert has implemented a fix and the issue is resolved.

  3. resolved Nov 13, 2025, 09:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 20, 2025

Verminderde beschikbaarheid PKIsigning platform

Detected by Pingoru
Mar 20, 2025, 01:42 PM UTC
Resolved
Mar 20, 2025, 02:19 PM UTC
Duration
37m
Affected: Signing serviceSMS verification servicePKIsigning authentication serverPKIsigning platform backend and APIDigiCert eSeal servicePKIsigning platform Front-endDigiCert Timestamp serviceWhatsapp verification serviceDigiCert cloud certificate serviceBatavia XBRL Render serviceDigidentity cloud certificate serviceLogius Digipoort
Timeline · 3 updates
  1. investigating Mar 20, 2025, 01:42 PM UTC

    We ervaren momenteel een verstoring op het PKIsigning platform. Functionaliteit kan tijdelijk minder beschikbaar zijn. We zijn bezig met een oplossing.

  2. monitoring Mar 20, 2025, 02:00 PM UTC

    We hebben het probleem gevonden en opgelost. We blijven de situatie monitoren.

  3. resolved Mar 20, 2025, 02:19 PM UTC

    Het probleem is verholpen.

Read the full incident report →

Critical March 12, 2025

Ondertekenen met DigiCert One certificaten niet mogelijk

Detected by Pingoru
Mar 12, 2025, 09:51 AM UTC
Resolved
Mar 12, 2025, 01:53 PM UTC
Duration
4h 1m
Affected: DigiCert cloud certificate service
Timeline · 3 updates
  1. investigating Mar 12, 2025, 09:51 AM UTC

    Opnieuw zijn er problemen bij DigiCert One. Ondertekenen met DigiCert One certificaten is momenteel niet mogelijk. Zie voor meer informatie: https://status.digicert.com/incidents/f4qgjj9gp8k7

  2. monitoring Mar 12, 2025, 10:02 AM UTC

    DigiCert heeft het probleem verholpen en blijft de resultaten in de gaten houden.

  3. resolved Mar 12, 2025, 01:53 PM UTC

    Het probleem is door DigiCert verholpen.

Read the full incident report →

Critical March 11, 2025

Ondertekenen met DigiCert certificaten niet mogelijk

Detected by Pingoru
Mar 11, 2025, 10:27 AM UTC
Resolved
Mar 11, 2025, 11:22 AM UTC
Duration
54m
Affected: DigiCert cloud certificate service
Timeline · 3 updates
  1. investigating Mar 11, 2025, 10:27 AM UTC

    Digicert heeft momenteel te maken met een verstoring van het DigiCert One platform. Daardoor is het niet mogelijk om te ondertekenen met DigiCert certificaten. Voor meer informatie zie: https://status.digicert.com/

  2. monitoring Mar 11, 2025, 10:37 AM UTC

    Het issue lijkt verholpen. We blijven de situatie monitoren.

  3. resolved Mar 11, 2025, 11:22 AM UTC

    Het issue is verholpen.

Read the full incident report →

Minor January 23, 2025

Performance problemen

Detected by Pingoru
Jan 23, 2025, 09:15 AM UTC
Resolved
Jan 23, 2025, 01:18 PM UTC
Duration
4h 2m
Affected: PKIsigning platform backend and API
Timeline · 4 updates
  1. investigating Jan 23, 2025, 09:15 AM UTC

    Op dit moment bestaan er performance problemen op het platform. Wij zijn bezig met het onderzoeken van de oorzaak.

  2. identified Jan 23, 2025, 09:21 AM UTC

    De oorzaak van de performance problemen is gevonden en er wordt gewerkt aan een oplossing.

  3. monitoring Jan 23, 2025, 10:10 AM UTC

    De performance problemen lijken verholpen. We blijven het voorlopig monitoren.

  4. resolved Jan 23, 2025, 01:18 PM UTC

    Het performanceprobleem is definitief verholpe. Wij zien geen verstoringen meer in de snelheid van het platform.

Read the full incident report →

Critical January 22, 2025

Technische storing

Detected by Pingoru
Jan 22, 2025, 02:21 PM UTC
Resolved
Jan 22, 2025, 02:48 PM UTC
Duration
26m
Affected: Signing serviceSMS verification servicePKIsigning authentication serverPKIsigning platform backend and APIDigiCert eSeal servicePKIsigning platform Front-endDigiCert Timestamp serviceWhatsapp verification serviceDigiCert cloud certificate serviceBatavia XBRL Render serviceDigidentity cloud certificate serviceLogius Digipoort
Timeline · 2 updates
  1. identified Jan 22, 2025, 02:21 PM UTC

    Als gevolg van een technisch probleem is het platform tijdelijk niet beschikbaar. Het is niet mogelijk om te ondertekenen op dit moment. We werken aan een oplossing en verwachten dat het voor 16 uur is opgelost. Excuses voor het ongemak.

  2. resolved Jan 22, 2025, 02:48 PM UTC

    Het platform is weer beschikbaar.

Read the full incident report →

Major January 15, 2025

Storing bij SBR (KvK/Belastingdienst)

Detected by Pingoru
Jan 15, 2025, 11:41 AM UTC
Resolved
Jan 15, 2025, 02:35 PM UTC
Duration
2h 53m
Timeline · 2 updates
  1. investigating Jan 15, 2025, 11:41 AM UTC

    Op dit moment is er een storing bij Digipoort waardoor jaarrekeningen en aangiften via SBR niet aangeleverd kunnen worden bij KvK en Belastingdienst. Wij hebben het aanleveren van berichten naar Digipoort daarom gepauzeerd. Berichten worden bewaard en aangeboden zodra Digipoort weer beschikbaar is. Dit heeft geen nadelige gevolgen voor documenten die nu worden klaargezet. Documenten die door deze problemen wel een foutstatus hebben gekregen zullen wij herstellen en opnieuw indienen.

  2. resolved Jan 15, 2025, 02:35 PM UTC

    Logius meldt dat de storing is opgelost. Het aanbieden van stukken aan Digipoort zal worden hervat.

Read the full incident report →

Critical January 14, 2025

Storing Digipoort SBR (KvK/Belastingdienst)

Detected by Pingoru
Jan 14, 2025, 02:02 PM UTC
Resolved
Jan 15, 2025, 08:06 AM UTC
Duration
18h 3m
Affected: Logius Digipoort
Timeline · 3 updates
  1. identified Jan 14, 2025, 02:02 PM UTC

    Op dit moment is er een storing bij Digipoort waardoor jaarrekeningen en aangiften via SBR niet aangeleverd kunnen worden bij KvK en Belastingdienst. Logius meldt deze verstoring en werkt aan een oplossing. Berichten worden opnieuw aangeboden zodra Digipoort weer beschikbaar is. Het kan zijn dat er een status fout wordt getoond maar dit wordt dus later door ons opgelost.

  2. identified Jan 14, 2025, 06:53 PM UTC

    We hebben helaas nog geen update van Logius ontvangen. Wij blijven dit continu monitoren. Verzoeken voor Digipoort kunnen worden klaargezet. Wij zorgen ervoor dat deze op een later moment worden verzonden.

  3. resolved Jan 15, 2025, 08:06 AM UTC

    Gisteravond is de storing bij Digipoort opgelost. Wij zorgen ervoor alle aanleveringen (opnieuw) bij Digipoort worden aangeleverd. NB: Als er reeds een foutstatus in AFAS aanwezig is dan kunnen wij deze niet herstellen.

Read the full incident report →

Major November 18, 2024

Filing with audit report (Deponeren met verklaring / SBR Assurance) not working

Detected by Pingoru
Nov 18, 2024, 11:22 AM UTC
Resolved
Nov 18, 2024, 04:22 PM UTC
Duration
4h 59m
Affected: Signing service
Timeline · 3 updates
  1. identified Nov 18, 2024, 11:22 AM UTC

    We are currently experiencing issues with 'Filing with Audit report' requests a.k.a. SBR Assurance. All requests of this type that have been sent since Thursday the 14th of november at 19.00, cannot be processed by DigiPoort because of an incompatibility issue. We have temporarily deactivated the request type, so new requests cannot be created at this point. For requests that meet the above criteria that have already been sent, the following applies: - Requests that have been completed, will get a failed status and cannot be repaired. They will have to be recreated and resent as soon as we have implemented a fix for this issue. - Requests that have been signed, but have not yet been approved, will have to be withdrawn. They need to be recreated and resent as soon as we have implemented a fix for this issue. We will contact all clients that have requests that meet the above criteria today.

  2. monitoring Nov 18, 2024, 02:36 PM UTC

    We have prepared a fix for the issue which will be deployed at 17.00 today.

  3. resolved Nov 18, 2024, 04:22 PM UTC

    We have deployed the fix and have reactivated the request type.

Read the full incident report →

Notice November 15, 2024

Degraded performance for 10 minutes

Detected by Pingoru
Nov 15, 2024, 02:17 PM UTC
Resolved
Nov 15, 2024, 02:33 PM UTC
Duration
15m
Affected: Signing serviceSMS verification servicePKIsigning authentication serverPKIsigning platform backend and APIDigiCert eSeal servicePKIsigning platform Front-endDigiCert Timestamp serviceWhatsapp verification serviceDigiCert cloud certificate serviceBatavia XBRL Render serviceDigidentity cloud certificate serviceLogius Digipoort
Timeline · 4 updates
  1. investigating Nov 15, 2024, 02:17 PM UTC

    In order to resolve an issue, there might be some degraded performance within the next 10 minutes.

  2. identified Nov 15, 2024, 02:18 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 15, 2024, 02:29 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Nov 15, 2024, 02:33 PM UTC

    This incident has been resolved.

Read the full incident report →