Monitoring —
We fixed the issue with our API. This problem was caused by a bigger backend update
Posted
by Michael
Investigating —
We're currently aware of the issue and are investigating the cause. We will provide further updates as we have them.
Posted
by Michael