- 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
-
investigating Jul 24, 2026, 08:03 AM UTC
All signatures using the PKisigning eSeal certificate are currently not working. We are investigating the issue.
-
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
-
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.
-
resolved Jul 24, 2026, 12:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 10:12 AM UTC
- Resolved
- May 11, 2026, 12:14 PM UTC
- Duration
- 3d 2h
Affected: DigiCert cloud certificate service
Timeline · 9 updates
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
-
monitoring Mar 20, 2025, 02:00 PM UTC
We hebben het probleem gevonden en opgelost. We blijven de situatie monitoren.
-
resolved Mar 20, 2025, 02:19 PM UTC
Het probleem is verholpen.
Read the full incident report →
- 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
-
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
-
monitoring Mar 12, 2025, 10:02 AM UTC
DigiCert heeft het probleem verholpen en blijft de resultaten in de gaten houden.
-
resolved Mar 12, 2025, 01:53 PM UTC
Het probleem is door DigiCert verholpen.
Read the full incident report →
- 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
-
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/
-
monitoring Mar 11, 2025, 10:37 AM UTC
Het issue lijkt verholpen. We blijven de situatie monitoren.
-
resolved Mar 11, 2025, 11:22 AM UTC
Het issue is verholpen.
Read the full incident report →
- 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
-
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.
-
identified Jan 23, 2025, 09:21 AM UTC
De oorzaak van de performance problemen is gevonden en er wordt gewerkt aan een oplossing.
-
monitoring Jan 23, 2025, 10:10 AM UTC
De performance problemen lijken verholpen. We blijven het voorlopig monitoren.
-
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 - 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
-
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.
-
resolved Jan 22, 2025, 02:48 PM UTC
Het platform is weer beschikbaar.
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2025, 11:41 AM UTC
- Resolved
- Jan 15, 2025, 02:35 PM UTC
- Duration
- 2h 53m
Timeline · 2 updates
-
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.
-
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 - 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
monitoring Nov 18, 2024, 02:36 PM UTC
We have prepared a fix for the issue which will be deployed at 17.00 today.
-
resolved Nov 18, 2024, 04:22 PM UTC
We have deployed the fix and have reactivated the request type.
Read the full incident report →
- 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
-
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.
-
identified Nov 15, 2024, 02:18 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Nov 15, 2024, 02:29 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 15, 2024, 02:33 PM UTC
This incident has been resolved.
Read the full incident report →
Critical September 23, 2024 - Detected by Pingoru
- Sep 23, 2024, 07:29 AM UTC
- Resolved
- Sep 23, 2024, 07:55 AM UTC
- Duration
- 26m
Affected: Batavia XBRL Render service
Timeline · 2 updates
-
investigating Sep 23, 2024, 07:29 AM UTC
We are currently investigating the issue.
-
resolved Sep 23, 2024, 07:55 AM UTC
One of our integrators was experiencing an outage in their infrastructure. A fix has been implemented. There might be API requests with XBRL files that have a failed status caused by this issue. We will fix these within the next hours. No action is required.
Read the full incident report →
