rewindex

CompaniesDiscordIncidents

Discord: Issues Sending Messages and Starting New Sessions

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

Timeline of updates

  1. resolved

    We've received clarification from Google that the issue is a scheduled job from some other customer that is causing disruption. The next scheduled run is not for a few more hours, so this won't recur for now. Separately, Discord engineering is powering through a migration of part of our infrastructure to a different class of machines that will not share any resources with the other customer, and this will give us more certainty that Discord should be safe from further impact. We are working to get this migration done by the next scheduled job time, and anticipate that we should be able to do so. Therefore, since we do not anticipate further impact, we are going to close this statuspage. If anything does happen, we will of course open a new incident and let you know.

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 2020-08-08 20:00 UTC, resolved after 3.4 h, 1 update(s).

Title
Issues Sending Messages and Starting New Sessions
Vendor
Discord
Date
URL
https://rewindex.com/company/discord/incidents/bnv0wbddzz2x

Discord profileRecent Discord incidentsAll outages on August 8, 2020Discord in August 2020MarkdownJSON