UiPath Status

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The mitigation has been successfully implemented, and service has been restored.

Impact has been resolved for Document Understanding, Agents, IXP, and GenAI Activities across all affected regions. Users should no longer experience request failures, elevated error rates, or degraded performance when using GPT-4.0-powered features and workflows.

We will continue to monitor the services to ensure stability.

Identified: An issue with an upstream provider may be impacting GPT-4.0-powered functionality for Document Understanding, Agents, IXP, and GenAI Activities across multiple regions, and we are investigating.

Impact: Users may experience request failures, increased error rates, or degraded performance when using GPT-4.0-powered features and workflows.

Our teams have identified a potential mitigation and are actively implementing it to reduce customer impact. We will continue to provide updates as progress is made.

Investigating: An issue with an upstream provider may be impacting GPT-4.0-powered functionality for Document Understanding, Agents, IXP, and GenAI Activities across multiple regions, and we are investigating.

Impact: Users may experience request failures, increased error rates, or degraded performance when using GPT-4.0-powered features and workflows.

Resolved: The outage has been resolved and IXP is fully operational. Impact: No ongoing user impact.

Monitoring: All regions are fully operational. We will perform validations, and share any further updates as they become available

Monitoring: We have applied and confirmed the fix in several regions, are are continuing to roll it out

Monitoring: The fix has been deployed in the Japan region and we are validating its effectiveness. Additional testing is underway to confirm recovery. Services in all other regions remain fully operational. We will share further updates as they become available.

Monitoring: A fix has been implemented successfully in all regions except Japan, where we are still actively working on resolving the issue. Services in other regions are operating normally. Our team continues to investigate and implement the fix for the Japan region, and we will provide further updates as soon as possible.

Monitoring: We continue to monitor the service and have not observed any further issues so far. The system remains stable, and we will keep monitoring for continued assurance.

Monitoring: A fix has been implemented and services are operating normally. We are continuing to monitor the service to ensure stability.

Identified: We have identified the issue and are working on implementing a fix.

Investigating: Investigation is ongoing. Our team continues to work toward a finding the root cause and we will share further updates as available.

Investigating: We are currently experiencing delays and intermittent failures affecting document extraction that use Gemini models. Users may notice delay or unsuccessful processing requests across all regions. Our team is actively investigating the issue and working to restore normal performance.

Resolved: The incident is resolved

Monitoring: We have rolled back a previous change which was responsible for the issue, and are seeing calls to GPT models succeed again. Next update: we expect no further service disruptions, and will update once we have confirmed all regions are recovered

Investigating: We are investigating failures and increased latency with GPT models for IXP. Impact: Users may be unable to use GPT models in IXP. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: The mitigation has been successfully implemented, and service has been restored.

Impact has been resolved for Document Understanding, Agents, IXP, and GenAI Activities across all affected regions. Users should no longer experience request failures, elevated error rates, or degraded performance when using GPT-4.0-powered features and workflows.

We will continue to monitor the services to ensure stability.

Identified: An issue with an upstream provider may be impacting GPT-4.0-powered functionality for Document Understanding, Agents, IXP, and GenAI Activities across multiple regions, and we are investigating.

Impact: Users may experience request failures, increased error rates, or degraded performance when using GPT-4.0-powered features and workflows.

Our teams have identified a potential mitigation and are actively implementing it to reduce customer impact. We will continue to provide updates as progress is made.

Investigating: An issue with an upstream provider may be impacting GPT-4.0-powered functionality for Document Understanding, Agents, IXP, and GenAI Activities across multiple regions, and we are investigating.

Impact: Users may experience request failures, increased error rates, or degraded performance when using GPT-4.0-powered features and workflows.

Resolved: The mitigation has been successfully implemented, and service has been restored.

Impact has been resolved for Document Understanding, Agents, IXP, and GenAI Activities across all affected regions. Users should no longer experience request failures, elevated error rates, or degraded performance when using GPT-4.0-powered features and workflows.

We will continue to monitor the services to ensure stability.

Identified: An issue with an upstream provider may be impacting GPT-4.0-powered functionality for Document Understanding, Agents, IXP, and GenAI Activities across multiple regions, and we are investigating.

Impact: Users may experience request failures, increased error rates, or degraded performance when using GPT-4.0-powered features and workflows.

Our teams have identified a potential mitigation and are actively implementing it to reduce customer impact. We will continue to provide updates as progress is made.

Investigating: An issue with an upstream provider may be impacting GPT-4.0-powered functionality for Document Understanding, Agents, IXP, and GenAI Activities across multiple regions, and we are investigating.

Impact: Users may experience request failures, increased error rates, or degraded performance when using GPT-4.0-powered features and workflows.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The outage has been resolved and IXP is fully operational. Impact: No ongoing user impact.

Monitoring: All regions are fully operational. We will perform validations, and share any further updates as they become available

Monitoring: We have applied and confirmed the fix in several regions, are are continuing to roll it out

Monitoring: The fix has been deployed in the Japan region and we are validating its effectiveness. Additional testing is underway to confirm recovery. Services in all other regions remain fully operational. We will share further updates as they become available.

Monitoring: A fix has been implemented successfully in all regions except Japan, where we are still actively working on resolving the issue. Services in other regions are operating normally. Our team continues to investigate and implement the fix for the Japan region, and we will provide further updates as soon as possible.

Monitoring: We continue to monitor the service and have not observed any further issues so far. The system remains stable, and we will keep monitoring for continued assurance.

Monitoring: A fix has been implemented and services are operating normally. We are continuing to monitor the service to ensure stability.

Identified: We have identified the issue and are working on implementing a fix.

Investigating: Investigation is ongoing. Our team continues to work toward a finding the root cause and we will share further updates as available.

Investigating: We are currently experiencing delays and intermittent failures affecting document extraction that use Gemini models. Users may notice delay or unsuccessful processing requests across all regions. Our team is actively investigating the issue and working to restore normal performance.

Resolved: The incident is resolved

Monitoring: We have rolled back a previous change which was responsible for the issue, and are seeing calls to GPT models succeed again. Next update: we expect no further service disruptions, and will update once we have confirmed all regions are recovered

Investigating: We are investigating failures and increased latency with GPT models for IXP. Impact: Users may be unable to use GPT models in IXP. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: The issue has been fully resolved, and all systems are operating normally.

Monitoring: The database issue impacting IXP and Communication Mining has been resolved, and services are recovering normally. Our team is monitoring the systems closely to ensure continued stability.

Investigating: We are investigating an issue impacting IXP and Communication Mining caused by a database outage. Our team is actively working to restore service and will provide updates as they become available.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The outage has been resolved and IXP is fully operational. Impact: No ongoing user impact.

Monitoring: All regions are fully operational. We will perform validations, and share any further updates as they become available

Monitoring: We have applied and confirmed the fix in several regions, are are continuing to roll it out

Monitoring: The fix has been deployed in the Japan region and we are validating its effectiveness. Additional testing is underway to confirm recovery. Services in all other regions remain fully operational. We will share further updates as they become available.

Monitoring: A fix has been implemented successfully in all regions except Japan, where we are still actively working on resolving the issue. Services in other regions are operating normally. Our team continues to investigate and implement the fix for the Japan region, and we will provide further updates as soon as possible.

Monitoring: We continue to monitor the service and have not observed any further issues so far. The system remains stable, and we will keep monitoring for continued assurance.

Monitoring: A fix has been implemented and services are operating normally. We are continuing to monitor the service to ensure stability.

Identified: We have identified the issue and are working on implementing a fix.

Investigating: Investigation is ongoing. Our team continues to work toward a finding the root cause and we will share further updates as available.

Investigating: We are currently experiencing delays and intermittent failures affecting document extraction that use Gemini models. Users may notice delay or unsuccessful processing requests across all regions. Our team is actively investigating the issue and working to restore normal performance.

Resolved: The incident is resolved

Monitoring: We have rolled back a previous change which was responsible for the issue, and are seeing calls to GPT models succeed again. Next update: we expect no further service disruptions, and will update once we have confirmed all regions are recovered

Investigating: We are investigating failures and increased latency with GPT models for IXP. Impact: Users may be unable to use GPT models in IXP. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The outage has been resolved and IXP is fully operational. Impact: No ongoing user impact.

Monitoring: All regions are fully operational. We will perform validations, and share any further updates as they become available

Monitoring: We have applied and confirmed the fix in several regions, are are continuing to roll it out

Monitoring: The fix has been deployed in the Japan region and we are validating its effectiveness. Additional testing is underway to confirm recovery. Services in all other regions remain fully operational. We will share further updates as they become available.

Monitoring: A fix has been implemented successfully in all regions except Japan, where we are still actively working on resolving the issue. Services in other regions are operating normally. Our team continues to investigate and implement the fix for the Japan region, and we will provide further updates as soon as possible.

Monitoring: We continue to monitor the service and have not observed any further issues so far. The system remains stable, and we will keep monitoring for continued assurance.

Monitoring: A fix has been implemented and services are operating normally. We are continuing to monitor the service to ensure stability.

Identified: We have identified the issue and are working on implementing a fix.

Investigating: Investigation is ongoing. Our team continues to work toward a finding the root cause and we will share further updates as available.

Investigating: We are currently experiencing delays and intermittent failures affecting document extraction that use Gemini models. Users may notice delay or unsuccessful processing requests across all regions. Our team is actively investigating the issue and working to restore normal performance.

Resolved: The incident is resolved

Monitoring: We have rolled back a previous change which was responsible for the issue, and are seeing calls to GPT models succeed again. Next update: we expect no further service disruptions, and will update once we have confirmed all regions are recovered

Investigating: We are investigating failures and increased latency with GPT models for IXP. Impact: Users may be unable to use GPT models in IXP. Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: The issue has been fully resolved and service is back to operational.

Monitoring: The stale subscriptions have been cleaned up and message delivery has been restored. Robot allocation changes are now propagating to Orchestrator as expected. We are actively monitoring the system to ensure stability and confirm no further throttling occurs.

Identified: We identified an issue where robot allocations made at the tenant level were not being reflected in Orchestrator. The root cause was traced to messages throttling caused by exceeded storage quotas. Stale duplicate subscriptions with no active consumers had accumulated unread messages, exhausting the storage limit and blocking new message delivery.

Resolved: The outage has been resolved and IXP is fully operational. Impact: No ongoing user impact.

Monitoring: All regions are fully operational. We will perform validations, and share any further updates as they become available

Monitoring: We have applied and confirmed the fix in several regions, are are continuing to roll it out

Monitoring: The fix has been deployed in the Japan region and we are validating its effectiveness. Additional testing is underway to confirm recovery. Services in all other regions remain fully operational. We will share further updates as they become available.

Monitoring: A fix has been implemented successfully in all regions except Japan, where we are still actively working on resolving the issue. Services in other regions are operating normally. Our team continues to investigate and implement the fix for the Japan region, and we will provide further updates as soon as possible.

Monitoring: We continue to monitor the service and have not observed any further issues so far. The system remains stable, and we will keep monitoring for continued assurance.

Monitoring: A fix has been implemented and services are operating normally. We are continuing to monitor the service to ensure stability.

Identified: We have identified the issue and are working on implementing a fix.

Investigating: Investigation is ongoing. Our team continues to work toward a finding the root cause and we will share further updates as available.

Investigating: We are currently experiencing delays and intermittent failures affecting document extraction that use Gemini models. Users may notice delay or unsuccessful processing requests across all regions. Our team is actively investigating the issue and working to restore normal performance.

Resolved: The incident is resolved

Monitoring: We have rolled back a previous change which was responsible for the issue, and are seeing calls to GPT models succeed again. Next update: we expect no further service disruptions, and will update once we have confirmed all regions are recovered

Investigating: We are investigating failures and increased latency with GPT models for IXP. Impact: Users may be unable to use GPT models in IXP. Next update: Our teams are working to understand the cause and scope and will share updates as available.