Previous incidents

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.

We identified the issue as a certificate that had expired. We were able to replace the certificate, and everything should be fine now.

The root cause of this issue was that the automatic process that was supposed to replace the certificate before it expired did not run. We will be investigating and rectifying that problem so it does not happen again.