UiPath Status

Resolved: The upstream dependency issue has been fully resolved. All Customer Portal services have been restored and are operating normally.

We apologize for any inconvenience caused. Thank you for your patience.

Monitoring: System recovery is in progress and Customer Portal features are now operational  We are currently monitoring system stability and conducting final verification before confirming  full resolution.

Investigating: The upstream provider has identified the root cause of the disruption and is actively deploying a fix across affected instances We are seeing gradual improvement in Customer Portal functionality.

Investigating: We are experiencing degraded service on Customer Portal affecting multiple support-related features.

Affected functionality:

• Customer Support Infrastructure
• Viewing existing support case details and email replies
• Account/Company data loading
• Self-registration case status checks
• File downloads linked to support cases

What's working:

• Authentication and login
• Non-support dependent features (Knowledge Base, Community, etc.)

Root cause: An upstream dependency used by Customer Portal's support Infrastructure is currently experiencing a service disruption.

Next steps: Our team is actively monitoring the situation and working to restore full service as quickly as possible. No action is required from customers at this time.

We will provide updates as the situation evolves.

Resolved: The issue has been resolved. Our monitoring indicates that services are operating normally, and no further impact has been observed.

Identified: We have identified the cause of the outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions and are working on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our focus is on restoring service as quickly as possible.

Investigating: We are investigating reports of an outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions. Impact: Users may be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: The fix has been deployed and service has been restored

Monitoring: A fix has been deployed to address the issue. We are actively monitoring the environment to confirm full service restoration.

Investigating: Our team is making progress in identifying the root cause and is actively working diligently to mitigate the issue. No action is required from customers at this time.

Investigating: We are currently investigating degraded performance affecting IXP in the US region.

Affected functionality:

• Automations utilizing IXP may experience increased latency
• Some requests may return HTTP 503 errors

Next steps: Our team is actively investigating the root cause and working to restore full service. No action is required from customers at this time.

Resolved: The upstream dependency issue has been fully resolved. All Customer Portal services have been restored and are operating normally.

We apologize for any inconvenience caused. Thank you for your patience.

Monitoring: System recovery is in progress and Customer Portal features are now operational  We are currently monitoring system stability and conducting final verification before confirming  full resolution.

Investigating: The upstream provider has identified the root cause of the disruption and is actively deploying a fix across affected instances We are seeing gradual improvement in Customer Portal functionality.

Investigating: We are experiencing degraded service on Customer Portal affecting multiple support-related features.

Affected functionality:

• Customer Support Infrastructure
• Viewing existing support case details and email replies
• Account/Company data loading
• Self-registration case status checks
• File downloads linked to support cases

What's working:

• Authentication and login
• Non-support dependent features (Knowledge Base, Community, etc.)

Root cause: An upstream dependency used by Customer Portal's support Infrastructure is currently experiencing a service disruption.

Next steps: Our team is actively monitoring the situation and working to restore full service as quickly as possible. No action is required from customers at this time.

We will provide updates as the situation evolves.

Postmortem: ## Customer Impact

On March 13, 2026, between 12:31 and 13:09 UTC, customers using Studio Web in the U.S. environment experienced a service outage lasting approximately 38 minutes. Users encountered HTTP 503 errors and were unable to access Studio Web during this period.

The incident occurred at 11:31 am UTC, before the start of U.S. business hours, which limited the number of affected customers. Based on our analysis, a small number of customers experienced failed requests during the outage window.

Root Cause

A planned infrastructure change updated the network configuration of our enterprise U.S. production environment, changing the outbound IP address used by the service. The new IP address was not added to the access rules of a critical storage resource that the service depends on. When service instances restarted, they were unable to connect to this storage resource because the new IP address was blocked by the existing network access rules.

The dependency between the environment's outbound IP and the storage resource's access rules was not tracked in the migration process, and there was no automated validation to verify that all dependent resources had been updated before the migration proceeded.

Detection

The issue was detected automatically by our monitoring systems within minutes of the service becoming unavailable. Our on-call engineering team was engaged immediately after being alerted.

Response

Our engineering team identified the root cause within 22 minutes of engagement by analyzing service logs and correlating them with the ongoing infrastructure migration. The issue was resolved at 13:06 UTC by updating the storage resource's network access rules to allow the new IP address. Full service restoration was confirmed at 13:09 UTC.

Total time from first alert to confirmed resolution: 38 minutes.

Follow-Up

1. Implement validation for such specific edge-cases before proceeding with further infrastructure changes.
2. Audit all storage resources and network-restricted dependencies across all regions to identify and remediate similar configuration gaps before resuming the migration.
3. Implement automated pre-migration validation that verifies all dependent resources have been updated with new network configurations.
4. Add dedicated monitoring for storage connectivity failures to enable faster detection of this specific failure mode.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating an issue impacting Studio Web in the US region. Further updates will be provided shortly.

Resolved: The issue has been resolved. Our monitoring indicates that services are operating normally, and no further impact has been observed.

Identified: We have identified the cause of the outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions and are working on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our focus is on restoring service as quickly as possible.

Investigating: We are investigating reports of an outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions. Impact: Users may be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Resolved: The upstream dependency issue has been fully resolved. All Customer Portal services have been restored and are operating normally.

We apologize for any inconvenience caused. Thank you for your patience.

Monitoring: System recovery is in progress and Customer Portal features are now operational  We are currently monitoring system stability and conducting final verification before confirming  full resolution.

Investigating: The upstream provider has identified the root cause of the disruption and is actively deploying a fix across affected instances We are seeing gradual improvement in Customer Portal functionality.

Investigating: We are experiencing degraded service on Customer Portal affecting multiple support-related features.

Affected functionality:

• Customer Support Infrastructure
• Viewing existing support case details and email replies
• Account/Company data loading
• Self-registration case status checks
• File downloads linked to support cases

What's working:

• Authentication and login
• Non-support dependent features (Knowledge Base, Community, etc.)

Root cause: An upstream dependency used by Customer Portal's support Infrastructure is currently experiencing a service disruption.

Next steps: Our team is actively monitoring the situation and working to restore full service as quickly as possible. No action is required from customers at this time.

We will provide updates as the situation evolves.

Resolved: The issue has been resolved. Our monitoring indicates that services are operating normally, and no further impact has been observed.

Identified: We have identified the cause of the outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions and are working on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our focus is on restoring service as quickly as possible.

Investigating: We are investigating reports of an outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions. Impact: Users may be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Resolved: The upstream dependency issue has been fully resolved. All Customer Portal services have been restored and are operating normally.

We apologize for any inconvenience caused. Thank you for your patience.

Monitoring: System recovery is in progress and Customer Portal features are now operational  We are currently monitoring system stability and conducting final verification before confirming  full resolution.

Investigating: The upstream provider has identified the root cause of the disruption and is actively deploying a fix across affected instances We are seeing gradual improvement in Customer Portal functionality.

Investigating: We are experiencing degraded service on Customer Portal affecting multiple support-related features.

Affected functionality:

• Customer Support Infrastructure
• Viewing existing support case details and email replies
• Account/Company data loading
• Self-registration case status checks
• File downloads linked to support cases

What's working:

• Authentication and login
• Non-support dependent features (Knowledge Base, Community, etc.)

Root cause: An upstream dependency used by Customer Portal's support Infrastructure is currently experiencing a service disruption.

Next steps: Our team is actively monitoring the situation and working to restore full service as quickly as possible. No action is required from customers at this time.

We will provide updates as the situation evolves.

Resolved: The issue has been resolved. Our monitoring indicates that services are operating normally, and no further impact has been observed.

Identified: We have identified the cause of the outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions and are working on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our focus is on restoring service as quickly as possible.

Investigating: We are investigating reports of an outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions. Impact: Users may be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Resolved: The upstream dependency issue has been fully resolved. All Customer Portal services have been restored and are operating normally.

We apologize for any inconvenience caused. Thank you for your patience.

Monitoring: System recovery is in progress and Customer Portal features are now operational  We are currently monitoring system stability and conducting final verification before confirming  full resolution.

Investigating: The upstream provider has identified the root cause of the disruption and is actively deploying a fix across affected instances We are seeing gradual improvement in Customer Portal functionality.

Investigating: We are experiencing degraded service on Customer Portal affecting multiple support-related features.

Affected functionality:

• Customer Support Infrastructure
• Viewing existing support case details and email replies
• Account/Company data loading
• Self-registration case status checks
• File downloads linked to support cases

What's working:

• Authentication and login
• Non-support dependent features (Knowledge Base, Community, etc.)

Root cause: An upstream dependency used by Customer Portal's support Infrastructure is currently experiencing a service disruption.

Next steps: Our team is actively monitoring the situation and working to restore full service as quickly as possible. No action is required from customers at this time.

We will provide updates as the situation evolves.

Resolved: The issue has been resolved. Our monitoring indicates that services are operating normally, and no further impact has been observed.

Identified: We have identified the cause of the outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions and are working on a fix. Impact: Users may continue to be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our focus is on restoring service as quickly as possible.

Investigating: We are investigating reports of an outage impacting the Web Search tool used in RPA workflows and Agents in Multiple Regions. Impact: Users may be unable to run RPA workflows or deployed/debug Agents that rely on the Web Search tool, which may cause those automations to fail. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We are actively working on implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.

Identified: We have identified the cause of the disruption impacting Prepare Python environment step for Agents in Multiple Regions and are actively implementing a fix.

Impact: Coded agents failed at the Prepare Python environment step when requires-python>=3.12 was set in pyproject.toml. Workaround: Remove or lower the requires-python constraint in pyproject.toml to >=3.11 until the fix is deployed.

Next update: Additional updates will be provided as remediation continues.