Discord

Affected: API, Media Proxy

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 19:48 UTC

   We are currently investigating this issue.

2. resolved 2026-10-01 20:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: Android

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-24 02:08 UTC

   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.

2. identified 2026-09-24 02:10 UTC

   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.

3. monitoring 2026-09-24 03:05 UTC

   A fix has been implemented and we are monitoring results. Please close and refresh your app to get the fix for adult status.

4. resolved 2026-09-24 03:32 UTC

   This incident has been resolved. https://x.com/discord/status/2102964092189475028?s=20

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 18:18 UTC

   We are currently investigating this issue.

2. identified 2026-09-17 20:00 UTC

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

3. monitoring 2026-09-17 20:17 UTC

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

4. resolved 2026-09-17 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 21:32 UTC

   We are currently investigating this issue.

2. identified 2026-09-16 21:45 UTC

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

3. monitoring 2026-09-16 22:15 UTC

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

4. resolved 2026-09-16 22:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 19:03 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-16 19:20 UTC

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

3. resolved 2026-09-16 19:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-16 16:15 UTC

   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,...

2. resolved 2026-09-16 16:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-15 14:26 UTC

   We are currently investigating this issue.

2. identified 2026-09-15 14:42 UTC

   The issue has been identified and we are working to restore service.

3. monitoring 2026-09-15 14:58 UTC

   A fix has been implemented and we are currently monitoring recovery of services.

4. resolved 2026-09-15 15:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: Media Proxy

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 16:24 UTC

   We are currently investigating an issue involving high error-rates for image downloads.

2. identified 2026-09-11 16:27 UTC

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

3. monitoring 2026-09-11 17:39 UTC

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

4. resolved 2026-09-11 17:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-11 04:21 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-11 06:20 UTC

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

3. resolved 2026-09-11 06:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-03 21:31 UTC

   We've identified an issue causing some servers to appear unavailable in the client

2. monitoring 2026-09-03 22:06 UTC

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

3. resolved 2026-09-03 22:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-03 14:35 UTC

   Some servers may appear unavailable in the client. We are investigating

2. identified 2026-09-03 14:56 UTC

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

3. monitoring 2026-09-03 15:01 UTC

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

4. resolved 2026-09-03 15:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 23:26 UTC

   We are investigating problems with voice endpoint selection. Your calls may fail to start or may fail to get an endpoint.

2. identified 2026-09-02 23:35 UTC

   We've identified an issue with our endpoint selection service and are applying a mitigation now. We are seeing recovery to endpoint selection now.

3. resolved 2026-09-02 23:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 16:12 UTC

   We're investigating an issue where some servers are offline.

2. investigating 2026-09-02 17:04 UTC

   We are continuing to investigate this issue

3. investigating 2026-09-02 17:51 UTC

   We are still investigating the issue, some servers are continuing to have a degraded experience

4. monitoring 2026-09-02 18:18 UTC

   We have recovered. We are still investigating the root cause and will post an update once we have more information

5. resolved 2026-09-02 18:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-31 22:54 UTC

   Some users may not be able to connect to some of their servers

2. investigating 2026-08-31 23:26 UTC

   some servers will appear unavailable for some users, and some other services may also be impacted (voice calls, activities)

3. investigating 2026-08-31 23:38 UTC

   We are taking steps to remediate the issue

4. identified 2026-08-31 23:56 UTC

   We are taking steps to remediate the issue

5. resolved 2026-09-01 00:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-14 06:09 UTC

   We are currently investigating this issue.

2. monitoring 2026-08-14 06:14 UTC

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

3. resolved 2026-08-14 06:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-07 22:21 UTC

   We're aware of an issue preventing users and bots from sending messages, we're working on fully restoring service

2. identified 2026-08-07 22:26 UTC

   This issue has expanded and is now affecting all Discord interactions. We're continuing to work towards mitigating the issue.

3. monitoring 2026-08-07 22:42 UTC

   We've recovered service and are continuing to monitor for recovery.

4. resolved 2026-08-07 23:02 UTC

   This issue has been fully resolved

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-04 18:49 UTC

   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.

2. identified 2026-08-04 18:50 UTC

   We are continuing to work on a fix for this issue.

3. identified 2026-08-04 19:36 UTC

   We are actively working toward system recovery and will post another update in 10 minutes.

4. monitoring 2026-08-04 19:53 UTC

   We have a fix in place are seeing recovery, although some users may still be seeing impact.

5. monitoring 2026-08-04 19:59 UTC

   We're seeing significant positive impact from our earlier fix; nearly all users should be recovered at this point. We are monitoring closely.

6. resolved 2026-08-04 20:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-27 17:48 UTC

   You may have issues logging in or not receiving DM messages live

2. resolved 2026-07-27 18:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-22 23:32 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-22 23:49 UTC

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

3. resolved 2026-07-22 23:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-17 00:49 UTC

   We are currently investigating this issue.

2. identified 2026-07-17 01:51 UTC

   We've identified an upstream latency issue, and we're working to mitigate its impacts.

3. resolved 2026-07-17 03:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API, Payments

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-10 16:49 UTC

   We are currently investigating this issue.

2. monitoring 2026-07-10 17:11 UTC

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

3. resolved 2026-07-10 19:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-29 18:46 UTC

   We are currently investigating the issue.

2. resolved 2026-06-29 20:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-10 17:15 UTC

   We have currently disabled activities and are working towards a resolution

2. monitoring 2026-06-10 18:21 UTC

   We are ramping up traffic for activities

3. resolved 2026-06-10 18:35 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: Gateway

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-09 21:24 UTC

   We are currently investigating this issue.

2. identified 2026-06-09 21:30 UTC

   We are letting in more connections as capacity allows

3. monitoring 2026-06-09 21:37 UTC

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

4. resolved 2026-06-09 21:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-22 01:55 UTC

   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.

2. resolved 2026-05-22 03:39 UTC

   We have applied a fix and are seeing recovery across our systems

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-09 06:25 UTC

   We're investigating an availability where some users may be unable to start a session or some guilds may be unable to connect.

2. monitoring 2026-05-09 06:54 UTC

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

3. resolved 2026-05-09 07:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-08 19:08 UTC

   We're investgating errors in our API systems.

2. identified 2026-05-08 19:24 UTC

   We have identified the issue. Many users are unable to start their sessions at this time

3. identified 2026-05-08 19:56 UTC

   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.

4. monitoring 2026-05-08 20:16 UTC

   We are seeing significant recovery at this time. We are continue to restore ancillary services and we are metering in traffic as users reconnect.

5. identified 2026-05-08 20:19 UTC

   We are beginning to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state

6. identified 2026-05-08 21:08 UTC

   We are continuing to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state

7. identified 2026-05-08 21:47 UTC

   Users are able to connect to the platform, and we are working on recovering some features

8. resolved 2026-05-08 22:38 UTC

   All critical functionalities have recovered for all users.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-02 17:03 UTC

   We are currently investigating the issue

2. resolved 2026-05-02 17:29 UTC

   We've resolved the issue and messaging should be functional

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: Gateway

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-28 19:20 UTC

   Users are experiencing delays connecting to the platform. We are investigating

2. investigating 2026-04-28 19:29 UTC

   We are investigating issues with large guilds being unavailable

3. monitoring 2026-04-28 21:02 UTC

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

4. resolved 2026-04-28 21:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-19 02:37 UTC

   We're investigating an issue where some users may be unable to update their user profile.

2. monitoring 2026-04-19 03:41 UTC

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

3. resolved 2026-04-19 03:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-16 19:47 UTC

   We are currently investigating issues interacting with invites.

2. identified 2026-04-16 19:49 UTC

   The issue has been identified and changes are being rolled back.

3. monitoring 2026-04-16 20:05 UTC

   The rollback is progressing and we are monitoring recovery.

4. resolved 2026-04-16 20:30 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-07 01:48 UTC

   We are currently investigating an issue with embeds.

2. identified 2026-04-07 02:28 UTC

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

3. monitoring 2026-04-07 02:46 UTC

   A fix has been deployed and we're monitoring the results.

4. resolved 2026-04-07 02:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-31 05:11 UTC

   We are currently investigating this issue.

2. monitoring 2026-03-31 05:30 UTC

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

3. resolved 2026-03-31 05:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-28 21:23 UTC

   We are currently investigating this issue.

2. identified 2026-03-28 21:31 UTC

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

3. monitoring 2026-03-28 21:40 UTC

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

4. monitoring 2026-03-28 21:43 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-03-28 21:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API, Gateway

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-25 19:21 UTC

   We're aware of an issue that is preventing people from connecting to Discord - we're actively investigating

2. investigating 2026-03-25 19:46 UTC

   We're continuing to investigate impacts to voice connectivity. There may be some temporary impacts to other features as we work to accelerate recovery.

3. identified 2026-03-25 20:07 UTC

   We believe we have identified the issue and are taking action to try and restore voice traffic

4. monitoring 2026-03-25 21:26 UTC

   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.

5. resolved 2026-03-25 22:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API, Push Notifications

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-25 15:18 UTC

   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.

2. monitoring 2026-03-25 15:43 UTC

   We have identified the source of the issues and are monitoring recovery.

3. resolved 2026-03-25 15:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-20 02:47 UTC

   New voice calls are failing to be created. We are currently investigating.

2. monitoring 2026-03-20 05:43 UTC

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

3. resolved 2026-03-20 05:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-03-12 21:04 UTC

   We believe that the 503s have been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 20:50 UTC

   We are aware that bot traffic may be hitting 503 errors and are investigating the issue.

2. resolved 2026-03-12 21:06 UTC

   We believe the 503s have been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: Gateway

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-11 23:07 UTC

   They should be back shortly

2. monitoring 2026-03-11 23:11 UTC

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

3. resolved 2026-03-11 23:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-09 17:08 UTC

   Users may experience issues sending and receiving messages.

2. identified 2026-03-09 17:22 UTC

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

3. monitoring 2026-03-09 17:29 UTC

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

4. resolved 2026-03-09 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: Desktop, iOS, Android, Web

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-06 03:26 UTC

   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.

2. monitoring 2026-03-06 03:38 UTC

   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.

3. resolved 2026-03-06 03:49 UTC

   k-ID age verification is operating normally again in the UK and Australia. Previously age verified users were not impacted.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-05 01:37 UTC

   We're investigating an issue where some guilds are unavailable.

2. identified 2026-03-05 01:49 UTC

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

3. resolved 2026-03-05 01:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-03-02 20:02 UTC

   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...

2. resolved 2026-03-11 17:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: Gateway

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-28 21:54 UTC

   We are currently investigating this issue. Restarting your sessions *should* fix it but existing sessions may have not be seeing new DMs

2. identified 2026-02-28 22:28 UTC

   We are currently investigating this issue. Restarting your sessions *should* fix it but existing sessions may have not be seeing new DMs

3. identified 2026-02-28 22:42 UTC

   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

4. monitoring 2026-02-28 22:51 UTC

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

5. resolved 2026-02-28 22:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: Gateway

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-28 14:39 UTC

   you may need to refresh your client to see new DM messages. We are working on identifying the extent of the issue

2. monitoring 2026-02-28 14:53 UTC

   Some users were unable to start sessions, but should be able to now. Some servers were also not available

3. resolved 2026-02-28 16:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-02-28 14:00 UTC

   We are currently investigating this issue.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-27 21:52 UTC

   We are investigating an issue where some servers may show up as unavailable and some voice calls may not be able to start.

2. resolved 2026-02-27 22:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-27 21:23 UTC

   We're investigating an issue that is causing errors joining voice channels or watching streams

2. monitoring 2026-01-27 22:56 UTC

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

3. resolved 2026-01-27 23:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.

Affected: API, Search

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-25 00:35 UTC

   We are currently investigating this issue.

2. resolved 2026-01-25 06:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Discord's status page.