Zitadel incident

Investigating Potentially Degraded Performance

Minor Resolved View vendor source →

Zitadel experienced a minor incident on June 29, 2026, lasting 3h 16m. The incident has been resolved; the full update timeline is below.

Started
Jun 29, 2026, 06:48 AM UTC
Resolved
Jun 29, 2026, 10:04 AM UTC
Duration
3h 16m
Detected by Pingoru
Jun 29, 2026, 06:48 AM UTC

Update timeline

  1. investigating Jun 29, 2026, 06:48 AM UTC

    Status: Investigating We are currently investigating reports of issues affecting our service. Our team is actively working to identify the cause of the problem. We will provide another update as soon as we have more information. Affected components Application Authentication (M2M / Client) (Degraded performance) User Authentication (Login) (Degraded performance)

  2. investigating Jun 29, 2026, 07:34 AM UTC

    Status: Investigating We identified a potential problem that might affect a subset of customer. We are working on a resolution. Affected components Application Authentication (M2M / Client) (Degraded performance) User Authentication (Login) (Degraded performance)

  3. investigating Jun 29, 2026, 08:28 AM UTC

    Status: Investigating We identified a potential cause and are working to rollout a fix. Affected components Application Authentication (M2M / Client) (Degraded performance) User Authentication (Login) (Degraded performance)

  4. resolved Jun 29, 2026, 10:04 AM UTC

    Status: Resolved The issues affecting our service have been resolved, and all systems are now operating normally. We apologize for any disruption this may have caused. Affected components Application Authentication (M2M / Client) (Operational) User Authentication (Login) (Operational)