Discord: Increased API Latency & Failed Message Sends
Timeline of updates
- resolved
The secondary that previously failed has successfully snuggled up near a warm fire with a cozy blanket and some hot cocoa and is now adequately warm to serve traffic at nominal latency.
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: minor) posted by Discord, started 2018-10-04 18:28 UTC, resolved after 7 min, 1 update(s).
- Title
- Increased API Latency & Failed Message Sends
- Vendor
- Discord
- Date
- URL
- https://rewindex.com/company/discord/incidents/nsc2bnb6tpj9
Discord profileRecent Discord incidentsAll outages on October 4, 2018Discord in October 2018MarkdownJSON