Increased API Errors
May 8, 19:08 UTCMay 8, 22:38 UTC
Duration
3h 30m
Impact
Major
Root cause
Not disclosed
Discord, 90 days
21 incidents
Affected
Not listed by the vendor.
Final update
All critical functionalities have recovered for all users.
Timeline
- Resolved · May 8, 22:38 UTC
All critical functionalities have recovered for all users.
- Identified · May 8, 21:47 UTC
Users are able to connect to the platform, and we are working on recovering some features
- Identified · May 8, 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
- Identified · May 8, 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
- Monitoring · May 8, 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.
- Identified · May 8, 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.
- Identified · May 8, 19:24 UTC
We have identified the issue. Many users are unable to start their sessions at this time
- Investigating · May 8, 19:08 UTC
We're investgating errors in our API systems.
More from Discord
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2402:08 UTC | Age group status mismatch across devices | major | 1h 24m |
| Sep 1718:18 UTC | Issue / Delay in establishing call connection | major | 2h 21m |
| Sep 1621:32 UTC | Issue establishing voice call | major | 1h 2m |
| Sep 1619:03 UTC | API Errors | none | 25m |
| Sep 1616:15 UTC | Google Pay Outage | major | 28m |
| Sep 1514:26 UTC | Session Unavailability | none | 50m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.