← Back to the carnage
DISCORD
⚪ Discord's request handler took an unscheduled nap, turned out to be a classic case of 'have you tried turning it off and on again' - which, miraculously, actually worked this time. (Auto-resolved: no updates in 24h)
// The official story
Investigating slow and failing requests
// Status page says
Dec 19 , 15:23 PST Resolved - This incident has been resolved. Dec 19 , 15:14 PST Monitoring - We've identified the issue and implemented a fix. Latency should be going down and we should see full recovery soon. Dec 19 , 14:55 PST Investigating - We are currently investigating this issue.
🔗 Official status page (for the PR-approved version)
https://discordstatus.com/incidents/xt705bsck7skDiscord's Greatest Hits
🟢 DISCORD
Sep 16, 2026
🟠 Discord's Android payment system ghosted harder than your ex—Google Play decided to go dark, leaving users unable to throw money at their screen. iOS and web users are fine because of course they are. Existing subscriptions are still breathing, barely. (Auto-resolved: no updates in 24h)
🟢 DISCORD
Sep 11, 2026
🟡 Discord's media proxy is cosplaying as a dial-up modem from 2003. Images are downloading at speeds that make loading a single meme feel like a life commitment. Engineers are investigating why their CDN decided to go full tortoise mode. (Auto-resolved: no updates in 24h)
🟢 DISCORD
Aug 31, 2026
🟠 Discord decided certain servers needed to file missing persons reports. Voice calls and activities also ghosted some users. Engineers are now playing archaeological dig to find what they buried. (Auto-resolved: no updates in 24h)
🟢 DISCORD
Aug 31, 2026
🟠 Discord's having a Schrödinger's server moment—your guild exists AND doesn't exist depending on who you ask. Voice comms and activities also ghosted the group chat. Engineers are frantically checking if they accidentally unplugged the wrong cable. (Auto-resolved: no updates in 24h)