Previous incidents

The team has fixed the issue and all service are back to normal.

All services are operating normally

Engineers have implemented a fix in the search system, all systems are back to operational.

The issue has been resolved and systems are back to normal.

System is stable

A 10-second spike in error rates affected Identification API requests. This has been resolved.

The issue has bee resolved, no code worker deployments are working again.

Between 1:42pm and 1:46pm UTC, we observed an elevated error rate and higher-than-normal latency in our US region for our Ingress endpoint. The system is now stable.

We have identified the issue and applied a fix, Engineers are monitoring the systems

Between 7:16pm and 7:19pm UTC, we observed an elevated error rate and higher-than-normal latency in our US region for our Ingress endpoint. The system is now stable.

The system is stable. Our engineers are investigating the root cause.

We observed increased load resulting in higher-than-average latencies. We have confirmed full recovery, and all services are operating normally.

The issue affecting service availability has been resolved. We deployed a fix and have confirmed normal performance across affected systems.

We have identified the issue to be actually a non-issue, and systems are and were stable.

All services are restored to normal operation.

Issue has been resolved and services are back to normal.

Between 14:08–22:36 UTC on 28 July, 2026, a bot-detection rule targeting Chromium automation frameworks generated a high rate of false positives for a subset of browsers, most significantly Samsung Internet. Approximately 1.48% of total JS agent traffic was affected. The rule has been disabled, and detection has returned to normal.

Issue has been resolved and daily summary emails service back to normal.

All services have been returned to normal operation.