Changes / Drata / Some customers unable to login

Drata: Critical incident: Some customers unable to login

Summary

Some Drata customers could not log in to the Web Application during a critical incident that started at 2025-11-04 03:51 UTC and lasted 22 h 55 min, resolving at 2025-11-05 02:46 UTC. Drata identified the root cause without disclosing it and deployed a fix to all regions.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 100%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Some customers unable to login
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-11-04 03:51 UTC
AddedResolved time#5
Before: not present
After: 2025-11-05 02:46 UTC
AddedAffected components#6
Before: not present
After: Web Application
AddedUpdateinvestigating#7
Before: not present
After: Our team is currently investigating an issue in which some customers are unable to login. We will provide updates as they become available.
AddedUpdateidentified#8
Before: not present
After: The root cause of the issue has been identified. We are actively working on a fix.
AddedUpdateidentified#9
Before: not present
After: A fix for the issue has been implemented. We are actively deploying the fix to all regions.
AddedUpdatemonitoring#10
Before: not present
After: A fix for the issue has been deployed. The team will continue to monitor.
AddedUpdateresolved#11
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Critical incident: Some customers unable to login (this change)
Some Drata customers could not log in to the Web Application during a critical incident that started at 2025-11-04 03:51 UTC and lasted 22 h 55 min, resolving at 2025-11-05 02:46 UTC. Drata identified the root cause without disclosing it and deployed a fix to all regions.
Major incident

All Drata changes → · Drata profile · Markdown · JSON