Whether Discord is up right now, what's wrong if it isn't, and how the last few months went. It reads discordstatus.com and checks again every minute while this page is open.
Nothing ongoing right now. All quiet.
Nothing ongoing right now. All quiet.
No maintenance on the calendar.
No maintenance on the calendar.
| Nov 8 16:40 UTC | 163 ms |
|---|---|
| Nov 8 17:00 UTC | 192 ms |
| Nov 8 17:20 UTC | 155 ms |
| Nov 8 17:40 UTC | 157 ms |
| Nov 8 18:00 UTC | 171 ms |
| Nov 8 18:20 UTC | 155 ms |
| Nov 8 18:40 UTC | 158 ms |
| Nov 8 19:00 UTC | 175 ms |
| Nov 8 19:20 UTC | 149 ms |
| Nov 8 19:40 UTC | 152 ms |
| Nov 8 20:00 UTC | 167 ms |
| Nov 8 20:20 UTC | 144 ms |
| Nov 8 20:40 UTC | 146 ms |
| Nov 8 21:00 UTC | 163 ms |
| Nov 8 21:20 UTC | 143 ms |
| Nov 8 21:40 UTC | 145 ms |
| Nov 8 22:00 UTC | 168 ms |
| Nov 8 22:20 UTC | 141 ms |
| Nov 8 22:40 UTC | 139 ms |
| Nov 8 23:00 UTC | 161 ms |
| Nov 8 23:20 UTC | 138 ms |
| Nov 8 23:40 UTC | 137 ms |
| Nov 9 00:00 UTC | 151 ms |
| Nov 9 00:20 UTC | 140 ms |
| Nov 9 00:40 UTC | 137 ms |
| Nov 9 01:00 UTC | 147 ms |
| Nov 9 01:20 UTC | 141 ms |
| Nov 9 01:40 UTC | 138 ms |
| Nov 9 02:00 UTC | 148 ms |
| Nov 9 02:20 UTC | 135 ms |
| Nov 9 02:40 UTC | 132 ms |
| Nov 9 03:00 UTC | 154 ms |
| Nov 9 03:20 UTC | 128 ms |
| Nov 9 03:40 UTC | 128 ms |
| Nov 9 04:00 UTC | 141 ms |
| Nov 9 04:20 UTC | 128 ms |
| Nov 9 04:40 UTC | 131 ms |
| Nov 9 05:00 UTC | 155 ms |
| Nov 9 05:20 UTC | 128 ms |
| Nov 9 05:40 UTC | 127 ms |
| Nov 9 06:00 UTC | 157 ms |
| Nov 9 06:20 UTC | 127 ms |
| Nov 9 06:40 UTC | 127 ms |
| Nov 9 07:00 UTC | 151 ms |
| Nov 9 07:20 UTC | 125 ms |
| Nov 9 07:40 UTC | 128 ms |
| Nov 9 08:00 UTC | 163 ms |
| Nov 9 08:20 UTC | 140 ms |
| Nov 9 08:40 UTC | 140 ms |
| Nov 9 09:00 UTC | 167 ms |
| Nov 9 09:20 UTC | 145 ms |
| Nov 9 09:40 UTC | 141 ms |
| Nov 9 10:00 UTC | 171 ms |
| Nov 9 10:20 UTC | 148 ms |
| Nov 9 10:40 UTC | 150 ms |
| Nov 9 11:00 UTC | 195 ms |
| Nov 9 11:20 UTC | 142 ms |
| Nov 9 11:40 UTC | 146 ms |
| Nov 9 12:00 UTC | 176 ms |
| Nov 9 12:20 UTC | 154 ms |
| Nov 9 12:40 UTC | 148 ms |
| Nov 9 13:00 UTC | 168 ms |
| Nov 9 13:20 UTC | 133 ms |
| Nov 9 13:40 UTC | 142 ms |
| Nov 9 14:00 UTC | 170 ms |
| Nov 9 14:20 UTC | 152 ms |
| Nov 9 14:40 UTC | 156 ms |
| Nov 9 15:00 UTC | 182 ms |
| Nov 9 15:20 UTC | 158 ms |
| Nov 9 15:40 UTC | 156 ms |
| Nov 9 16:00 UTC | 173 ms |
| Nov 9 16:20 UTC | 159 ms |
| Nov 2 18:00 UTC | 166 ms |
|---|---|
| Nov 2 20:00 UTC | 162 ms |
| Nov 2 22:00 UTC | 148 ms |
| Nov 3 00:00 UTC | 144 ms |
| Nov 3 02:00 UTC | 137 ms |
| Nov 3 04:00 UTC | 130 ms |
| Nov 3 06:00 UTC | 125 ms |
| Nov 3 08:00 UTC | 140 ms |
| Nov 3 10:00 UTC | 145 ms |
| Nov 3 12:00 UTC | 149 ms |
| Nov 3 14:00 UTC | 158 ms |
| Nov 3 16:00 UTC | 174 ms |
| Nov 3 18:00 UTC | 167 ms |
| Nov 3 20:00 UTC | 163 ms |
| Nov 3 22:00 UTC | 164 ms |
| Nov 4 00:00 UTC | 150 ms |
| Nov 4 02:00 UTC | 143 ms |
| Nov 4 04:00 UTC | 135 ms |
| Nov 4 06:00 UTC | 132 ms |
| Nov 4 08:00 UTC | 150 ms |
| Nov 4 10:00 UTC | 153 ms |
| Nov 4 12:00 UTC | 155 ms |
| Nov 4 14:00 UTC | 154 ms |
| Nov 4 16:00 UTC | 161 ms |
| Nov 4 18:00 UTC | 155 ms |
| Nov 4 20:00 UTC | 163 ms |
| Nov 4 22:00 UTC | 150 ms |
| Nov 5 00:00 UTC | 138 ms |
| Nov 5 02:00 UTC | 135 ms |
| Nov 5 04:00 UTC | 132 ms |
| Nov 5 06:00 UTC | 130 ms |
| Nov 5 08:00 UTC | 145 ms |
| Nov 5 10:00 UTC | 147 ms |
| Nov 5 12:00 UTC | 146 ms |
| Nov 5 14:00 UTC | 152 ms |
| Nov 5 16:00 UTC | 158 ms |
| Nov 5 18:00 UTC | 164 ms |
| Nov 5 20:00 UTC | 155 ms |
| Nov 5 22:00 UTC | 144 ms |
| Nov 6 00:00 UTC | 138 ms |
| Nov 6 02:00 UTC | 138 ms |
| Nov 6 04:00 UTC | 126 ms |
| Nov 6 06:00 UTC | 124 ms |
| Nov 6 08:00 UTC | 140 ms |
| Nov 6 10:00 UTC | 143 ms |
| Nov 6 12:00 UTC | 145 ms |
| Nov 6 14:00 UTC | 148 ms |
| Nov 6 16:00 UTC | 150 ms |
| Nov 6 18:00 UTC | 161 ms |
| Nov 6 20:00 UTC | 180 ms |
| Nov 6 22:00 UTC | 233 ms |
| Nov 7 00:00 UTC | 151 ms |
| Nov 7 02:00 UTC | 142 ms |
| Nov 7 04:00 UTC | 137 ms |
| Nov 7 06:00 UTC | 130 ms |
| Nov 7 08:00 UTC | 146 ms |
| Nov 7 10:00 UTC | 149 ms |
| Nov 7 12:00 UTC | 151 ms |
| Nov 7 14:00 UTC | 155 ms |
| Nov 7 16:00 UTC | 159 ms |
| Nov 7 18:00 UTC | 153 ms |
| Nov 7 20:00 UTC | 148 ms |
| Nov 7 22:00 UTC | 142 ms |
| Nov 8 00:00 UTC | 139 ms |
| Nov 8 02:00 UTC | 135 ms |
| Nov 8 04:00 UTC | 130 ms |
| Nov 8 06:00 UTC | 127 ms |
| Nov 8 08:00 UTC | 145 ms |
| Nov 8 10:00 UTC | 147 ms |
| Nov 8 12:00 UTC | 148 ms |
| Nov 8 14:00 UTC | 151 ms |
| Nov 8 16:00 UTC | 160 ms |
| Nov 8 18:00 UTC | 154 ms |
| Nov 8 20:00 UTC | 145 ms |
| Nov 8 22:00 UTC | 139 ms |
| Nov 9 00:00 UTC | 135 ms |
| Nov 9 02:00 UTC | 133 ms |
| Nov 9 04:00 UTC | 129 ms |
| Nov 9 06:00 UTC | 128 ms |
| Nov 9 08:00 UTC | 143 ms |
| Nov 9 10:00 UTC | 145 ms |
| Nov 9 12:00 UTC | 143 ms |
| Nov 9 14:00 UTC | 153 ms |
| Nov 9 16:00 UTC | 157 ms |
No spikes since tracking began on Nov 9, 2026. Nice and steady.
00 █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ 06 █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ 12 █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ 18 █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████
| Oct 12 | 165 ms |
|---|---|
| Oct 13 | 164 ms |
| Oct 14 | 167 ms |
| Oct 15 | 162 ms |
| Oct 16 | 171 ms |
| Oct 17 | 169 ms |
| Oct 18 | 171 ms |
| Oct 19 | 165 ms |
| Oct 20 | 194 ms |
| Oct 21 | 175 ms |
| Oct 22 | 171 ms |
| Oct 23 | 172 ms |
| Oct 24 | 296 ms |
| Oct 25 | 172 ms |
| Oct 26 | 163 ms |
| Oct 27 | 178 ms |
| Oct 28 | 165 ms |
| Oct 29 | 196 ms |
| Oct 30 | 172 ms |
| Oct 31 | 173 ms |
| Nov 1 | 168 ms |
| Nov 2 | 168 ms |
| Nov 3 | 180 ms |
| Nov 4 | 166 ms |
| Nov 5 | 179 ms |
| Nov 6 | 310 ms |
| Nov 7 | 164 ms |
| Nov 8 | 163 ms |
| Nov 9 | 157 ms |
This is Discord's own published metric, the "API Response Time" graph on discordstatus.com: an average over all API requests as Discord's monitoring reports it, not a measurement from this site. The last 24 hours come in 5-minute points; hours before Nov 8, 2026 were filled from Discord's 30-minute and 2-hour views.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved. https://x.com/discord/status/2102964092189475028?s=20
A fix has been implemented and we are monitoring results. Please close and refresh your app to get the fix for adult status.
We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but "adult" on web/desktop. We’re aware of the issue and actively working on a fix.
We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but "adult" on web/desktop. We’re aware of the issue and actively working on a fix.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
This incident has been resolved.
We're currently experiencing an issue that prevents users from completing purchases (including Nitro subscriptions and Shop items) through the Android app. This is caused by an ongoing outage with Google Play. Purchases on other platforms (iOS, web, and desktop) are unaffected, and existing subscriptions remain active. We're monitoring Google's status and will post an update as soon as service is restored. No action is needed on your part — please try again later. https://pay.google.com/status/incidents/gQJsjf662F7KwPyiNqav
This incident has been resolved.
A fix has been implemented and we are currently monitoring recovery of services.
The issue has been identified and we are working to restore service.
We are currently investigating this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating an issue involving high error-rates for image downloads.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We've identified an issue causing some servers to appear unavailable in the client
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Some servers may appear unavailable in the client. We are investigating
This incident has been resolved.
We've identified an issue with our endpoint selection service and are applying a mitigation now. We are seeing recovery to endpoint selection now.
We are investigating problems with voice endpoint selection. Your calls may fail to start or may fail to get an endpoint.
This incident has been resolved.
We have recovered. We are still investigating the root cause and will post an update once we have more information
We are still investigating the issue, some servers are continuing to have a degraded experience
We are continuing to investigate this issue
We're investigating an issue where some servers are offline.
This incident has been resolved.
We are taking steps to remediate the issue
We are taking steps to remediate the issue
some servers will appear unavailable for some users, and some other services may also be impacted (voice calls, activities)
Some users may not be able to connect to some of their servers
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
This issue has been fully resolved
We've recovered service and are continuing to monitor for recovery.
This issue has expanded and is now affecting all Discord interactions. We're continuing to work towards mitigating the issue.
We're aware of an issue preventing users and bots from sending messages, we're working on fully restoring service
This incident has been resolved.
We're seeing significant positive impact from our earlier fix; nearly all users should be recovered at this point. We are monitoring closely.
We have a fix in place are seeing recovery, although some users may still be seeing impact.
We are actively working toward system recovery and will post another update in 10 minutes.
We are continuing to work on a fix for this issue.
We are currently investigating an issue that is impacting users' ability to send direct messages. Other functionality including interactions, shop, and SDK integrations are also affected.
This incident has been resolved.
You may have issues logging in or not receiving DM messages live
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
This incident has been resolved.
We've identified an upstream latency issue, and we're working to mitigate its impacts.
We are currently investigating this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating the issue.
This incident has been resolved
We are ramping up traffic for activities
We have currently disabled activities and are working towards a resolution
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are letting in more connections as capacity allows
We are currently investigating this issue.
We have applied a fix and are seeing recovery across our systems
We're aware of an issue that is affecting a subset of users trying to interact with our services. We are working on a fix to address the issues.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We're investigating an availability where some users may be unable to start a session or some guilds may be unable to connect.
All critical functionalities have recovered for all users.
Users are able to connect to the platform, and we are working on recovering some features
We are continuing to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state
We are beginning to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state
We are seeing significant recovery at this time. We are continue to restore ancillary services and we are metering in traffic as users reconnect.
We are continuing to work to remediate the issues impacting availability for some Discord users. This is causing impact across our service, including logging in and sending messages.
We have identified the issue. Many users are unable to start their sessions at this time
We're investgating errors in our API systems.
We've resolved the issue and messaging should be functional
We are currently investigating the issue
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are investigating issues with large guilds being unavailable
Users are experiencing delays connecting to the platform. We are investigating
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We're investigating an issue where some users may be unable to update their user profile.
The issue has been resolved.
The rollback is progressing and we are monitoring recovery.
The issue has been identified and changes are being rolled back.
We are currently investigating issues interacting with invites.
This incident has been resolved.
A fix has been deployed and we're monitoring the results.
The issue has been identified and a fix is being deployed.
We are currently investigating an issue with embeds.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
This incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
This incident has been resolved.
Voice and video should have recovered and users should be able to connect to voice calls. We are still tracking down issues with our API.
We believe we have identified the issue and are taking action to try and restore voice traffic
We're continuing to investigate impacts to voice connectivity. There may be some temporary impacts to other features as we work to accelerate recovery.
We're aware of an issue that is preventing people from connecting to Discord - we're actively investigating
This incident has been resolved.
We have identified the source of the issues and are monitoring recovery.
We are investigating degraded performance affecting some Discord features, including streaming and messaging, due to a networking issue beginning at approximately 7:53 AM PT; our team is actively engaged with our cloud provider to resolve the issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
New voice calls are failing to be created. We are currently investigating.
We believe the 503s have been resolved.
We are aware that bot traffic may be hitting 503 errors and are investigating the issue.
We believe that the 503s have been resolved.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
They should be back shortly
This incident has been resolved.
Updated clients which support the DAVE (Audio & Video End-to-End Encryption) Protocol are now required to connect to non-stages voice calls across the Discord Platform. If you attempt to connect with an out of date client, the voice gateway will reject your connection with close code 4017. See https://support.discord.com/hc/en-us/articles/38025123604631-Minimum-Client-Version-Requirements-for-Voice-Chat for minimum client version requirements and https://support.discord.com/hc/en-us/articles/25968222946071-End-to-End-Encryption-for-Audio-and-Video for further details. ChromeOS devices should now be able to connect voice channels after refreshing the Discord application.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Users may experience issues sending and receiving messages.
k-ID age verification is operating normally again in the UK and Australia. Previously age verified users were not impacted.
k-ID has deployed a fix for UK/AU age verification issues. We’re monitoring to ensure age verification is working normally. Previously age verified users should not be impacted.
Some users in the UK and Australia may be unable to complete new age verification via k-ID. Users who have already completed age verification should not be impacted. We’re actively working with k-ID on a resolution and will share updates here as we learn more.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We're investigating an issue where some guilds are unavailable.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This is actually a continuation of the incident from earlier today, which we marked "resolved" in error. We have now identified and are remediating the issue
We are currently investigating this issue. Restarting your sessions *should* fix it but existing sessions may have not be seeing new DMs
We are currently investigating this issue. Restarting your sessions *should* fix it but existing sessions may have not be seeing new DMs
This incident has been resolved.
Some users were unable to start sessions, but should be able to now. Some servers were also not available
you may need to refresh your client to see new DM messages. We are working on identifying the extent of the issue
We are currently investigating this issue.
This incident has been resolved.
We are investigating an issue where some servers may show up as unavailable and some voice calls may not be able to start.