All Systems Operational
API   Operational
90 days ago
99.99 % 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
Oct 18, 2018

No incidents reported today.

Oct 17, 2018

No incidents reported.

Oct 16, 2018

No incidents reported.

Oct 15, 2018

No incidents reported.

Oct 14, 2018

No incidents reported.

Oct 13, 2018

No incidents reported.

Oct 12, 2018

No incidents reported.

Oct 11, 2018

No incidents reported.

Oct 10, 2018
Resolved - This incident has been resolved.
Oct 10, 17:29 PDT
Identified - The issue has been identified and we are working on fixing it.
Oct 10, 17:07 PDT
Oct 9, 2018
Resolved - This incident has been resolved.
Oct 9, 15:26 PDT
Identified - The issue has been identified and a fix is being implemented.
Oct 9, 15:08 PDT
Investigating - We're aware of an issue affecting sending DMs and viewing online friends. We're online and working on a resolution
Oct 9, 15:08 PDT
Oct 8, 2018

No incidents reported.

Oct 7, 2018

No incidents reported.

Oct 6, 2018

No incidents reported.

Oct 5, 2018

No incidents reported.

Oct 4, 2018
Resolved - The secondary that previously failed has successfully snuggled up near a warm fire with a cozy blanket and some hot cocoa and is now adequately warm to serve traffic at nominal latency.
Oct 4, 11:35 PDT
Monitoring - The secondary appears to be sufficiently warm now, and we are noticing error rates and latency drop to nominal levels.
Oct 4, 11:31 PDT
Investigating - We are aware of issues regarding higher than normal latency, and failed message sends. The team is aware of the root cause of the issue (a host error on one of our database secondaries caused it to reboot).

During this time, the secondary is "cold" as it loads data into memory. We are monitoring the instance as it warms up, and expect latency to fully recover in 5-15 minutes, and latency to continue to as the secondary gradually warms up.
Oct 4, 11:28 PDT