Live
D

Descope

Descope is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Descope status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Descope since . The days before that show only what Descope published.

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

8
Console Operational
90 days agoNo incidentsToday

US πŸ‡ΊπŸ‡Έ

API Operational
90 days agoNo incidentsToday

EU πŸ‡ͺπŸ‡Ί

API Operational
90 days agoNo incidentsToday

AP πŸ‡¦πŸ‡Ί

API Operational
90 days agoNo incidentsToday

CA πŸ‡¨πŸ‡¦

API Operational
90 days agoNo incidentsToday

SA πŸ‡§πŸ‡·

API Operational
90 days agoNo incidentsToday

UK πŸ‡¬πŸ‡§

API Operational
90 days agoNo incidentsToday

SG πŸ‡ΈπŸ‡¬

API Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Follow Descope

Your coding agent knows when Descope is down, and tells you when a failure is theirs, not yours. You can also get Descope incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "descope" and tell me if Descope has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=descope
Slack
/feed subscribe https://outages.live/feed.xml?providers=descope

Go from tracking outages to fixing production issues with Polylane.

Try Polylane