Descope had 7 outages in the last 2 years totaling 1h 1m of downtime — averaging 0.3 incidents per month.
There were 7 Descope outages since October 20, 2025 totaling 1h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this incident. seems related to our CDN provider, seems to be only affecting small number of requests
We are continuing to work on a fix for this incident. Seems related to CDN provider
This incident has been resolved.
Type: Incident Duration: 1 hour and 30 minutes Affected Components: API Mar 18, 10:45:26 GMT+0 - Investigating - We are currently investigating this incident. Mar 18, 12:15:43 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 18, 12:15:49 GMT+0 - Resolved - This incident has been resolved.
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.
Type: Incident Duration: 3 minutes Affected Components: , Console, API, US 🇺🇸 → Nov 23, 08:58:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 23, 09:00:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 23, 09:02:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 23, 09:03:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 2 hours and 32 minutes Affected Components: , API, US 🇺🇸 → Nov 18, 14:46:37 GMT+0 - Monitoring - Edge provider implemented a fix and are currently monitoring the result. Nov 18, 14:54:43 GMT+0 - Resolved - This incident has been resolved. Nov 18, 12:22:57 GMT+0 - Investigating - We are currently investigating this incident. Nov 18, 12:36:24 GMT+0 - Identified - we are seeing a recovery on latency and error rates
Type: Incident Duration: 1 hour and 2 minutes Affected Components: , Console, API, US 🇺🇸 → Oct 30, 13:55:00 GMT+0 - Investigating - We are currently investigating this incident. Oct 30, 14:00:00 GMT+0 - Monitoring - Error level went down, seems like momentarily issue with queueing system Oct 30, 14:01:00 GMT+0 - Resolved - This incident has been resolved. We will do a full post mortem, but from initial analysis it seems our internal queue system was overwhelmed from internal service creating very high amount of events in short period of time.
Type: Incident Duration: 3 hours and 38 minutes Affected Components: API Oct 20, 14:45:00 GMT+0 - Investigating - We are currently investigating this incident. Related to AWS outage in lambda service Oct 20, 16:31:40 GMT+0 - Identified - We are continuing to work on a fix for this incident. Issue related to high error rate on AWS lambda service, working on mitigating issue Oct 20, 17:53:55 GMT+0 - Monitoring - Fix was implemented by our cloud provider and we are currently monitoring the result. Oct 20, 18:23:10 GMT+0 - Resolved - This incident has been resolved.