Skip to content

Outage tracker / Descope

Is Descope down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of Descope pass from all 10 regions we check.

As of Oct 23, 2026, 7:58 PM UTC, RealUptime's checks of Descope passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Descope did not fail from two or more distant regions in the 62 days we have checked it (since Aug 22, 2026). This does not show Descope works for users.

our check readinglive · checked Oct 23, 2026, 7:58 PM UTC
US-East958 msChecks passing
US-West201 msChecks passing
Europe424 msChecks passing
Asia-Pacific646 msChecks passing
US-Central290 msChecks passing
Canada160 msChecks passing
UK162 msChecks passing
Southeast Asia609 msChecks passing
Australia368 msChecks passing
South America11898 msChecks passing
their status pagetheir claim, not our reading

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

Descope response time, by region

US-East
1.0sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 498ms2026-10-06 UTC: p95 307ms2026-10-07 UTC: p95 296ms2026-10-08 UTC: p95 354ms2026-10-09 UTC: p95 338ms2026-10-10 UTC: p95 280ms2026-10-11 UTC: p95 263ms2026-10-12 UTC: p95 295ms2026-10-13 UTC: p95 497ms2026-10-14 UTC: p95 550ms2026-10-15 UTC: p95 521ms2026-10-16 UTC: p95 551ms2026-10-17 UTC: p95 606ms2026-10-18 UTC: p95 983ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 552ms2026-10-23 UTC: p95 1.0s
Sep 24Oct 8Oct 23
US-West
425msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 674ms2026-10-06 UTC: p95 253ms2026-10-07 UTC: p95 232ms2026-10-08 UTC: p95 233ms2026-10-09 UTC: p95 228ms2026-10-10 UTC: p95 257ms2026-10-11 UTC: p95 220ms2026-10-12 UTC: p95 579ms2026-10-13 UTC: p95 719ms2026-10-14 UTC: p95 699ms2026-10-15 UTC: p95 532ms2026-10-16 UTC: p95 544ms2026-10-17 UTC: p95 718ms2026-10-18 UTC: p95 741ms2026-10-19 UTC: p95 800ms2026-10-20 UTC: p95 587ms2026-10-21 UTC: p95 810ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 425ms
Sep 24Oct 8Oct 23
Europe
767msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-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 414ms2026-10-06 UTC: p95 485ms2026-10-07 UTC: p95 637ms2026-10-08 UTC: p95 445ms2026-10-09 UTC: p95 497ms2026-10-10 UTC: p95 650ms2026-10-11 UTC: p95 568ms2026-10-12 UTC: p95 558ms2026-10-13 UTC: p95 508ms2026-10-14 UTC: p95 621ms2026-10-15 UTC: p95 668ms2026-10-16 UTC: p95 598ms2026-10-17 UTC: p95 608ms2026-10-18 UTC: p95 658ms2026-10-19 UTC: p95 709ms2026-10-20 UTC: p95 574ms2026-10-21 UTC: p95 529ms2026-10-22 UTC: p95 679ms2026-10-23 UTC: p95 767ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.7sp95 · 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-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.0s2026-10-06 UTC: p95 772ms2026-10-07 UTC: p95 719ms2026-10-08 UTC: p95 739ms2026-10-09 UTC: p95 791ms2026-10-10 UTC: p95 704ms2026-10-11 UTC: p95 745ms2026-10-12 UTC: p95 808ms2026-10-13 UTC: p95 702ms2026-10-14 UTC: p95 734ms2026-10-15 UTC: p95 723ms2026-10-16 UTC: p95 817ms2026-10-17 UTC: p95 784ms2026-10-18 UTC: p95 786ms2026-10-19 UTC: p95 650ms2026-10-20 UTC: p95 767ms2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.7s
Sep 24Oct 8Oct 23
US-Central
308msp95 · 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-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 466ms2026-10-06 UTC: p95 289ms2026-10-07 UTC: p95 320ms2026-10-08 UTC: p95 342ms2026-10-09 UTC: p95 288ms2026-10-10 UTC: p95 284ms2026-10-11 UTC: p95 366ms2026-10-12 UTC: p95 321ms2026-10-13 UTC: p95 310ms2026-10-14 UTC: p95 285ms2026-10-15 UTC: p95 494ms2026-10-16 UTC: p95 288ms2026-10-17 UTC: p95 292ms2026-10-18 UTC: p95 286ms2026-10-19 UTC: p95 488ms2026-10-20 UTC: p95 313ms2026-10-21 UTC: p95 518ms2026-10-22 UTC: p95 591ms2026-10-23 UTC: p95 308ms
Sep 24Oct 8Oct 23
Canada
313msp95 · 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-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 351ms2026-10-06 UTC: p95 325ms2026-10-07 UTC: p95 290ms2026-10-08 UTC: p95 300ms2026-10-09 UTC: p95 308ms2026-10-10 UTC: p95 322ms2026-10-11 UTC: p95 341ms2026-10-12 UTC: p95 279ms2026-10-13 UTC: p95 297ms2026-10-14 UTC: p95 353ms2026-10-15 UTC: p95 314ms2026-10-16 UTC: p95 428ms2026-10-17 UTC: p95 290ms2026-10-18 UTC: p95 314ms2026-10-19 UTC: p95 338ms2026-10-20 UTC: p95 445ms2026-10-21 UTC: p95 335ms2026-10-22 UTC: p95 514ms2026-10-23 UTC: p95 313ms
Sep 24Oct 8Oct 23
UK
244msp95 · 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-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 443ms2026-10-06 UTC: p95 465ms2026-10-07 UTC: p95 367ms2026-10-08 UTC: p95 377ms2026-10-09 UTC: p95 421ms2026-10-10 UTC: p95 346ms2026-10-11 UTC: p95 336ms2026-10-12 UTC: p95 416ms2026-10-13 UTC: p95 514ms2026-10-14 UTC: p95 280ms2026-10-15 UTC: p95 239ms2026-10-16 UTC: p95 390ms2026-10-17 UTC: p95 478ms2026-10-18 UTC: p95 371ms2026-10-19 UTC: p95 435ms2026-10-20 UTC: p95 308ms2026-10-21 UTC: p95 418ms2026-10-22 UTC: p95 416ms2026-10-23 UTC: p95 244ms
Sep 24Oct 8Oct 23
Southeast Asia
1.1sp95 · 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-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.0s2026-10-06 UTC: p95 733ms2026-10-07 UTC: p95 875ms2026-10-08 UTC: p95 997ms2026-10-09 UTC: p95 679ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 792ms2026-10-12 UTC: p95 984ms2026-10-13 UTC: p95 637ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 985ms2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 973ms2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
Australia
537msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 862ms2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 422ms2026-10-08 UTC: p95 785ms2026-10-09 UTC: p95 426ms2026-10-10 UTC: p95 748ms2026-10-11 UTC: p95 432ms2026-10-12 UTC: p95 444ms2026-10-13 UTC: p95 456ms2026-10-14 UTC: p95 689ms2026-10-15 UTC: p95 832ms2026-10-16 UTC: p95 562ms2026-10-17 UTC: p95 770ms2026-10-18 UTC: p95 730ms2026-10-19 UTC: p95 794ms2026-10-20 UTC: p95 432ms2026-10-21 UTC: p95 478ms2026-10-22 UTC: p95 407ms2026-10-23 UTC: p95 537ms
Sep 24Oct 8Oct 23
South America
2.2sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 528ms2026-10-06 UTC: p95 692ms2026-10-07 UTC: p95 802ms2026-10-08 UTC: p95 487ms2026-10-09 UTC: p95 482ms2026-10-10 UTC: p95 646ms2026-10-11 UTC: p95 585ms2026-10-12 UTC: p95 549ms2026-10-13 UTC: p95 715ms2026-10-14 UTC: p95 643ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 968ms2026-10-19 UTC: p95 742ms2026-10-20 UTC: p95 465ms2026-10-21 UTC: p95 542ms2026-10-22 UTC: p95 672ms2026-10-23 UTC: p95 2.2s
Sep 24Oct 8Oct 23

Check your own site while you wait on Descope

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of Descope fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Descope fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Descope's official status.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 958msstatus code: 401checked: Oct 23, 2026, 7:53 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
      Checks passinglatency: 201msstatus code: 401checked: Oct 23, 2026, 7:58 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
      Checks passinglatency: 290msstatus code: 401checked: Oct 23, 2026, 7:23 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
      Checks passinglatency: 160msstatus code: 401checked: Oct 23, 2026, 7:30 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
    Checks passinglatency: 11898msstatus code: 401checked: Oct 23, 2026, 7:42 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 424msstatus code: 401checked: Oct 23, 2026, 7:51 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
      Checks passinglatency: 162msstatus code: 401checked: Oct 23, 2026, 7:41 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 646msstatus code: 401checked: Oct 23, 2026, 7:37 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
      Checks passinglatency: 609msstatus code: 401checked: Oct 23, 2026, 7:27 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
      Checks passinglatency: 368msstatus code: 401checked: Oct 23, 2026, 7:04 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 probe events

No probe events on record yet for Descope.

check 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 check readings and Descope's own claim at the time, side by side.

Full check history for Descope: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![Descope uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Descope down?", https://realuptime.io/outages/descope. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Descope's stated SLA

At or above your target

Our checks of Descope failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.descope.com

RealUptime is not affiliated with Descope; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.