We had a couple issues that occurred Thursday June 10 between 7:00 UTC and 14:00 UTC.  Both of these issues took longer to resolve than our standard response time due to a obscure bug in our monitoring systems.   We’ve identified the root cause of the monitoring issue and we’ve taken a number of steps to ensure it cannot happen again. In addition, we’ve added a significant amount of internal and external monitoring to help isolate and identify issues with any of our services. Our utmost apologies for any inconvenience generated as a result of these issues.

The Amsterdam issue was with the navigation proxy at our Amsterdam site intermittently from 10:25 UTC to 13:00 UTC.  We’ve disabled the proxy in that location pending an on-going investigation to identify the root cause of the issue. During that time frame, the proxy was experiencing very bizarre traffic patterns and we’re doing extensive testing to ensure our systems can handle similar traffic patterns in the future.