Archived and Closed
This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Resolved
The minor release was perceived to be low-risk, so after checking in with the appropriate folks, we deployed it at 4:14 p.m. It didn't take long for the API logs to tell us that all was not well, so we immediately rolled our release back. The total downtime was 5 minutes. Since then, we've identified and corrected the issue, and we'll plan on re-releasing it this week.
API outages are a real bummer, and we work hard to avoid them. Luckily, we caught this one almost immediately, but we regret if you were affected during the outage.
There are no replies.