Resolved -
This incident has been resolved.
Jan 22, 02:23 UTC
Monitoring -
API error rates and latencies have returned to normal levels. The root cause was a hardware failure in our primary DB, resolved by failing over to a hot standby.
We are continuing to monitor the API and database.
Jan 22, 01:47 UTC
Update -
We are continuing to investigate this issue. We are seeing an improvement in error rates and latencies, but both remain elevated.
Jan 22, 01:33 UTC
Investigating -
We are currently investigating elevated latencies and error rates for our primary API.
Jan 22, 01:03 UTC