Resolved -
This incident has been resolved.
May 29, 17:09 UTC
Monitoring -
A fix has been implemented. Monitoring to ensure error rates are down on all affected deployments
May 29, 16:47 UTC
Investigating -
We are currently investigating.
May 29, 15:23 UTC