Affected
This incident has been resolved.
We had to perform an unplanned maintenance (involving a restart) on some LB components.
Some services may have experience 502 errors during the maintenance.
We implemented a fix and are currently monitoring the result.
The root cause has been identified.
We are continuing to work on a fix for this incident.
We noticed a delay when provisioning or re deploying services. We are currently investigating this incident.