Rewindex

CompaniesDiscordIncidents

Discord: Elevated Errors Across the Platform

MinorStatus: resolvedStarted Resolved (2.6 h)1 updatediscordstatus.com (opens in new tab)
Part of an outage event

Google Cloud outage, Dec 14, 2020 · 10 vendors, 12 incidents

Discord’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +19 min vs the first vendor naming Google Cloud)

Swipe sideways to see the whole diagram.

same windowGoogle Cloudown incident not archivedWithin an hour2 vendors, 1 blamed Google CloudSnowflake, BugsnagDiscord (this incident)posted +19 min
same windowGoogle Cloudown incident not archivedWithin an hour2 vendors, 1 blamed GoogleCloudSnowflake, BugsnagDiscord (this incident)posted +19 min
Discord is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 1 blamed Google Cloud<br/>Snowflake, Bugsnag"]:::blames
  root --> h1
  me["Discord (this incident)<br/>posted +19 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    All systems are operational. This incident was related to an issue with one of our providers. We have restored the impacted resources.

From Discord’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on discordstatus.com (opens in new tab).

Discord profileRecent Discord incidentsMarkdownJSON