Cisco Umbrella Outage History

Started Apr 29, 2026, 07:11 PM UTC· resolved Apr 29, 2026, 09:54 PM UTC

1. investigating Apr 29, 2026, 07:11 PM UTC

   We are currently investigating an issue impacting Cisco Secure Connect onboarding. Due to a third-party provider outage affecting certificate issuance, onboarding of new organizations may fail or become stuck. Additionally, newly provisioned sites are unable to generate certificates at this time. Existing customers, active services, and existing sites and sessions remain unaffected and continue to operate normally. Our engineering team is actively working with the provider to restore normal onboarding. We will provide updates as more information becomes available.

2. investigating Apr 29, 2026, 08:53 PM UTC

   We are actively working with third-party vendor to remediate the certificate provisioning issue. We will continue to provide updates as additional information becomes available.

3. monitoring Apr 29, 2026, 09:24 PM UTC

   The third-party vendor has remediated the certificate provisioning issue. We are now seeing onboarding return to normal patterns.

4. resolved Apr 29, 2026, 09:54 PM UTC

   The third-party vendor has resolved the certificate provisioning issue, and onboarding processes are now working as expected.

Read the full incident report →

Started Apr 08, 2026, 10:31 AM UTC· resolved Apr 08, 2026, 12:46 PM UTC

1. investigating Apr 08, 2026, 10:31 AM UTC

   We are continuing to investigate the issue with Zero Trust Access enrollment, which may be affecting a limited number of customers. The issue may impact only new enrollment attempts, while existing connections remain uninterrupted. Our team is working to confirm the extent of the impact and restore normal service as quickly as possible. Further updates will be provided as more information becomes available. Thank you for your patience and understanding.

2. identified Apr 08, 2026, 10:53 AM UTC

   We have identified the root cause of the issue. Mitigation steps will be implemented to restore normal service as quickly as possible. Further updates will be provided as we make progress.

3. monitoring Apr 08, 2026, 12:38 PM UTC

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

4. resolved Apr 08, 2026, 12:46 PM UTC

   The issue affecting Zero Trust Access enrollment for some users is resolved. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Connect experience.

Read the full incident report →

Started Apr 07, 2026, 05:00 AM UTC· resolved Apr 07, 2026, 06:14 AM UTC

1. investigating Apr 07, 2026, 05:00 AM UTC

   We are currently investigating reports of service performance issues affecting our Umbrella/Secure Connect platform in the Chennai and Mumbai regions. Some users may experience temporary connectivity delays or intermittent service interruptions while accessing our proxy services. Our engineering team is actively working to stabilize the environment and restore full service performance as quickly as possible. We appreciate your patience and understanding as we work to improve your Cisco Umbrella/Secure Connect experience.

2. investigating Apr 07, 2026, 05:44 AM UTC

   We are still actively investigating the issue affecting service performance for our Umbrella/Secure Connect. We appreciate your patience and will provide updates as soon as new information becomes available.

3. resolved Apr 07, 2026, 06:14 AM UTC

   The service performance issues affecting our Umbrella/Secure Connect platform in the Chennai and Mumbai regions have been resolved. Our engineering team has stabilized the environment, and all services are now operating as expected. We’re Here to Help Thank you for your patience and understanding while we worked to restore full service. If you have any questions or need assistance, please contact our support team.

Read the full incident report →

Started Apr 01, 2026, 04:26 AM UTC· resolved Apr 01, 2026, 11:17 AM UTC

1. identified Apr 01, 2026, 04:26 AM UTC

   We have identified a potential issue with the Remote Browser Isolation (RBI) service affecting customers connecting to the Middle East (UAE) data center. Actual Impact: Customers in the Middle East (UAE) region may be experiencing "fail open" errors when attempting to access the Remote Browser Isolation service. This may result in unexpected behavior where traffic is not being isolated as per configured policies. Our engineering team is actively working to identify the root cause, and implement a resolution. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding.

2. resolved Apr 01, 2026, 11:17 AM UTC

   We are pleased to confirm that the issue affecting the Remote Browser Isolation (RBI) service in the Middle East (UAE) data center has been resolved. All services are now operating normally, and customers should no longer experience "fail open" errors or unexpected behavior when accessing the RBI service. Thank you for your patience and understanding while we worked to restore full service. If you have any questions or need assistance, please contact our support team.

Read the full incident report →

Started Mar 26, 2026, 12:53 PM UTC· resolved Mar 26, 2026, 01:08 PM UTC

1. investigating Mar 26, 2026, 12:53 PM UTC

   We are currently investigating reports of timeouts and slow connections affecting services in the Manchester (man1) data center. Our team is working to identify the cause and restore full service as quickly as possible. Updates will be provided here as more information becomes available. Thank you for your patience and understanding.

2. resolved Mar 26, 2026, 01:08 PM UTC

   We are pleased to confirm that the timeout and slow connection issue affecting services in the Manchester (man1) data center has been fully resolved. All services are now operating normally.

Read the full incident report →

Started Mar 24, 2026, 07:17 PM UTC· resolved Mar 24, 2026, 09:07 PM UTC

1. identified Mar 24, 2026, 07:17 PM UTC

   We are investigating a partial service degradation issue affecting Cisco Umbrella customers in the Vancouver (YVR) region. Customers may experience increased latency and intermittent connectivity. Our engineering team has identified the cause and is actively implementing mitigation steps to restore full service. We are committed to resolving this as quickly as possible and will provide updates as new information becomes available. We appreciate your patience and understanding

2. resolved Mar 24, 2026, 09:07 PM UTC

   The issue affecting Cisco Umbrella customers in the Vancouver (YVR) region has been resolved.All services are now operating normally. We’re Here to Help If you have any questions or need assistance, please contact our support team.

Read the full incident report →

Started Mar 20, 2026, 04:26 PM UTC· resolved Mar 20, 2026, 05:19 PM UTC

1. investigating Mar 20, 2026, 04:26 PM UTC

   We are currently investigating an issue affecting the sandboxing -file scanning service in the Denver region. Customers utilizing Umbrella and Secure Connect services via the Denver EDC, and who have enabled the optional sandbox feature, may encounter a fail-open condition under certain circumstances. The impact is currently expected to be limited to a small subset of customers. Engineers are actively working to identify the root cause, and we will provide updates as more information becomes available.

2. monitoring Mar 20, 2026, 05:14 PM UTC

   The issue affecting the sandboxing - file scanning service in the Denver region has been mitigated. Services are operating normally, and functionality has been restored. We are continuing to monitor the environment to ensure stability.

3. resolved Mar 20, 2026, 05:19 PM UTC

   The issue has been resolved. Services are operating normally, and functionality has been restored. We’re Here to Help If you have any questions or need assistance, please contact our support team.

Read the full incident report →

Started Mar 20, 2026, 11:50 AM UTC· resolved Mar 20, 2026, 01:43 PM UTC

1. identified Mar 20, 2026, 11:50 AM UTC

   Due to high load in the FRA1 data center, new connections for Cisco+ Secure Connect VPN will be redirected to their closest configured site. Existing connections will remain intact and will not be interrupted. This is an informational update; no impact is expected for this service. We are implementing this change to ensure continued performance and reliability. If you have any questions or need assistance, please contact our support team.

2. resolved Mar 20, 2026, 01:43 PM UTC

   We are pleased to confirm that the FRA1 data center has been successfully brought Back Into Rotation (BIR). All services are fully operational, and new connections for Cisco+ Secure Connect VPN are now being directed to FRA1 as usual. Thank you for your patience and understanding. If you have any questions or need assistance, please contact our support team.

Read the full incident report →

Started Mar 18, 2026, 06:06 PM UTC· resolved Mar 18, 2026, 06:06 PM UTC

1. resolved Mar 18, 2026, 06:06 PM UTC

   Earlier today at approximately 17:20 UTC, users connected to Cisco Secure Connect in the nyc1 data center may have experienced an administrative disconnect.Users were able to manually reconnect to the service, and no further impact was observed.The issue has been resolved, and services are operating normally. We’re Here to Help If you have any questions or need assistance, please contact our support team.

Read the full incident report →

Started Mar 10, 2026, 05:14 AM UTC· resolved Mar 10, 2026, 05:52 AM UTC

1. investigating Mar 10, 2026, 05:14 AM UTC

   We are investigating a potential issue with the DNS Resolvers service affecting customers connecting to the Middle East data centers. Our engineering team is actively working to confirm the impact, identify the root cause, and implement a resolution. We are committed to restoring full service as quickly as possible. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding during this time.

2. resolved Mar 10, 2026, 05:52 AM UTC

   The issue affecting the DNS Resolvers service in the Middle East data center has been resolved. The service is now operating normally. We apologize for any inconvenience caused and thank you for your patience. We’re Here to Help: If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

Read the full incident report →

Started Mar 07, 2026, 08:58 PM UTC· resolved Mar 07, 2026, 08:58 PM UTC

1. resolved Mar 07, 2026, 08:58 PM UTC

   We have successfully resolved the service disruption caused by an issue suspected with an external infrastructure provider. All services are now fully operational.

Read the full incident report →

Started Mar 06, 2026, 05:22 AM UTC· resolved Mar 06, 2026, 05:46 AM UTC

1. investigating Mar 06, 2026, 05:22 AM UTC

   We are investigating a potential issue with SWG FQDN service affecting customers connecting to the Multiple Region across data center. Customer will not be able to access as SWG FQDN as the Service is not be able resolve the IP Cisco is currently working to confirm the impact, identify the root cause, and implement a resolution. We are committed to restoring full service as quickly as possible. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding during this time

2. resolved Mar 06, 2026, 05:46 AM UTC

   The issue affecting SWG FQDN has been resolved as of 05:36 UTC Mar 06, 2026 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

Read the full incident report →

Started Mar 02, 2026, 07:51 PM UTC· resolved Mar 02, 2026, 07:51 PM UTC

1. resolved Mar 02, 2026, 07:51 PM UTC

   We identified an issue impacting DLP event reporting between 18:43 UTC and 19:09 UTC. During this time, DLP policies continued to be enforced. However, some DLP events may not have been recorded or displayed in dashboards. DLP Reporting functionality has now been fully restored. We apologize for the inconvenience.If you have any questions or need assistance, please contact our support team.

Read the full incident report →

Started Feb 28, 2026, 04:20 PM UTC· resolved Feb 28, 2026, 05:44 PM UTC

1. investigating Feb 28, 2026, 04:20 PM UTC

   We are investigating an issue where the 'AnyDestination' functionality within DLP is currently experiencing a service degradation. As a result, scanners are failing to process 'any destination' requests appropriately and are instead reverting to legacy enforcement behavior. This has resulted in a 'fail-open' state, where policy enforcement is currently wide open. Our team is actively working to restore full functionality.

2. identified Feb 28, 2026, 04:49 PM UTC

   We have identified the cause affecting 'AnyDestination' functionality within Data Loss Prevention. Remediation efforts are underway. Updates will be provided as restoration progresses.

3. monitoring Feb 28, 2026, 05:31 PM UTC

   Remediation efforts have been implemented to address the issue affecting 'AnyDestination' functionality. We are now monitoring the environment as service functionality is restored across the platform. We will provide a final update once full stability is confirmed.

4. resolved Feb 28, 2026, 05:44 PM UTC

   Full service functionality has been restored. All services are now operating normally. We’re Here to Help We apologize for any inconvenience caused and thank you for your patience.If you have any questions or need assistance, please contact our support team.

Read the full incident report →

Started Feb 27, 2026, 05:23 PM UTC· resolved Mar 12, 2026, 03:23 PM UTC

1. investigating Feb 27, 2026, 05:23 PM UTC

   We are currently investigating an issue impacting one feature within the Investigate dashboard, specifically the DNS query volume . This affects the visibility of query volume data in the UI. All other Umbrella services, including DNS resolution, traffic handling, and policy enforcement, remain fully operational. Our team is actively working to restore normal data processing for the affected dashboard feature and will provide updates as they become available.

2. identified Feb 27, 2026, 06:03 PM UTC

   We have identified the issue impacting the DNS query volume display within the Investigate dashboard. DNS resolution, traffic handling, and policy enforcement remain fully operational. The team is preparing remediation steps and will continue monitoring the system

3. identified Feb 27, 2026, 06:27 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Feb 27, 2026, 06:31 PM UTC

   We are continuing to work on a fix for this issue.

5. identified Mar 02, 2026, 06:36 PM UTC

   Our engineering teams are continuing to make progress on resolving the display issue within the Investigate dashboard. While remediation is in progress, we anticipate it may take a few more days to fully resolve. We will provide further updates as they become available.

6. resolved Mar 12, 2026, 03:23 PM UTC

   We are pleased to confirm that the display issue impacting the Investigate dashboard has been fully resolved. All dashboard functions are now operating as expected. Thank you for your patience and understanding while we worked to restore full service.

Read the full incident report →

Started Feb 12, 2026, 09:16 AM UTC· resolved Feb 12, 2026, 02:05 PM UTC

1. investigating Feb 12, 2026, 09:16 AM UTC

   We are investigating a global issue with the Policy Enforcement service, which is currently experiencing delayed processing. As a result, customers are temporarily unable to update their policies; any posture changes configured on the dashboard will not take effect at this time. Our engineering team has upgraded CPU resources and is actively working to identify the root cause and restore full functionality as quickly as possible. We will provide updates at regular intervals as more information becomes available. We appreciate your patience and understanding during this time. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

2. investigating Feb 12, 2026, 10:02 AM UTC

   Our engineering team has upgraded CPU resources and is monitoring the environment to determine if this action improves processing times. Further investigation is underway to identify the root cause of the delay. We will provide additional updates as more information becomes available. Thank you for your patience and understanding.

3. investigating Feb 12, 2026, 11:33 AM UTC

   We are currently experiencing delays in policy updates due to an unusually high processing load. Efforts are underway to optimize performance and improve processing times. While changes have been made to help accelerate the process, customers may continue to experience slower policy updates for the time being. We appreciate your patience and understanding as we work to resolve this issue and will provide further updates as soon as more information is available.

4. identified Feb 12, 2026, 12:30 PM UTC

   Processing delays are ongoing, but progress continues toward resolution. We expect the current policy update backlog to be cleared within the next few hours. Once all outstanding entries are processed, normal policy update functionality will be restored. We appreciate your patience and understanding as we work to resolve this issue.

5. identified Feb 12, 2026, 01:39 PM UTC

   We are continuing to process the remaining policy updates and are making steady progress toward full resolution. We are very close to moving into a monitoring state and expect normal policy update functionality to be restored soon. Further updates will be provided as we confirm resolution. We appreciate your patience and understanding as we work to restore optimal service.

6. resolved Feb 12, 2026, 02:05 PM UTC

   All policy files have now been processed and the queue is clear. Policy generation is functioning as expected, with new policies being applied promptly after configuration. Verification confirms that policies are being delivered efficiently, and all policy translation tests are passing. We appreciate your patience while this issue was resolved.

Read the full incident report →

Started Jan 30, 2026, 11:41 PM UTC· resolved Jan 30, 2026, 11:45 PM UTC

1. investigating Jan 30, 2026, 11:41 PM UTC

   We are aware of an issue with the Umbrella App Discovery page impacting some customers in Central United States. Certain components of the page may not be loading as expected. Our team is actively investigating the problem and working to restore full functionality. Thank you for your patience and understanding

2. resolved Jan 30, 2026, 11:45 PM UTC

   This incident has been resolved. If you continue to experience any problems, please contact support.

Read the full incident report →

Started Jan 28, 2026, 12:38 AM UTC· resolved Jan 28, 2026, 01:38 AM UTC

1. investigating Jan 28, 2026, 12:38 AM UTC

   We are currently investigating a potential issue affecting tunnel service creation for customers connecting to the Minneapolis data center. Customers may experience disconnections or failures when establishing new tunnels or modifying PSKs. Our engineering team is actively working to confirm the impact, identify the root cause, and implement a resolution. Updates and additional details will be provided as more information becomes available.

2. investigating Jan 28, 2026, 12:39 AM UTC

   We are continuing to investigate this issue.

3. investigating Jan 28, 2026, 12:47 AM UTC

   We are continuing to investigate this issue.

4. resolved Jan 28, 2026, 01:38 AM UTC

   The issue has been identified and resolved as of 2026-01-28 01:17 UTC All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

Read the full incident report →

Started Jan 26, 2026, 08:45 AM UTC· resolved Jan 27, 2026, 08:04 AM UTC

1. identified Jan 26, 2026, 08:45 AM UTC

   We have performed mitigation actions to address the intermittent connectivity issues affecting customers connecting via the Copenhagen (CPH1.EDC) data center and are currently monitoring the situation for continued stability. Customers may still experience intermittent connectivity. For the best possible experience, we recommend connecting to the nearest available data center while we continue to address the situation. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

2. identified Jan 26, 2026, 08:52 AM UTC

   The Copenhagen (CPH1.EDC) data center has been taken Out of Rotation (OOR) as we continue to address and monitor intermittent connectivity issues. All customers are advised to connect to the nearest available data center for the best possible experience while our engineering team monitors the situation for stability. We will provide updates as more information becomes available and appreciate your patience during this time. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

3. identified Jan 26, 2026, 08:54 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Jan 26, 2026, 12:33 PM UTC

   The intermittent connectivity issues affecting the Copenhagen (CPH1.EDC) data center have been mitigated, and we are currently monitoring the site to ensure continued stability. At this time, customers should continue to use the nearest available data center for optimal performance. Once Copenhagen (CPH1.EDC) is ready to be brought back into rotation (BIR), we will provide further updates with all relevant details. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

5. resolved Jan 27, 2026, 08:04 AM UTC

   The issue affecting connectivity in Copenhagen (CPH1.EDC) has been resolved as of 07:50 UTC. The data center has now been brought back into rotation (BIR), and all services are up and running. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

Read the full incident report →

Started Jan 23, 2026, 10:37 PM UTC· resolved Jan 25, 2026, 12:32 PM UTC

1. investigating Jan 23, 2026, 10:37 PM UTC

   Customers connecting via Copenhagen (CPH1.EDC) may have experience intermittent connectivity issues. We recommend connecting to the nearest available data center for the best possible experience while we continue to address the situation. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your Cisco Secure Access experience.

2. resolved Jan 25, 2026, 12:32 PM UTC

   Traffic has been redirected to the nearest site.

Read the full incident report →

Started Jan 23, 2026, 12:26 PM UTC· resolved Jan 23, 2026, 09:22 PM UTC

1. investigating Jan 23, 2026, 12:26 PM UTC

   Tunnel Based Connectivity Degraded Customers connecting via Stockholm (STO1.EDC) may have experienced throughput decreased performance. However, all tunnels remain stable and connectivity is not interrupted. Our engineering team is actively working to confirm the impact, identify the root cause, and implement a resolution. We are committed to restoring full service as quickly as possible. Updates and additional details will be provided as new information becomes available. We appreciate your patience and understanding during this time.

2. investigating Jan 23, 2026, 01:08 PM UTC

   Tunnel-based Connectivity The Stockholm (STO1.EDC) data center has been taken Out of Rotation (OOR) due to node instability. All client connections have been automatically redirected to the alternate data centers. During the failover process, customers may have experienced brief connectivity interruptions. Our engineering team is actively working to restore full service and stability. Updates will be provided as soon as new information is available.

3. identified Jan 23, 2026, 04:26 PM UTC

   We have identified some irregularities in network traffic at our Stockholm (STO1.EDC) data center, which is contributing to the decreased performance previously reported. Our teams are closely monitoring the situation and investigating these findings as a possible cause. Remediation efforts are actively underway as our engineering and network teams continue to work towards a resolution. We will provide further updates as soon as more information becomes available. We appreciate your patience and understanding as we work to restore the service.

4. identified Jan 23, 2026, 06:33 PM UTC

   We are currently exploring multiple solutions to address the situation, and remediation efforts are actively underway as our teams work toward a resolution. We will provide further updates as soon as more information becomes available.

5. identified Jan 23, 2026, 08:26 PM UTC

   Efforts to resolve the current issue are ongoing. Our teams are working on all potential solutions to restore services. We are closely monitoring the situation and will keep you informed with any significant developments.

6. resolved Jan 23, 2026, 09:22 PM UTC

   The latency and performance issues previously affecting the Stockholm (STO1.EDC) data center have been resolved. All services are now operating normally, and latency has returned to expected levels. We apologize for any inconvenience this may have caused and appreciate your patience and understanding while we worked to restore full service. We’re Here to Help If you have any questions or need assistance, please contact our support team. Thank you for your understanding and support as we work to enhance your experience.

Read the full incident report →

Started Jan 15, 2026, 08:18 AM UTC· resolved Jan 15, 2026, 02:05 PM UTC

1. investigating Jan 15, 2026, 08:18 AM UTC

   We are currently investigating an issue affecting tunnel services at the Palo Alto Datacenter. To maintain service continuity, traffic has been redirected to our Los Angeles (LAX1) Data Center. We will provide periodic updates and share new information as it becomes available.

2. identified Jan 15, 2026, 10:58 AM UTC

   We have identified the cause of the issue affecting tunnel services at the Palo Alto Datacenter. Remediation efforts are underway, and service stability has improved. We are actively monitoring the situation and will provide a final update once the issue is fully resolved.

3. identified Jan 15, 2026, 11:48 AM UTC

   We are continuing to work on a fix for this issue.

4. investigating Jan 15, 2026, 02:04 PM UTC

   The issue affecting instabilities in Palo Alto has been resolved as of 13:35 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.

5. resolved Jan 15, 2026, 02:05 PM UTC

   The issue affecting instabilities in Palo Alto has been resolved as of 13:35 UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Jan 13, 2026, 08:01 PM UTC· resolved Jan 14, 2026, 02:17 AM UTC

1. investigating Jan 13, 2026, 08:01 PM UTC

   The Web Policy feature "Protect bypass" which is designed to allow encrypted files to bypass blocking, is currently not functioning as intended. Our engineering team is actively working to resolve this issue.

2. identified Jan 13, 2026, 08:47 PM UTC

   The engineering team has identified the issue and is currently performing a rollback to restore full functionality. The rollback process may take up to three hours to complete.

3. identified Jan 14, 2026, 12:51 AM UTC

   Rollback has been completed in all locations except for Singapore, which is still in progress.

4. resolved Jan 14, 2026, 02:17 AM UTC

   Rollback has been completed in Singapore, and all issues have been resolved.

Read the full incident report →

Started Jan 09, 2026, 10:02 AM UTC· resolved Jan 09, 2026, 11:12 AM UTC

1. investigating Jan 09, 2026, 10:02 AM UTC

   Tenant configuration not Loading on dashboard We are currently investigating an issue causing Tenant configuration missing from the dashboard. Customers will not be able to view configured tenants (new or existing) on the dashboard. However, the tenants are correctly configured on the backend and are functioning as expected. Updates will be provided as more information becomes available.

2. monitoring Jan 09, 2026, 10:15 AM UTC

   The issue has been identified and fixed by the ENG team. We are currently monitoring the situation and will provide updates as soon as they are available.

3. resolved Jan 09, 2026, 11:12 AM UTC

   The issue affecting Tenant configuration missing from the Dashboard has been resolved as of 10:02UTC. All services are now operating normally. We apologize for any inconvenience caused and thank you for your patience.

Read the full incident report →

Started Dec 30, 2025, 12:14 PM UTC· resolved Dec 30, 2025, 06:15 PM UTC

1. investigating Dec 30, 2025, 12:14 PM UTC

   We are currently experiencing a service performance issue affecting multiple data centers. You may notice an increased number of fail opens and timeouts, resulting in delays or failures when making requests. Our engineers are currently working to identify the root cause and implement a resolution. Updates will be provided as new information becomes available.

2. monitoring Dec 30, 2025, 01:26 PM UTC

   We identified issues and implemented a fix at 13:12 UTC. Subsequent internal checks indicate everything is working fine now. The team continues to monitor the situation closely.

3. monitoring Dec 30, 2025, 02:52 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Dec 30, 2025, 06:15 PM UTC

   This incident has been resolved.

Read the full incident report →