A database upgrade through the night resulted in unexpected downtime on our public API. The issue has been identified and resolved. We deeply apologize for any inconvenience.

Began at: