Affected
Operational from 7:23 AM to 7:32 AM
The issue was a human mistake. We added more control to this specific internal section to avoid this issue coming back later.
We just resolved the issue!
We are currently investigating this incident.