Discord Outage History

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.

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.

The upstream provider has resolved the issue on their side, and all Discord components are operating normally.

We are continuing to monitor for residual impact as upstream service is restored.

We've identified the expected upstream errors in our monitoring and are awaiting an in-progress fix from upstream provider.

An upstream provider is investigating a major issue, and we are currently investigating the impact to Discord.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're investigating an issue where some webhook messages containing attachments or images are failing to send.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating an issue that is preventing users from leaving servers.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are investigating a small amount of servers reporting outages.

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.

At this point, capacity is back online globally and Discord is operating normally. Thank you for your patience tonight while we worked through the issues.

We are showing nearly full recovery and are monitoring while the long-tail of overloaded servers rebalance.

We continue to work with our partner to restore capacity. Currently, graphs are looking better in some areas, but we are still seeing some hot spots.

We have identified the issue that caused us to have a capacity drop earlier and are working with our partner to resolve the issue. In the interim, we are continuing to bring up backup capacity to address the latency that certain regions are seeing.

We are bringing up additional capacity in North America right now out of caution, but the user experience should be relatively stable for voice and video at this point.

Voice and calls should be working normally. The team is still investigating some residual anomalies in the graphs, but the user experience should be back to normal.

We are aware of some intermittent connection issues/call drops. The team is online and investigating.

This incident has been resolved. We have fixed the issue preventing some Android users from solving captchas in the latest version of the Discord app. If you are still experiencing problems, please updating your Discord app to version 292.16 on your Android device, via the Google Play Store.

We have fixed the issue preventing some Android users from solving captchas in the latest version of the Discord app. If you are still experiencing problems, please updating your Discord app to version 292.16 on your Android device, via the Google Play Store.

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 load the shop.

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.

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.

The issue has been identified and a fix is being implemented.

We are currently investigating issues with payments and subscription processing.

This incident has been resolved.

We're recovering the affected data and monitoring its ingestion into all affected systems.

We've identified a data issue with active threads in servers that opted into an experimental, opt-in feature. We've fixed the underlying issue and are working on data recovery for the affected threads.

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 have stopped the streams which were stuck and completed the rollback. We are now hands off keeping an eye on recovery.

We are deploying a fix for streams which are stuck in a bad state, you may need to manually re-start your stream.

We have identified the issue and are rolling back a deploy.

We've addressed this issue and all affected users have been corrected.

We've identified a root cause for this issue and are working on remediating it.

Our windows updater should be fixed everywhere and we should have fully recovered. Happy gaming.

We are continuing to investigate an issue with our windows updater.

Some Windows users might have issues updating or downloading our windows client. We are investigating.

Subscriptions and shop should have recovered. Most of our features should also be back online and we are seeing recovery progressively.

We're currently seeing impacts to subscriptions and shop as a part our ongoing investigation

We are back to seeing issues across a lot of features. We are continuing to work with our provider to get to recovery.

Attachments and embeds should be mostly back but we are still investigating issues with other features like activities.

We are continuing to work with our provider to resolve this issue.

We are continuing to investigate and work with our providers to resolve this issue. It is likely impacting a few more features like activities.

We are investigating an issue with attachments and embeds not being rendered in the app.

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.

The issue is resolved

The team continues to investigate the mistaken push notifications and we are hoping to have this issue fully resolved later today.

We believe that the notifications are the result of some maintenance we performed on one of our backend systems and we are continuing to work to identify a fix for this issue.

We're aware of an issue causing some users to receive push notifications for previously muted conversations. The team is actively investigating to identify the root cause.