All Systems Operational
API   Operational
90 days ago
99.96 % uptime
Today
Gateway   Operational
90 days ago
100.0 % uptime
Today
CloudFlare   ? Operational
Media Proxy   ? Operational
90 days ago
100.0 % uptime
Today
Voice Operational
EU West   Operational
EU Central   Operational
Singapore   Operational
Sydney   Operational
US Central   Operational
US East   Operational
US South   Operational
US West   Operational
Brazil   Operational
Hong Kong   Operational
Russia   Operational
Japan   Operational
South Africa   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
API Response Time
Fetching
Past Incidents
Jan 19, 2019

No incidents reported today.

Jan 18, 2019

No incidents reported.

Jan 17, 2019

No incidents reported.

Jan 16, 2019

No incidents reported.

Jan 15, 2019

No incidents reported.

Jan 14, 2019

No incidents reported.

Jan 13, 2019

No incidents reported.

Jan 12, 2019
Resolved - We still have one database machine that is offline intentionally at this point. We are waiting until we're off of peak traffic before turning it back online. We have also disabled some internal functionality that is not user impacting in order to shed load from the databases.

We're going to mark this incident as resolved as the user impact is complete and, pending another incident, we do not expect it to recur.
Jan 12, 13:08 PST
Identified - We are continuing to see impact to one of our MongoDB machines which is causing the recovery to be slow and is what kicked off this problem. Google has confirmed this is a problem with their storage layer and they are escalating internally to try to achieve resolution.

Separately, we have identified some slowness being caused by a recent change we made to migrate data out of MongoDB and into Postgres. We have overloaded the Postgres setup and it is responding slowly. We are expanding that datababase now to provide more breathing room.
Jan 12, 12:03 PST
Monitoring - The service should be nearly recovered. We are still monitoring some additional latency causing message sends to be a little slower than usual, but this should clear up as the database caches warm up.

We will be investigating the root cause as well as working to understand why recovery took so long. We'll post another update when the incident is resolved, or if we have further information.
Jan 12, 11:53 PST
Update - We have resolved the issue and are letting people back in slowly.
Jan 12, 11:15 PST
Identified - We are aware of the issue and trying to resolve it.
Jan 12, 10:56 PST
Investigating - We are looking into why users cannot connect to Discord. Connected users should be fine.
Jan 12, 10:49 PST
Jan 11, 2019

No incidents reported.

Jan 10, 2019

No incidents reported.

Jan 9, 2019
Resolved - Service has been restored and is stable.
Jan 9, 12:48 PST
Monitoring - Connection and API issues are resolved. We are monitoring and will update soon.
Jan 9, 12:31 PST
Investigating - We are currently investigating this issue.
Jan 9, 12:01 PST
Jan 8, 2019

No incidents reported.

Jan 7, 2019

No incidents reported.

Jan 6, 2019

No incidents reported.

Jan 5, 2019

No incidents reported.