Criipto incident

MitID instability

Critical Resolved View vendor source →
Started
Mar 31, 2026, 07:24 AM UTC
Resolved
Mar 31, 2026, 12:27 PM UTC
Duration
5h 2m
Detected by Pingoru
Mar 31, 2026, 07:24 AM UTC

Affected components

MitID (Denmark)

Update timeline

  1. identified Mar 31, 2026, 07:24 AM UTC

    IN Groupe reports that MitID Web sites and API services might experience instability.

  2. identified Mar 31, 2026, 08:16 AM UTC

    Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem.

  3. identified Mar 31, 2026, 09:09 AM UTC

    Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem. No ETAs provided.

  4. identified Mar 31, 2026, 10:05 AM UTC

    Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem. No ETAs provided.

  5. identified Mar 31, 2026, 11:34 AM UTC

    Update from IN Groupe: Update from IN Groupe: The MitID Production infrastructure is still experiencing instability. We are working on solving the problem. (Same update as previous updates, no new information or ETA)

  6. resolved Mar 31, 2026, 12:27 PM UTC

    IN Groupe reports that the incident has been resolved.

Looking to track Criipto downtime and outages?

Pingoru polls Criipto's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Criipto reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Criipto alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Criipto for free

5 free monitors · No credit card required