Signicat incident

Incident on 3rd party service - iDIN

Resolved after 22 hours 18 minutes, affecting iDIN, on May 28, 2026.

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.

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.

Your product runs on more than Signicat

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →