10th April 2017

API Watching

The issue should have been resolved for all affected services as of 15:10 US/Pacific. We're continuing to monitor the situation.