All Systems Operational
Enterprise Operational
90 days ago
100.0 % uptime
Today
Enterprise Video   Operational
90 days ago
100.0 % uptime
Today
Enterprise API   Operational
90 days ago
100.0 % uptime
Today
Enterprise Broadcast   Operational
90 days ago
100.0 % uptime
Today
Enterprise SIP   Operational
90 days ago
100.0 % uptime
Today
Enterprise Session Monitoring   Operational
90 days ago
100.0 % uptime
Today
Enterprise Archiving   Operational
90 days ago
100.0 % uptime
Today
Standard Operational
90 days ago
100.0 % uptime
Today
Standard Video   Operational
90 days ago
100.0 % uptime
Today
Standard API   Operational
90 days ago
100.0 % uptime
Today
Standard Broadcast   Operational
90 days ago
100.0 % uptime
Today
Standard SIP   Operational
90 days ago
100.0 % uptime
Today
Standard Session Monitoring   Operational
90 days ago
100.0 % uptime
Today
Standard Archiving   Operational
90 days ago
100.0 % uptime
Today
Tools   ? Operational
90 days ago
100.0 % uptime
Today
Account Portal   Operational
90 days ago
99.97 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
May 20, 2018

No incidents reported today.

May 19, 2018

No incidents reported.

May 18, 2018

No incidents reported.

May 17, 2018

No incidents reported.

May 16, 2018

No incidents reported.

May 15, 2018

No incidents reported.

May 14, 2018

No incidents reported.

May 13, 2018

No incidents reported.

May 12, 2018

No incidents reported.

May 11, 2018

No incidents reported.

May 10, 2018

No incidents reported.

May 9, 2018
Resolved - All affected components have now been reconfigured.
May 9, 09:49 PDT
Identified - We have identified an issue that prevents some archives from being fully processed. The issue was limited to a Bombay server but also appeared in at least one US server (Standard line only). We believe this was caused by our latest release in which we re-enabled stereo support for archives. To resolve the issue, we're going to rollback that change since very few customers actually use stereo.
May 7, 16:13 PDT
May 8, 2018
Postmortem - Read details
May 9, 13:12 PDT
Resolved - Both the connection errors and audio issues have now been resolved.
May 8, 16:47 PDT
Identified - One of our enterprise TURN servers was incorrectly marked as a media server. This caused clients to make requests to it that repeatedly failed. The problem may manifest as websocket failures or audio missing from a call.

We initially received reports around 12:15PM PST and the the server was taken out of rotation at 12:33PM PST. There are some stale sessions that may still be making requests.
May 8, 14:14 PDT
May 6, 2018

No incidents reported.