Previous incidents

The system is fully recovered, and the dashboard/API data should correctly represent the system state. We're sorry for the trouble caused, and we will publish a postmortem within a few days.

We identified the root cause of a GCP Bigtable outage in us-east-1, which has been confirmed by the GCP support team. However, the system should be able to absorb a Bigtable outage, and we're looking into why the issue had broader performance consequences.

We've identified the issue, and the services have recovered. We've now caught up on the backlog the issue caused.

CORRECTION: The previous update incorrectly stated that the issue affected all customers; it was, in fact, limited to free and team plan customers and did not impact customers under SLAs (growth & enterprise)