Descope had 13 outages in the last 2 years — averaging 0.5 incidents per month.
There were 13 Descope outages since February 5, 2025. Each is summarised below — incident details, duration, and resolution information.
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.
Type: Incident Duration: 53 minutes Affected Components: Console, , API, , API, US 🇺🇸 → EU 🇪🇺 → Aug 20, 11:31:00 GMT+0 - Resolved - This incident has been resolved. About 2% of the traffic was affected, most of which originated from the Descope Console application. Aug 20, 10:54:00 GMT+0 - Identified - We have identified and working on addressing the incident that is causing login failures in both the US and EU data centers Aug 20, 11:20:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 52 minutes Affected Components: , API, API, , US 🇺🇸 → EU 🇪🇺 → Jun 12, 19:04:00 GMT+0 - Identified - The incident appears to be related to an outage of a few internet services. We are in touch with our partners to remediate the issue. Jun 12, 19:07:00 GMT+0 - Resolved - This incident has been resolved. Jun 12, 19:02:00 GMT+0 - Investigating - We are currently investigating this incident.
Type: Incident Duration: 1 day and 5 hours Affected Components: Console, API May 21, 15:32:00 GMT+0 - Resolved - This incident has been resolved. The root cause was an expired configuration between the US Descope cluster and the EU region. Only management key functionality on EU projects was impacted. EU project authentication services were not affected. May 21, 15:03:00 GMT+0 - Investigating - We are investigating reports of missing EU projects in the Descope console and management keys not working correctly for EU projects.
Type: Incident Duration: 15 minutes Affected Components: Console May 17, 20:00:00 GMT+0 - Identified - Descope Console experienced a DNS issue, which may still cause access issues for the next few minutes. The system is up and running, and there is no affect on the authentication services. May 17, 20:15:00 GMT+0 - Resolved - Descope console DNS is fully recovered
Type: Incident Duration: 47 minutes Affected Components: API, API Mar 22, 18:50:00 GMT+0 - Monitoring - The team has identified and resolved the issue. We are continuing to monitor and will update with any further details. Mar 22, 19:01:39 GMT+0 - Resolved - We experienced an issue with our Web Application Firewall (WAF). This resulted from a false-positive detection in our WAF that blocked suspected NextJS vulnerability. A handful of NextJS applications were affected. The protection rule was fixed and services are now operational. Mar 22, 18:15:00 GMT+0 - Investigating - We are currently investigating degraded performance against the Descope API.
Type: Incident Duration: 3 hours and 56 minutes Affected Components: API, Console, API Feb 5, 16:36:06 GMT+0 - Investigating - We are currently investigating this incident. Feb 5, 17:44:51 GMT+0 - Identified - We identified the root cause, which seems related to our CDN provider's network performance issues. We are working closely with them to remediate those issues. Our reports show that less than 30% of the overall requests are affected by this issue. Feb 5, 18:20:27 GMT+0 - Monitoring - A fix was implemented, and API performance is now back to normal levels. We continue to monitor the system to ensure optimal performance of all components. Feb 5, 20:32:35 GMT+0 - Resolved - The system is stable since fixes were applied.