The outage was caused by our internal reverse proxy failing to scale cleanly, resulting in incoming traffic not routing though our infrastructure correctly. A manual redeployment rectified the issue and service was restored. We have identified the cause for the failed scale and are putting changes in place to prevent re-occurrence.
Resolved · UTC
This incident has been resolved.
Identified · UTC
We are continuing to work on a fix for this incident.