Previous incidents

The errors were caused by an issue with an infrastructure upgrade. The upgrade has finished, and everything should be back to normal.

The issue has been resolved, and page load times should be back to normal.

The root cause was a denial-of-service attack on one of our customers, taking advantage of inadequate rate limiting on a particular endpoint. We've fixed the rate limiting to prevent this from happening again, and we apologize for the inconvenience.

We've identified the likely root cause of the issue. A performance issue related to calculating certain statistics coincided with a large data migration, causing unusual load on the database. We've paused the data migration and are working on a plan to mitigate the performance issue so this does not happen again.

We've traced the root cause of the issue to a brief network glitch in AWS. We don't expect it to happen again.

Updates on the IP-based geolocation service are completed, service is fully operational again.