Update timeline
- resolved Mar 09, 2026, 10:00 PM UTC
Type: Incident Duration: 15 minutes Affected Components: API, API Mar 9, 22:00:00 GMT+0 - Investigating - We are currently investigating this incident. Mar 9, 22:15:00 GMT+0 - Resolved - This incident has been resolved. Mar 15, 08:12:30 GMT+0 - Postmortem - The incident was caused by a regression in the middleware layer responsible for header parsing. The logic error prevented the middleware from correctly validating standard request headers, leading to a surge in 400 Bad Request responses. Full RCA will be delivered upon request, reach out to support for that.
Looking to track Descope downtime and outages?
Pingoru polls Descope's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Descope reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Descope alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
Start monitoring Descope for free
5 free monitors · No credit card required