Welcome to our status page. If you are looking for help, please check our documentation guides or contact us on our community forum. All products listed below have a target availability of 99.9%.
Uptime over the past 90 days. View historical uptime.
On April 23, 2026, from 3:00 pm UTC to 11:42 pm UTC, some customers with IP restriction policies enabled experienced agent jobs remaining pending or failing to start. More than 150 jobs were affected across multiple regions.
Customers without IP restrictions and agents using the serverless execution path were not affected.
A messaging infrastructure update introduced a regression that prevented required IP restriction headers from being forwarded between internal services during agent job initiation.
Without these headers, downstream authorization checks rejected requests from organizations using IP restrictions. Serverless agents were unaffected because they use a separate execution path.
The incident was detected through customer reports and monitoring of pending jobs. It was declared at 3:24 pm UTC, and the public status page was updated at 3:26 pm UTC.
The investigation established that:
At 5:26 pm UTC, the team identified the header propagation regression. A fix was validated and progressively deployed across production regions. Customers began confirming recovery by 11:00 pm UTC, and all regions were operational by 11:42 pm UTC.
We are taking the following actions:
We apologize for the disruption and are strengthening our testing, deployment, and monitoring processes to reduce the risk of recurrence.