Affected
Operational from 11:48 PM to 11:49 PM
This incident has been resolved.
We are currently investigating this incident.
We are continuing to work on a fix for this incident.
Identified the error, pushing a fix now