11th May 2016

API Watching

The issue should have been resolved for all affected services as of 13:32 US/Pacific. We're continuing to monitor the situation. We will provide another status update by 14:00 US/Pacific.