[India] - Degraded Performace in Serverless Job Execution

Update timeline

1. investigating Jul 18, 2026, 07:18 AM UTC

   We are Investigating the cause of the degraded performance impacting Job Execution for Serverless Robots in India. Impact: Users may experience slow job execution. Additional updates will be provided as we move toward resolution.

2. identified Jul 18, 2026, 08:05 AM UTC

   We have identified the issue and our teams has started working on applying the fix.

3. monitoring Jul 18, 2026, 08:57 AM UTC

   A fix has been applied and we are now monitoring the results. Job execution performance for Serverless Robots in India has returned to normal levels. We will continue to monitor the situation

4. resolved Jul 18, 2026, 09:06 AM UTC

   This incident has been resolved. Job execution performance for Serverless Robots in India has returned to normal levels and remained stable through the monitoring period.

5. postmortem Jul 29, 2026, 11:43 AM UTC

   ## Customer impact On July 18, 2026, customers in the India region may have experienced degraded performance, timeouts, or failures when using Agent Evaluations and Health Score. Some published Conversational Agents may also have been unable to initialize conversations. Serverless Robot jobs may have started or executed more slowly than normal. ## Impact timeline All times below are on July 18, 2026, in UTC. | Time | Affected services | Customer impact | | --- | --- | --- | | Approximately 07:00–07:09 | Agent Builder | Customers may have experienced degraded performance, timeouts, or failures in Agent Evaluations and Health Score. Some published Conversational Agents may also have been unable to initialize conversations. | | 07:09–08:30 | Agent Builder and Serverless Robots | The Agent Builder impact continued. Serverless Robot jobs may also have started or executed more slowly than normal. | | 08:30–09:06 | Serverless Robots | Agent Builder service had recovered. Serverless Robot jobs may still have started or executed more slowly than normal until service was fully restored. | ## Root cause An unusually large traffic spike in the India region exceeded the available service capacity for Agent Builder and Serverless Robots. ## Detection The issue was detected through automated service alerts. Our engineering teams began investigating and published customer notifications for the affected Agent Builder and Serverless Robot services. ## Response We restored service by increasing regional capacity, controlling the abnormal workload, and monitoring the affected features until performance stabilized. ## Follow up We are improving capacity safeguards, workload controls, isolation, and the performance of affected request paths to reduce the likelihood and customer impact of similar traffic spikes.