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. The system has remained stable during the monitoring period.

Monitoring: A fix has been deployed and the service is recovering. Current status: We are monitoring the system to ensure stability and full recovery. Further updates will be shared soon

Investigating: We are currently investigating reports of an issue in Integration Service in multiple regions.

Impact: Integration Service existing connections are not visible in Orchestrator, and attempts to create a new connection result in no response

Our teams are actively working to identify the cause and assess the scope of the issue. Further updates will be shared as soon as more information becomes available.

Investigating: We are currently investigating reports of an issue in Integration Service in Singapore region.

Impact: Integration Service existing connections are not visible in Orchestrator, and attempts to create a new connection result in no response

Our teams are actively working to identify the cause and assess the scope of the issue. Further updates will be shared as soon as more information becomes available.

Resolved: The issue has been resolved.

Monitoring: A fix has been deployed and the service is recovered. Current status: We are monitoring the system to ensure stability and full recovery.

Investigating: New connection creation in UiPath Integration Service is currently failing in the Europe region. Existing connections and running automations are not impacted.

The team is actively working to resolve the issue. We will continue to provide updates on status.

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

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.

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 issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

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: 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 issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

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: 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 issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: The issue has been resolved. The system has remained stable during the monitoring period.

Monitoring: A fix has been deployed and the service is recovering. Current status: We are monitoring the system to ensure stability and full recovery. Further updates will be shared soon

Investigating: We are currently investigating reports of an issue in Integration Service in multiple regions.

Impact: Integration Service existing connections are not visible in Orchestrator, and attempts to create a new connection result in no response

Our teams are actively working to identify the cause and assess the scope of the issue. Further updates will be shared as soon as more information becomes available.

Investigating: We are currently investigating reports of an issue in Integration Service in Singapore region.

Impact: Integration Service existing connections are not visible in Orchestrator, and attempts to create a new connection result in no response

Our teams are actively working to identify the cause and assess the scope of the issue. Further updates will be shared as soon as more information becomes available.

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.