Elevated 500/502 errors
Incident Report for CallTrackingMetrics
Resolved
Starting at 11:36 and ending at 12:08 we experienced elevated 502 errors. This was due to a recovery process that was putting too much load on our databases related to the incident on Thursday. Our team is working on expanding our footprint to support increased load spikes like this now. The issue is resolved and we will not repeat this.
Posted Feb 05, 2023 - 12:10 EST