StatOSS

Discord uptime

Discord, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

discord.com/api/v10/gatewayEvery 5 minutes

Discord is up.

Up for 51 d 10 h. Last checked 2026-11-20 18:37 UTC from Singapore: 200 in 24 ms.

Last 24 hours

Up for 51 d 10 h100% passed

288 checks, median 20 ms from Helsinki, all passed

95% under 25 ms

Response time by region
EuropeEurope20 ms
N. AmericaNorth America24 ms
AsiaAsia27 ms
OceaniaOceania26 ms

Medians over this range, on one scale up to 100 ms.

Last 90 days

Up for 51 d 10 h100% passed

14,801 checks, median 21 ms from Helsinki, all passed

95% under 194 ms

Response time by region
EuropeEurope21 ms
N. AmericaNorth America28 ms
AsiaAsia29 ms
OceaniaOceania26 ms

Medians over this range, on one scale up to 100 ms. Europe's places are scaled to Helsinki, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:38 UTC.

In the last 30 days Discord passed 8,859 of 8,859 checks, 100%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days100%2,011 of 2,0110
30 days100%8,859 of 8,8590
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany45 ms56 ms46 ms42
Helsinki, Finland20 ms25 ms20 ms420
Ashburn, USA25 ms51 ms29 ms503
Copenhagen, Denmark25 ms40 ms28 ms43
Singapore26 ms47 ms28 ms506
Sydney, Australia25 ms48 ms28 ms502

Outages

None detected since checks began on 30 Sep 2026.

What is checked

Voice, video and text chat, home to many open source and gaming communities and their bots.

StatOSS sends GET https://discord.com/api/v10/gateway and counts the check as passed on status 200 within 10 seconds. The Gateway endpoint that a bot asks for the WebSocket address before it connects. It needs no token and answers 200.

The Gateway itself, voice servers and message delivery are not checked, only the REST API that hands out the address.

Discord reports its own incidents at discordstatus.com. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 200.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.