Discord: Issues Sending DMs
Timeline of updates
- resolved
Turns out we didn't need to disable typing events (this time), we were able to get the cluster stable by just reducing the number of API servers by about 10%. Presence is back up and running & happy, DMs are flowing like normal. We've got a fix in the works for the underlying root cause (overstressing our service discovery system, which prevented the presence system from restarting with all nodes). We should have this deployed next week, but in the meantime, things should be stable. Thank you very much for your patience as we worked through this, and we are super sorry for the inconvenience!
From Discord’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on discordstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Discord, started 2019-10-05 21:04 UTC, resolved after 53 min, 1 update(s).
- Title
- Issues Sending DMs
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/fyw929cjnn6y
Discord profileRecent Discord incidentsAll outages on October 5, 2019Discord in October 2019MarkdownJSON