Signicat incident

Incident on 3rd party service - iDIN

Major Resolved View vendor source →

Signicat experienced a major incident on May 28, 2026 affecting iDIN, lasting 22h 18m. The incident has been resolved; the full update timeline is below.

Started
May 28, 2026, 01:30 PM UTC
Resolved
May 29, 2026, 11:48 AM UTC
Duration
22h 18m
Detected by Pingoru
May 28, 2026, 01:30 PM UTC

Affected components

iDIN

Update timeline

  1. monitoring May 28, 2026, 11:12 PM UTC

    An incident is currently affecting iDIN Our connection towards this 3rd party service is running but is not functioning properly as a result of their incident. We are monitoring their progression towards resolution.

  2. monitoring May 29, 2026, 07:45 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring May 29, 2026, 07:46 AM UTC

    We are continuing to monitor for any further issues.

  4. monitoring May 29, 2026, 08:05 AM UTC

    We are continuing to monitor for any further issues.

  5. monitoring May 29, 2026, 08:57 AM UTC

    We are seing improvements in our Dashboard and api.signicat.com-endpoints. id.signicat.com and Enterprise is still affected.

  6. monitoring May 29, 2026, 11:15 AM UTC

    All platforms are operational and we are seeing completed transactions. We will monitor a bit before resolving the incident.

  7. resolved May 29, 2026, 11:48 AM UTC

    This incident has been resolved.