Buildkite Status

Resolved: This incident has been resolved.

Monitoring: The integration between Pipelines and Test Engine has been re-enabled, restoring the Tests tab on build pages. We’re monitoring the recovery to confirm the integration remains stable. Test results continue to be available directly through Test Engine.

Monitoring: The integration between Pipelines and Test Engine remains temporarily disabled,  and we're actively working to bring this back online. This affects the Tests tab on build pages. We’ll provide another update as recovery progresses. Test results are available directly through Test Engine

Monitoring: We have identified and fixed the issue. We are monitoring and seeing signs of improvement. We've temporarily disabled the integration between Pipelines and Test Engine. This affects the Tests tab on build pages. We’ll provide another update as recovery progresses. Test results are available directly through Test Engine

Identified: We've identified the cause of the issue and are actively mitigating.

Investigating: Our Web UI is slow at the moment, we are investigating the issue.

Investigating: We've spotted that something has gone wrong and there's elevated latency. We're currently investigating the issue, and will provide an update soon.

Resolved: For the last week we have been internally testing our agent traffic running on our new EKS infrastructure successfully. At 23:01 11 August 2026 UTC we started routing <1% of agent traffic for a small subset of our customer to this EKS infrastructure. Within that subset of customers, any that were using an agent version < 3.97.0 saw an error "failed to decode JSON response: invalid character '<' looking for beginning of value". These older agents crashed once they received that error, which for some customers triggered repeated agent cycling. We reverted the routing to EKS infrastructure at 03:25 UTC after being alerted to the issue.

Monitoring: We have reverted the change which introduced the elevated error rate. We believe the issue to be resolved but will continue to monitor.

Identified: For a subset of customers, <1% of their Agent API traffic is experiencing issues. We are rolling back the change that caused this issue while we investigate it further.

Identified: We're seeing increased latency and error rates for a subset of our customers. We're currently addressing the cause and will provide status updates as they become available.

Investigating: We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Resolved: This incident has been resolved.

Monitoring: The integration between Pipelines and Test Engine has been re-enabled, restoring the Tests tab on build pages. We’re monitoring the recovery to confirm the integration remains stable. Test results continue to be available directly through Test Engine.

Monitoring: The integration between Pipelines and Test Engine remains temporarily disabled,  and we're actively working to bring this back online. This affects the Tests tab on build pages. We’ll provide another update as recovery progresses. Test results are available directly through Test Engine

Monitoring: We have identified and fixed the issue. We are monitoring and seeing signs of improvement. We've temporarily disabled the integration between Pipelines and Test Engine. This affects the Tests tab on build pages. We’ll provide another update as recovery progresses. Test results are available directly through Test Engine

Identified: We've identified the cause of the issue and are actively mitigating.

Investigating: Our Web UI is slow at the moment, we are investigating the issue.

Investigating: We've spotted that something has gone wrong and there's elevated latency. We're currently investigating the issue, and will provide an update soon.