rewindex

CompaniesDiscordIncidents

Discord: Major Service Impact

No impact listedStatus: resolvedStarted Resolved (2.0 h)1 updatediscordstatus.com (opens in new tab)

Timeline of updates

  1. resolved

    Discord is stable and we do not believe there will be a recurrence of today's issue at this time. We are still working on root causing what happened but are pushing out some mitigations to address some of the problems we saw in the incident.

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 2018-04-12 22:08 UTC, resolved after 2.0 h, 1 update(s).

Title
Major Service Impact
Vendor
Discord
Date
URL
https://rewindex.com/company/discord/incidents/xz52r2qb2y4v

Discord profileRecent Discord incidentsAll outages on April 12, 2018Discord in April 2018MarkdownJSON