Signicat incident

Service Disruption - Multiple methods

Critical Resolved View vendor source →

Signicat experienced a critical incident on March 17, 2026 affecting Portal and Portal API and .beID and 1 more component, lasting 2h 13m. The incident has been resolved; the full update timeline is below.

Started
Mar 17, 2026, 02:03 PM UTC
Resolved
Mar 17, 2026, 04:17 PM UTC
Duration
2h 13m
Detected by Pingoru
Mar 17, 2026, 02:03 PM UTC

Affected components

Portal and Portal API.beIDBuypassExpress Signature APIDigiDeHerkenningAssure APIEmail OTPEstonian ID CardFinnish Bank eIDs (FTN)

Update timeline

  1. investigating Mar 17, 2026, 02:03 PM UTC

    We might be experiencing issues and are currently investigating this issue.

  2. investigating Mar 17, 2026, 02:28 PM UTC

    We are continuing to investigate the ongoing incident. Signicat is treating this as an all-hands on deck situation, and we are giving it our highest priorities and resources.

  3. investigating Mar 17, 2026, 02:53 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 17, 2026, 03:12 PM UTC

    We are continuing to investigate this issue.

  5. investigating Mar 17, 2026, 03:20 PM UTC

    We are continuing to investigate this issue. Work is ongoing to resolve issues, and we are seeing signs of improvement.

  6. investigating Mar 17, 2026, 03:30 PM UTC

    We have implemented a fix and see significant improvement. We will continue investigating the issue and monitor the situation closely.

  7. monitoring Mar 17, 2026, 03:48 PM UTC

    Our services are operational, but we are continuing to monitor closely.

  8. resolved Mar 17, 2026, 04:17 PM UTC

    This incident is resolved. We are working with our providers to find the exact cause. We are also working on another mitigation on our side, in the event this issue appears again.