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 Seattle issue was a single resolver in Seattle  experiencing degraded DNS resolution. This issue would have affected users being routed to the specific machine at our Seattle location. The issue was fully resolved by 14:00 UTC.