There were 20 Discord outages since February 27, 2026 totaling 231h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating the issue
We've resolved the issue and messaging should be functional
Users are experiencing delays connecting to the platform. We are investigating
We are investigating issues with large guilds being unavailable
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating an issue where some users may be unable to update their user profile.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating issues interacting with invites.
The issue has been identified and changes are being rolled back.
The rollback is progressing and we are monitoring recovery.
The issue has been resolved.
We are currently investigating an issue with embeds.
The issue has been identified and a fix is being deployed.
A fix has been deployed and we're monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're aware of an issue that is preventing people from connecting to Discord - we're actively investigating
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 believe we have identified the issue and are taking action to try and restore voice traffic
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.
This incident has been resolved.
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.
We have identified the source of the issues and are monitoring recovery.
This incident has been resolved.
New voice calls are failing to be created. We are currently investigating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We believe that the 503s have been resolved.
They should be back shortly
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Users may experience issues sending and receiving messages.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
k-ID age verification is operating normally again in the UK and Australia. Previously age verified users were not impacted.
We're investigating an issue where some guilds are unavailable.
The issue has been identified and a fix is being implemented.
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.
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 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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
you may need to refresh your client to see new DM messages. We are working on identifying the extent of the issue
Some users were unable to start sessions, but should be able to now. Some servers were also not available
This incident has been resolved.
We are currently investigating this issue.
We are investigating an issue where some servers may show up as unavailable and some voice calls may not be able to start.
This incident has been resolved.
Pingoru polls Discord's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required