Companies/Discord/Incidents

Discord: Connection & Sending Messages Impacted

Timeline of updates

1. resolved2019-01-03 01:26 UTC

   We're marking this incident as resolved because the current issue is past and we've performed remediation on the involved cluster. However, the underlying root cause is still being investigated. We can say that this is the same thing that has happened a couple of times now -- we're seeing runaway memory utilization on a few sessions servers which leads to them running out of memory. This causes a handful to crash, which forces users to reconnect on the remaining servers -- sometimes forcing them into an out of memory case as well. In the worst instances of this behavior, this cascades to the entire cluster. We currently have a lot of data and a couple hypotheses, but we're still working to fully understand the root cause. Once we do we'll write up a postmortem. Given the number of times this has happened in the past month, we are treating this as an important issue and putting a lot of the team on understanding what has happened and how to properly resolve it for the long-term.

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 incidentsAll outages on January 2, 2019Discord in January 2019MarkdownJSON