Historia awarii Snapcall

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

Issue was due to a large amount of connections not planned in one of our voice node degrading the voice quality for ongoing call on this node.

This incident has been resolved.

We're experiencing an elevated level of API latency and are currently looking into the issue.

We are investigating the issue. We are noticing anomalously high latency network with our database cluster. Traffic is routed to backup cluster.

API Latency time have been restored to its usual level, and most users are back in. Service looks to be stable. We are following up with AWS for a postmortem of the underlying issue, and are monitoring.

Service looks stable and everyone is back online and calling.