The application is currently not responding. We are investigating the problem and will continue to update this post as we work toward the solution.
The system is back online. It was not responsive for approximately 10 minutes between 8:05 and 8:15 AM USA PDT and began responding again after some server reset routines.
Correction at 8:20 AM PDT: We're seeing inconsistent success to connect. The problem is NOT resolved as of yet.
Update at 8:35 AM PDT: Some connections are reporting as working and others are not. Access remains inconsistent. We will confirm consistent access in this blog post once we know all servers are responding normally.
Update at 8:40 AM PDT: Many customers are reporting the system as up and normal, some as up and slow. We do not have official confirmation that the problem is resolved, but it does appear usable for most at the moment. We expect the "all clear" confirmation shortly.
Update at 9:03 AM PDT: We identified a corrupt table index on one of our database
servers that introduced latency issues. This created timeout issues for
many requests beyond the localized table. We have identified the
offending table and corrected the problem. We will be monitoring closely.