Skip to content

Outage tracker / Descope

Is Descope down?

I'm having a problem

Operationalchecked 5 minutes ago

We reached Descope from all 10 regions we check.

As of Oct 5, 2026, 8:59 PM UTC, Descope answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Descope (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:59 PM UTC
US-East248 msOperational
US-West173 msOperational
Europe259 msOperational
Asia-Pacific223 msOperational
US-Central191 msOperational
Canada279 msOperational
UK192 msOperational
Southeast Asia588 msOperational
Australia573 msOperational
South America174 msOperational
their status pagetheir claim, not our reading

Descope publishes no status feed we can read, so the only independent reading here is ours on the left.

Descope response time, by region

US-East
501msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 520ms2026-09-07 UTC: p95 558ms2026-09-08 UTC: p95 547ms2026-09-09 UTC: p95 538ms2026-09-10 UTC: p95 522ms2026-09-11 UTC: p95 528ms2026-09-12 UTC: p95 253ms2026-09-13 UTC: p95 267ms2026-09-14 UTC: p95 272ms2026-09-15 UTC: p95 282ms2026-09-16 UTC: p95 501ms2026-09-17 UTC: p95 537ms2026-09-18 UTC: p95 557ms2026-09-19 UTC: p95 550ms2026-09-20 UTC: p95 508ms2026-09-21 UTC: p95 492ms2026-09-22 UTC: p95 513ms2026-09-23 UTC: p95 479ms2026-09-24 UTC: p95 462ms2026-09-25 UTC: p95 444ms2026-09-26 UTC: p95 428ms2026-09-27 UTC: p95 420ms2026-09-28 UTC: p95 392ms2026-09-29 UTC: p95 464ms2026-09-30 UTC: p95 297ms2026-10-01 UTC: p95 362ms2026-10-02 UTC: p95 485ms2026-10-03 UTC: p95 515ms2026-10-04 UTC: p95 523ms2026-10-05 UTC: p95 501ms
Sep 6Sep 20Oct 5
US-West
658msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 248ms2026-09-07 UTC: p95 296ms2026-09-08 UTC: p95 299ms2026-09-09 UTC: p95 334ms2026-09-10 UTC: p95 369ms2026-09-11 UTC: p95 332ms2026-09-12 UTC: p95 363ms2026-09-13 UTC: p95 324ms2026-09-14 UTC: p95 434ms2026-09-15 UTC: p95 406ms2026-09-16 UTC: p95 225ms2026-09-17 UTC: p95 243ms2026-09-18 UTC: p95 227ms2026-09-19 UTC: p95 214ms2026-09-20 UTC: p95 327ms2026-09-21 UTC: p95 270ms2026-09-22 UTC: p95 420ms2026-09-23 UTC: p95 370ms2026-09-24 UTC: p95 350ms2026-09-25 UTC: p95 275ms2026-09-26 UTC: p95 333ms2026-09-27 UTC: p95 198ms2026-09-28 UTC: p95 246ms2026-09-29 UTC: p95 225ms2026-09-30 UTC: p95 218ms2026-10-01 UTC: p95 280ms2026-10-02 UTC: p95 264ms2026-10-03 UTC: p95 558ms2026-10-04 UTC: p95 602ms2026-10-05 UTC: p95 658ms
Sep 6Sep 20Oct 5
Europe
416msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 273ms2026-09-07 UTC: p95 310ms2026-09-08 UTC: p95 378ms2026-09-09 UTC: p95 329ms2026-09-10 UTC: p95 355ms2026-09-11 UTC: p95 373ms2026-09-12 UTC: p95 434ms2026-09-13 UTC: p95 362ms2026-09-14 UTC: p95 352ms2026-09-15 UTC: p95 340ms2026-09-16 UTC: p95 276ms2026-09-17 UTC: p95 355ms2026-09-18 UTC: p95 336ms2026-09-19 UTC: p95 416ms2026-09-20 UTC: p95 395ms2026-09-21 UTC: p95 390ms2026-09-22 UTC: p95 301ms2026-09-23 UTC: p95 282ms2026-09-24 UTC: p95 300ms2026-09-25 UTC: p95 313ms2026-09-26 UTC: p95 388ms2026-09-27 UTC: p95 420ms2026-09-28 UTC: p95 408ms2026-09-29 UTC: p95 477ms2026-09-30 UTC: p95 458ms2026-10-01 UTC: p95 411ms2026-10-02 UTC: p95 342ms2026-10-03 UTC: p95 360ms2026-10-04 UTC: p95 348ms2026-10-05 UTC: p95 416ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.0sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 969ms2026-09-07 UTC: p95 939ms2026-09-08 UTC: p95 904ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 945ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 789ms2026-09-13 UTC: p95 907ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 844ms2026-09-19 UTC: p95 829ms2026-09-20 UTC: p95 805ms2026-09-21 UTC: p95 846ms2026-09-22 UTC: p95 715ms2026-09-23 UTC: p95 685ms2026-09-24 UTC: p95 870ms2026-09-25 UTC: p95 671ms2026-09-26 UTC: p95 692ms2026-09-27 UTC: p95 802ms2026-09-28 UTC: p95 672ms2026-09-29 UTC: p95 619ms2026-09-30 UTC: p95 734ms2026-10-01 UTC: p95 730ms2026-10-02 UTC: p95 848ms2026-10-03 UTC: p95 756ms2026-10-04 UTC: p95 842ms2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
US-Central
496msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 754ms2026-09-07 UTC: p95 718ms2026-09-08 UTC: p95 732ms2026-09-09 UTC: p95 697ms2026-09-10 UTC: p95 637ms2026-09-11 UTC: p95 624ms2026-09-12 UTC: p95 244ms2026-09-13 UTC: p95 300ms2026-09-14 UTC: p95 314ms2026-09-15 UTC: p95 304ms2026-09-16 UTC: p95 282ms2026-09-17 UTC: p95 383ms2026-09-18 UTC: p95 291ms2026-09-19 UTC: p95 315ms2026-09-20 UTC: p95 274ms2026-09-21 UTC: p95 345ms2026-09-22 UTC: p95 519ms2026-09-23 UTC: p95 488ms2026-09-24 UTC: p95 554ms2026-09-25 UTC: p95 438ms2026-09-26 UTC: p95 730ms2026-09-27 UTC: p95 320ms2026-09-28 UTC: p95 314ms2026-09-29 UTC: p95 320ms2026-09-30 UTC: p95 375ms2026-10-01 UTC: p95 309ms2026-10-02 UTC: p95 322ms2026-10-03 UTC: p95 308ms2026-10-04 UTC: p95 435ms2026-10-05 UTC: p95 496ms
Sep 6Sep 20Oct 5
Canada
321msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 605ms2026-09-07 UTC: p95 660ms2026-09-08 UTC: p95 686ms2026-09-09 UTC: p95 669ms2026-09-10 UTC: p95 657ms2026-09-11 UTC: p95 586ms2026-09-12 UTC: p95 321ms2026-09-13 UTC: p95 358ms2026-09-14 UTC: p95 321ms2026-09-15 UTC: p95 337ms2026-09-16 UTC: p95 293ms2026-09-17 UTC: p95 302ms2026-09-18 UTC: p95 311ms2026-09-19 UTC: p95 286ms2026-09-20 UTC: p95 316ms2026-09-21 UTC: p95 350ms2026-09-22 UTC: p95 310ms2026-09-23 UTC: p95 361ms2026-09-24 UTC: p95 320ms2026-09-25 UTC: p95 299ms2026-09-26 UTC: p95 353ms2026-09-27 UTC: p95 311ms2026-09-28 UTC: p95 410ms2026-09-29 UTC: p95 279ms2026-09-30 UTC: p95 354ms2026-10-01 UTC: p95 371ms2026-10-02 UTC: p95 330ms2026-10-03 UTC: p95 291ms2026-10-04 UTC: p95 300ms2026-10-05 UTC: p95 321ms
Sep 6Sep 20Oct 5
UK
448msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 470ms2026-09-07 UTC: p95 430ms2026-09-08 UTC: p95 478ms2026-09-09 UTC: p95 409ms2026-09-10 UTC: p95 378ms2026-09-11 UTC: p95 301ms2026-09-12 UTC: p95 362ms2026-09-13 UTC: p95 351ms2026-09-14 UTC: p95 365ms2026-09-15 UTC: p95 352ms2026-09-16 UTC: p95 416ms2026-09-17 UTC: p95 356ms2026-09-18 UTC: p95 357ms2026-09-19 UTC: p95 361ms2026-09-20 UTC: p95 407ms2026-09-21 UTC: p95 302ms2026-09-22 UTC: p95 468ms2026-09-23 UTC: p95 371ms2026-09-24 UTC: p95 452ms2026-09-25 UTC: p95 348ms2026-09-26 UTC: p95 406ms2026-09-27 UTC: p95 349ms2026-09-28 UTC: p95 321ms2026-09-29 UTC: p95 402ms2026-09-30 UTC: p95 307ms2026-10-01 UTC: p95 380ms2026-10-02 UTC: p95 505ms2026-10-03 UTC: p95 549ms2026-10-04 UTC: p95 560ms2026-10-05 UTC: p95 448ms
Sep 6Sep 20Oct 5
Southeast Asia
1.0sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 896ms2026-09-07 UTC: p95 485ms2026-09-08 UTC: p95 524ms2026-09-09 UTC: p95 934ms2026-09-10 UTC: p95 835ms2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 973ms2026-09-13 UTC: p95 675ms2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 659ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 962ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 974ms2026-09-20 UTC: p95 911ms2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 884ms2026-09-29 UTC: p95 685ms2026-09-30 UTC: p95 887ms2026-10-01 UTC: p95 994ms2026-10-02 UTC: p95 982ms2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
Australia
748msp95 · latest
1s500ms0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 663ms2026-09-07 UTC: p95 537ms2026-09-08 UTC: p95 594ms2026-09-09 UTC: p95 660ms2026-09-10 UTC: p95 836ms2026-09-11 UTC: p95 416ms2026-09-12 UTC: p95 747ms2026-09-13 UTC: p95 755ms2026-09-14 UTC: p95 768ms2026-09-15 UTC: p95 817ms2026-09-16 UTC: p95 687ms2026-09-17 UTC: p95 788ms2026-09-18 UTC: p95 547ms2026-09-19 UTC: p95 854ms2026-09-20 UTC: p95 593ms2026-09-21 UTC: p95 434ms2026-09-22 UTC: p95 838ms2026-09-23 UTC: p95 463ms2026-09-24 UTC: p95 831ms2026-09-25 UTC: p95 862ms2026-09-26 UTC: p95 895ms2026-09-27 UTC: p95 521ms2026-09-28 UTC: p95 682ms2026-09-29 UTC: p95 454ms2026-09-30 UTC: p95 425ms2026-10-01 UTC: p95 622ms2026-10-02 UTC: p95 765ms2026-10-03 UTC: p95 833ms2026-10-04 UTC: p95 586ms2026-10-05 UTC: p95 748ms
Sep 6Sep 20Oct 5
South America
536msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 547ms2026-09-07 UTC: p95 407ms2026-09-08 UTC: p95 630ms2026-09-09 UTC: p95 546ms2026-09-10 UTC: p95 559ms2026-09-11 UTC: p95 615ms2026-09-12 UTC: p95 644ms2026-09-13 UTC: p95 486ms2026-09-14 UTC: p95 561ms2026-09-15 UTC: p95 525ms2026-09-16 UTC: p95 590ms2026-09-17 UTC: p95 637ms2026-09-18 UTC: p95 573ms2026-09-19 UTC: p95 629ms2026-09-20 UTC: p95 519ms2026-09-21 UTC: p95 585ms2026-09-22 UTC: p95 580ms2026-09-23 UTC: p95 615ms2026-09-24 UTC: p95 505ms2026-09-25 UTC: p95 752ms2026-09-26 UTC: p95 573ms2026-09-27 UTC: p95 620ms2026-09-28 UTC: p95 656ms2026-09-29 UTC: p95 932ms2026-09-30 UTC: p95 464ms2026-10-01 UTC: p95 647ms2026-10-02 UTC: p95 627ms2026-10-03 UTC: p95 656ms2026-10-04 UTC: p95 639ms2026-10-05 UTC: p95 536ms
Sep 6Sep 20Oct 5

Is it Descope, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Descope -- it cannot diagnose Descope's own systems.

What we measured, function by function

Descope answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Descope go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Descope, and again when they can reach it again. That is our own measurement from ten regions, not Descope's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 248msstatus code: 401checked: Oct 5, 2026, 8:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Descope normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 173msstatus code: 401checked: Oct 5, 2026, 8:37 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Descope normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 191msstatus code: 401checked: Oct 5, 2026, 8:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Descope normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 279msstatus code: 401checked: Oct 5, 2026, 8:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Descope normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 174msstatus code: 401checked: Oct 5, 2026, 8:24 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Descope normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 259msstatus code: 401checked: Oct 5, 2026, 8:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Descope normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 192msstatus code: 401checked: Oct 5, 2026, 8:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Descope normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 223msstatus code: 401checked: Oct 5, 2026, 8:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Descope normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 588msstatus code: 401checked: Oct 5, 2026, 8:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Descope normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 573msstatus code: 401checked: Oct 5, 2026, 8:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Descope normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Descope, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Descope yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Descope.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Descope since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Descope covering any window you pick, with our measurements and Descope's own claim at the time, side by side.

Full availability history for Descope: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Descope uptime measured by RealUptimeLive, from this page's own readings.
[![Descope uptime measured by RealUptime](https://realuptime.io/outages/descope/badge.svg?days=30)](https://realuptime.io/outages/descope)
<a href="https://realuptime.io/outages/descope"><img src="https://realuptime.io/outages/descope/badge.svg?days=30" alt="Descope uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Descope's SLA implies, from our measurement

At or above your target

We measured none of downtime for Descope over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Descope's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://api.descope.com/v1/auth/me
secondary
https://www.descope.com/
RealUptime is not affiliated with Descope; the name identifies what we measured, and nothing here speaks for Descope's own team. We send a single web request to Descope from 10 regions on our own schedule and time the response. We do not see inside Descope's systems, do not use an account or real transaction, and are not the same signal Descope's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Descope is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.