We experienced an unusually large spike in traffic that overloaded one of our client's origin servers causing some incoming queries to be dropped with a 502 error. Unfortunately, this capacity issue spilled into the rest of our services as our application workers were busy handling the slow API queries.

We identified a weakness in our rate-limiting algorithm, which allowed the incident to occur. Furthermore, we deployed changes to our rate-limiting algorithm to mitigate any further related incidents.