Looking for an update now? Check the current status, or follow Discord for future changes.
89.8%of 49 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
93.3%
30
2
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A fix has been implemented and we are monitoring results.
Please close and refresh your app to get the fix for adult status.
identified
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.
investigating
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 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
We have recovered. We are still investigating the root cause and will post an update once we have more information
investigating
We are still investigating the issue, some servers are continuing to have a degraded experience
investigating
We are continuing to investigate this issue
investigating
We're investigating an issue where some servers are offline.
Legacy Incident Archive
24 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
March 2026
Issues connecting to Discord
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
We believe we have identified the issue and are taking action to try and restore voice traffic
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.
investigating
We're aware of an issue that is preventing people from connecting to Discord - we're actively investigating
Elevated errors for streaming and messaging
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the source of the issues and are monitoring recovery.
investigating
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.
Failure to start new voice calls
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
New voice calls are failing to be created. We are currently investigating.
Applications experiencing 503 errors
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are aware that bot traffic may be hitting 503 errors and are investigating the issue.
