UiPath Status
Real-time updates of UiPath issues and outages
UiPath status is Operational
UiPath Automation Cloud
UiPath Orchestrator
UiPath Automation Hub
UiPath AI Center
UiPath Action Center
UiPath Apps
UiPath Automation Ops
Active Incidents
Our team is investigating an intermittent failures with document extraction in US region.
Postmortem: ## Customer Impact
Between December 9, 2025, at 4:00 PM UTC and December 10, 2025, at 7:00 AM UTC, customers in the US region experienced intermittent failures and delays when using the Document Understanding service, specifically affecting document extraction and training workloads.
Scope:
The impact was limited to the US region. Customers may have observed increased error rates or delays when processing documents, particularly during peak usage periods. Other regions and services were not affected.
Root Cause
The incident was triggered by a regional capacity constraint in our cloud provider's GPU infrastructure US region. Although quota for GPU resources was sufficient, the cloud provider was unable to allocate new GPU nodes due to high demand and limited physical availability in the region.
As customer traffic increased, clusters attempted to scale up, but new nodes could not be provisioned. This resulted in resource contention between extraction and training workloads.
- Extraction jobs — customer-facing and time-sensitive — began failing intermittently as GPU resources were exhausted.
- Training jobs stalled or were delayed.
Manual attempts to scale node pools or create new pools failed for the same reason. The cloud provider support confirmed that no additional GPU capacity was available and that alternative VM sizes were also constrained. Recovery was delayed because mitigation was only possible by reprioritizing workloads and waiting for GPU resources to free up.
Detection
The issue was first detected on December 9, 2025, at 16:00 UTC by automated monitoring systems reporting increased extraction error rates in the US region. Customer reports followed shortly after.
Initial investigation identified GPU allocation failures in node pools. Status page updates were posted proactively, and severity was escalated as impact was confirmed.
Response
Engineering teams analyzed cluster telemetry, node pool behavior, and platform logs. Multiple attempts to scale node pools or create new ones using alternative VM sizes failed due to our cloud provider's regional capacity issues.
To mitigate customer impact, the team took the following actions:
- Prioritized extraction workloads by scaling down or pausing training jobs, freeing GPU resources for extraction.
- Collaborated with the cloud provider support, who confirmed the capacity shortfall and initiated escalation.
- Monitored service health continuously until GPU resources became available naturally as regional demand fluctuated.
Service stability returned once extraction had sufficient GPU capacity, and training workloads were gradually reintroduced.
Follow-Up Actions
To prevent recurrence, the following improvements are underway:
- Capacity Planning:
Working with our cloud providers to secure additional reserved GPU capacity in the US region and evaluating alternative VM families. - Workload Prioritization:
Updating autoscaling and scheduling logic so extraction workloads are always prioritized during contention. - Monitoring & Alerting Enhancements:
Improved detection of early GPU allocation failures and automated workload reprioritization before customer impact. - Runbook Improvements:
Updating incident response runbooks to streamline cloud provider communication and document successful mitigation steps. - Cloud Provider Collaboration:
Strengthening engagement with our GPU infrastructure providers to gain better visibility into regional GPU availability and advocate for increased capacity.
We remain committed to delivering a reliable service and minimizing impact from underlying infrastructure constraints. Long-term improvements will continue to be communicated as they are implemented.
Resolved: The incident has been resolved.
Monitoring: A fix has been implemented, and we are currently monitoring the results.
Identified: Our team has identified the root cause and working towards implementing a fix. Although failure volume is low, a small percentage of organizations may experience intermittent degradation.
Investigating: Our team is investigating an intermittent failures with document extraction in US region.
Our team is investigating access failures affecting the Admin UI for the Autopilot for Everyone service in the Delayed US region.
Postmortem: ## Customer Impact
From December 8, 2025, 11:47 pm UTC to December 9, 2025, 2:05 am UTC, customers experienced an outage affecting the AI Trust Layer in our Delayed US region.
Multiple UiPath products that depend on this layer — including Autopilot For Everyone, AI Center, and LLMOps — experienced degraded functionality or complete service interruption during this period.
Root Cause
The outage was caused by an incorrect configuration of feature flags controlling the AI Trust Layer, which rendered the service inaccessible.
Detection
Our synthetic monitoring system first identified the issue through automated alerts that detected service failures, triggering our incident response protocol.
Response
Upon alert activation, our team conducted a comprehensive investigation across network and service layers. The investigation identified the root cause as a recently applied feature flag configuration.
Remediation included:
- Deploying the correct feature flag configuration across the affected region
- Verifying AI Trust Layer accessibility was restored
- Confirming all dependent UiPath products automatically resumed normal operation
Full service restoration was achieved immediately following the configuration deployment.
Follow-Up
To prevent similar incidents in the future, we will:
- Conduct a comprehensive review of our feature flag configuration management strategy and processes
- Implement enhanced safeguards for configuration rollouts, including pre-deployment validation
- Strengthen our testing procedures for critical service dependencies
Resolved: The incident has been resolved.
Monitoring: The fix has been deployed. We are observing the service closely to ensure the issue does not recur.
Identified: We have identified the root cause of the issue and are currently implementing a solution.
Investigating: Our team is investigating access failures affecting the Admin UI for the Autopilot for Everyone service in the Delayed US region.
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
Recently Resolved Incidents
No recent incidents
UiPath Outage Survival Guide
UiPath Components
UiPath Automation Cloud
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Orchestrator
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Automation Hub
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath AI Center
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Action Center
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Apps
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Automation Ops
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Computer Vision
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Cloud Robots - VM
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Customer Portal
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Data Service
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Documentation Portal
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Document Understanding
Our team is investigating an intermittent failures with document extraction in US region.
Postmortem: ## Customer Impact
Between December 9, 2025, at 4:00 PM UTC and December 10, 2025, at 7:00 AM UTC, customers in the US region experienced intermittent failures and delays when using the Document Understanding service, specifically affecting document extraction and training workloads.
Scope:
The impact was limited to the US region. Customers may have observed increased error rates or delays when processing documents, particularly during peak usage periods. Other regions and services were not affected.
Root Cause
The incident was triggered by a regional capacity constraint in our cloud provider's GPU infrastructure US region. Although quota for GPU resources was sufficient, the cloud provider was unable to allocate new GPU nodes due to high demand and limited physical availability in the region.
As customer traffic increased, clusters attempted to scale up, but new nodes could not be provisioned. This resulted in resource contention between extraction and training workloads.
- Extraction jobs — customer-facing and time-sensitive — began failing intermittently as GPU resources were exhausted.
- Training jobs stalled or were delayed.
Manual attempts to scale node pools or create new pools failed for the same reason. The cloud provider support confirmed that no additional GPU capacity was available and that alternative VM sizes were also constrained. Recovery was delayed because mitigation was only possible by reprioritizing workloads and waiting for GPU resources to free up.
Detection
The issue was first detected on December 9, 2025, at 16:00 UTC by automated monitoring systems reporting increased extraction error rates in the US region. Customer reports followed shortly after.
Initial investigation identified GPU allocation failures in node pools. Status page updates were posted proactively, and severity was escalated as impact was confirmed.
Response
Engineering teams analyzed cluster telemetry, node pool behavior, and platform logs. Multiple attempts to scale node pools or create new ones using alternative VM sizes failed due to our cloud provider's regional capacity issues.
To mitigate customer impact, the team took the following actions:
- Prioritized extraction workloads by scaling down or pausing training jobs, freeing GPU resources for extraction.
- Collaborated with the cloud provider support, who confirmed the capacity shortfall and initiated escalation.
- Monitored service health continuously until GPU resources became available naturally as regional demand fluctuated.
Service stability returned once extraction had sufficient GPU capacity, and training workloads were gradually reintroduced.
Follow-Up Actions
To prevent recurrence, the following improvements are underway:
- Capacity Planning:
Working with our cloud providers to secure additional reserved GPU capacity in the US region and evaluating alternative VM families. - Workload Prioritization:
Updating autoscaling and scheduling logic so extraction workloads are always prioritized during contention. - Monitoring & Alerting Enhancements:
Improved detection of early GPU allocation failures and automated workload reprioritization before customer impact. - Runbook Improvements:
Updating incident response runbooks to streamline cloud provider communication and document successful mitigation steps. - Cloud Provider Collaboration:
Strengthening engagement with our GPU infrastructure providers to gain better visibility into regional GPU availability and advocate for increased capacity.
We remain committed to delivering a reliable service and minimizing impact from underlying infrastructure constraints. Long-term improvements will continue to be communicated as they are implemented.
Resolved: The incident has been resolved.
Monitoring: A fix has been implemented, and we are currently monitoring the results.
Identified: Our team has identified the root cause and working towards implementing a fix. Although failure volume is low, a small percentage of organizations may experience intermittent degradation.
Investigating: Our team is investigating an intermittent failures with document extraction in US region.
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Insights
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Integration Service
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Marketplace
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Process Mining
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Task Mining
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Test Manager
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath IXP
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Serverless Robots
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Studio Web
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Solutions Management
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Context Grounding
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Autopilot for Everyone
Our team is investigating access failures affecting the Admin UI for the Autopilot for Everyone service in the Delayed US region.
Postmortem: ## Customer Impact
From December 8, 2025, 11:47 pm UTC to December 9, 2025, 2:05 am UTC, customers experienced an outage affecting the AI Trust Layer in our Delayed US region.
Multiple UiPath products that depend on this layer — including Autopilot For Everyone, AI Center, and LLMOps — experienced degraded functionality or complete service interruption during this period.
Root Cause
The outage was caused by an incorrect configuration of feature flags controlling the AI Trust Layer, which rendered the service inaccessible.
Detection
Our synthetic monitoring system first identified the issue through automated alerts that detected service failures, triggering our incident response protocol.
Response
Upon alert activation, our team conducted a comprehensive investigation across network and service layers. The investigation identified the root cause as a recently applied feature flag configuration.
Remediation included:
- Deploying the correct feature flag configuration across the affected region
- Verifying AI Trust Layer accessibility was restored
- Confirming all dependent UiPath products automatically resumed normal operation
Full service restoration was achieved immediately following the configuration deployment.
Follow-Up
To prevent similar incidents in the future, we will:
- Conduct a comprehensive review of our feature flag configuration management strategy and processes
- Implement enhanced safeguards for configuration rollouts, including pre-deployment validation
- Strengthen our testing procedures for critical service dependencies
Resolved: The incident has been resolved.
Monitoring: The fix has been deployed. We are observing the service closely to ensure the issue does not recur.
Identified: We have identified the root cause of the issue and are currently implementing a solution.
Investigating: Our team is investigating access failures affecting the Admin UI for the Autopilot for Everyone service in the Delayed US region.
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Autopilot (Plugins)
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Agents
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.
UiPath Agentic Orchestration
UiPath is facing outage globally due to our DNS provider facing issues.
Postmortem: ## Customer Impact
Between December 5, 2025 08:56 UTC and December 5, 2025 09:30 UTC, customers may have experienced disruption when accessing Automation Cloud platform and Support Portal due to issue with our DNS provider.
Users globally were affected.
Root Cause
The disruption was triggered by an upstream outage at our DNS provider, Cloudflare, which began at 08:56 UTC on December 5, 2025. During this period, DNS resolution failures prevented customers from accessing the platform. While Cloudflare restored normal DNS operations at 09:20 UTC, downstream service recovery within UiPath continued for an additional 10 minutes.
Once DNS services resumed, the Authentication service experienced a sudden surge in incoming requests. Because the service had scaled down during the outage due to reduced traffic, this post-outage traffic spike required rapid scaling of the underlying infrastructure.
As new compute instances came online, they initiated a high number of simultaneous SQL connection requests. This led to a significant spike in active SQL connections during the rapid scale-up, resulting in temporary database load and intermittent request failures. The combination of accelerated autoscaling, elevated request volume, and the sharp increase in SQL connections caused intermittent failures in the Authentication service immediately after DNS recovery. These cascading effects extended the impact window beyond the initial Cloudflare outage, leading to temporary service degradation until the system fully stabilized at 09:30 UTC.
Detection
The issue was detected through our internal monitoring systems, which triggered alerts across all UiPath hosted regions. It was promptly classified and declared a high-severity incident.
Response
- Engineering teams monitored the system closely after DNS recovery and identified that the post-outage impact was caused by a sudden traffic surge and rapid autoscaling of the Authentication service.
- No manual intervention was required, as the autoscaling mechanism automatically provisioned new compute instances, which initialized, established database connections, and stabilized as traffic normalized.
- Full service recovery was achieved within approximately 10 minutes after DNS restoration, with no further issues observed thereafter.
Follow Up
We will update our autoscaling configuration to maintain a optimal number of Authentication service compute instances, based on historical traffic patterns and average load requirements. Ensuring a baseline capacity will help maintain readiness during abrupt traffic recoveries such as those following external dependency outages. This will reduce cold-start delays, prevent sudden spikes in SQL connections during rapid scale-up, and minimize the risk of similar service degradation in the future.
Cloudflare Root Cause Analysis - Cloudflare outage on December 5, 2025
Resolved: We are pleased to confirm that the issue caused by our DNS provider has been fully mitigated. All UiPath cloud services, including the Support Portal, have been restored and are operating normally.
Our teams will continue to monitor performance closely.
Thank you for your patience and understanding throughout this incident.
Monitoring: Our DNS provider, has implemented a fix for the issue that caused a global service disruption. We are already seeing recovery across UiPath cloud services, including the Support Portal.
Our teams continue to closely monitor system performance to ensure full restoration. Some services may take additional time to stabilize as the fix propagates globally.
Thank you for your patience and understanding while this incident was addressed. We will provide a final update once all services are fully confirmed as operational.
Identified: We are aware of a global outage affecting UiPath services due to an issue with our DNS provider. As a result, you may experience disruptions when accessing UiPath Cloud services including our Support Portal, which is currently impacted by this DNS outage. Our engineering and infrastructure teams are actively working with provider to restore services as quickly as possible. We are monitoring the situation continuously and will share updates as soon as more information becomes available. We sincerely apologize for the inconvenience this may cause and appreciate your patience while we work to resolve this issue.
Identified: UiPath is facing outage globally due to our DNS provider facing issues.