Volterra Outage History

Started Aug 21, 2026, 05:57 AM UTC· resolved Aug 21, 2026, 10:02 AM UTC

1. identified Aug 21, 2026, 05:57 AM UTC

   The F5 Distributed Cloud team has identified a performance degradation issue specific to the New York Regional Edge and is conducting urgent maintenance to address the problem. While there will be no traffic impact, customers may notice CE tunnels appearing as down. We are working diligently to resolve this matter promptly and will share further updates as soon as we have more information. Thank you for your patience and understanding during this time.

2. monitoring Aug 21, 2026, 07:21 AM UTC

   The F5 Distributed Cloud team has successfully completed the emergency maintenance to address the issue at the New York Regional Edge. We are now actively monitoring the environment to ensure ongoing stability. We appreciate your patience and will provide a final update once we confirm that full service stability is maintained.

3. resolved Aug 21, 2026, 10:02 AM UTC

   The F5 Distributed Cloud team has successfully resolved the issue of the New York Regional Edge. After thorough monitoring, we can confirm that no additional impact has been observed. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.

Read the full incident report →

Started Aug 14, 2026, 04:31 PM UTC· resolved Aug 14, 2026, 07:03 PM UTC

1. investigating Aug 14, 2026, 04:31 PM UTC

   We are currently investigating a service degradation in the Paris (PA4) region that began around 14th Aug at 14:50 UTC. Engineering teams have observed an increase in 5xx responses and are actively investigating the underlying cause. We are continuing to monitor the situation closely and will provide further updates as more information becomes available.

2. resolved Aug 14, 2026, 07:03 PM UTC

   The F5 Distributed Cloud team can confirm that the issue affecting the Paris (PA4) Regional Edge and the Global Log Receiver (GLR) service has been fully resolved. We sincerely appreciate your patience and understanding throughout this event. All services are now operating as expected.

Read the full incident report →

Started Aug 04, 2026, 04:24 PM UTC· resolved Aug 05, 2026, 03:47 AM UTC

1. investigating Aug 04, 2026, 04:24 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting DNS propagation. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at [Insert Reported Time, e.g., 04:17 PM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Aug 04, 2026, 05:02 PM UTC

   F5 Distributed Cloud is currently investigating an issue affecting the DNS propagation. Our engineering teams are actively investigating the root cause and working toward a resolution. Please note that other Distributed Cloud services are not affected. We will provide additional updates as soon as more information becomes available.

3. identified Aug 04, 2026, 07:11 PM UTC

   The issue affecting DNS propagation has been identified and our teams are working on the lag resolution. Thank you for your patience while we work to resolve this issue. If you have any questions or concerns, please feel free to reach out to our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding and cooperation as we continue to improve our services.

4. monitoring Aug 04, 2026, 08:25 PM UTC

   The issue that caused the DNS propagation lag has been resolved, and services are operating normally. Our teams have confirmed system stability, and we will continue to closely monitor DNS to ensure ongoing stability and consistent performance. If you have any questions or need assistance, please contact our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding as we continue working to improve our services.

5. resolved Aug 05, 2026, 03:47 AM UTC

   We're pleased to confirm the issue affecting the DNS service has been resolved, and the service is now operating normally. Our engineering teams have addressed the underlying issue and have verified system stability. We'll continue to keep a close watch on DNS performance to ensure everything remains stable and consistent. If you have any questions or need assistance, please contact our Support team: - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 Thank you for your patience and understanding. Sincerely, F5 Distributed Cloud

Read the full incident report →

Started Aug 03, 2026, 04:45 PM UTC· resolved Aug 04, 2026, 04:42 AM UTC

1. investigating Aug 03, 2026, 04:45 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting GLR logs latency. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 04:38 PM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. monitoring Aug 03, 2026, 05:37 PM UTC

   The F5 Distributed Cloud has identified a degradation affecting Global Log Receiver (GLR). by now service has been restored and our engineering teams are actively monitoring to ensure continued platform stability. We will provide additional updates as more information becomes available. Please note that there is no traffic interruption and all core Distributed Cloud Console services remain fully operational. We appreciate your patience and understanding.

3. resolved Aug 04, 2026, 04:42 AM UTC

   We are glad to confirm that the previously observed service degradation affecting Global Log Receiver (GLR) has been resolved, and GLR is operating normally. Following service restoration, our engineering teams have continued to monitor the platform to ensure sustained stability, and no further issues have been detected. There was no traffic interruption, and all core F5 Distributed Cloud Console services remained fully operational throughout the event. This incident is now considered closed. Thank you for your patience and understanding. Sincerely, F5 Distributed Cloud

Read the full incident report →

Started Jul 30, 2026, 12:44 PM UTC· resolved Jul 31, 2026, 02:42 AM UTC

1. investigating Jul 30, 2026, 12:44 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting GLR (Global Log Relay) and access logs within the Distributed Cloud environment. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 12:38 PM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. identified Jul 30, 2026, 01:26 PM UTC

   The F5 Distributed Cloud Support Team has identified a delay in access logs appearing in the Distributed Cloud Console UI. Global Log Receiver (GLR) functionality remains at its usual operating levels. All XC Console core services continue to function as expected without disruption. Our engineering team is actively investigating the access log delay to ensure prompt resolution. Updates will be shared as soon as we have more information. Thank you for your patience and understanding.

3. monitoring Jul 30, 2026, 03:31 PM UTC

   The F5 Distributed Cloud Team has resolved an issue that was causing a delay in access logs appearing in the Distributed Cloud Console UI. The system is now fully operational, and we will continue to monitor it closely to ensure stability. Thank you for your patience and understanding during this time.

4. resolved Jul 31, 2026, 02:42 AM UTC

   The F5 Distributed Cloud Team has resolved the issue causing delays in access logs appearing in the Distributed Cloud Console UI. The system is fully operational, and access logs have remained stable without further lag. Thank you for your patience and understanding during this time.

Read the full incident report →

Started Jul 29, 2026, 08:48 AM UTC· resolved Jul 30, 2026, 05:09 AM UTC

1. investigating Jul 29, 2026, 08:48 AM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting Mumbai regional edge. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 08:40 AM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Jul 29, 2026, 09:44 AM UTC

   The F5 Distributed Cloud team has identified a performance degradation issue isolated to Mumbai Regional Edge and is actively investigating the issue. We are committed to resolving this with urgency to minimize the impact on our customer services. We will provide further updates as more information becomes available. We appreciate your patience and understanding

3. monitoring Jul 29, 2026, 10:32 AM UTC

   The F5 Distributed Cloud team has identified and corrected the configuration propagation issue at the Mumbai (MB2) Regional Edge. The propagation issue has been resolved, and no further customer impact is expected. We are currently monitoring the environment to ensure continued stability. We appreciate your patience and will provide a final update once we confirm that full service stability is maintained.

4. resolved Jul 30, 2026, 05:09 AM UTC

   The F5 Distributed Cloud team had successfully resolved the issue affecting the connectivity in Mumbai Regional Edge (MB2), and after an extensive period of monitoring, we can confirm that no further impact was observed. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.

Read the full incident report →

Started Jul 27, 2026, 09:02 AM UTC· resolved Jul 28, 2026, 05:29 AM UTC

1. investigating Jul 27, 2026, 09:02 AM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting CDN services in Dallas (DAL3). We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 09:00 UTC. • Our incident response team has been fully mobilized. • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Jul 27, 2026, 09:30 AM UTC

   The F5 Distributed Cloud team has identified an issue with the CDN Edge in Dallas (DAL3) and is working diligently on corrective measures to restore full functionality. Please note that there might be an increase in latency faced by customers as traffic will get automatically routed towards the nearest edge location. We appreciate your patience and understanding as we work on resolving this matter. Our teams continue to proactively monitor the situation and will share updates as soon as they become available. If you have any further concerns, please do not hesitate to reach out to us via your established support channels.

3. monitoring Jul 27, 2026, 01:49 PM UTC

   The F5 Distributed Cloud team is pleased to inform you that a fix has been implemented and the issue has been resolved. The CDN edge in Dallas (DAL3) has been enabled back for customer traffic. We will continue to proactively monitor the situation to ensure the stability of our services. Should you encounter any issue, please do not hesitate to reach out to us via your established channels.

4. resolved Jul 28, 2026, 05:29 AM UTC

   The F5 Distributed Cloud team had successfully resolved the issue affecting CDN edge connectivity in Dallas (DAL3), and after an extensive period of monitoring, we can confirm that no further impact was observed. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.

Read the full incident report →

Started Jul 24, 2026, 12:05 PM UTC· resolved Jul 24, 2026, 01:49 PM UTC

1. investigating Jul 24, 2026, 12:05 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation which affected Bot Defense services in multiple regions. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 07/24/2026, 10:55 UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided once we have more information; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. resolved Jul 24, 2026, 01:49 PM UTC

   Between 2026-07-24 10:55 UTC and 11:15 UTC, a service degradation was observed due to an External Cloud Provider issue. This possibly affected communication between F5 services and customer origins, resulting in increased 5xx errors and higher origin latency. The issue was confirmed to be related to the Cloud Provider and not F5 Distributed Cloud infrastructure. The issue has been fully resolved, and services are operating normally. If you continue to experience any issues, please reach out to our support team through your established channels. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Started Jul 16, 2026, 06:22 AM UTC· resolved Jul 17, 2026, 11:04 PM UTC

1. investigating Jul 16, 2026, 06:22 AM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting routed DDOS tile is not accessible. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 06;14 UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Jul 16, 2026, 08:28 AM UTC

   The F5 Distributed Cloud team has identified an accessibility issue that some customers have experienced with the "Routed DDoS" tile in the Distributed Cloud Console. Our teams are working diligently on corrective measures to restore full accessibility. Please be rest assured that this issue does not impact the functionality of the Routed DDoS service itself— operations and protections associated with the service remain fully intact. We appreciate your patience and understanding as we work on resolving this matter. Our teams continue to proactively monitor the situation and will share updates as soon as they become available. If you have any further concerns, please do not hesitate to reach out to us via your established support channels.

3. monitoring Jul 16, 2026, 12:13 PM UTC

   The F5 Distributed Cloud team has addressed the previously identified accessibility issue related to the "Routed DDoS" tile in the Distributed Cloud Console. Our teams are closely monitoring the situation to ensure stability. We would like to reassure our customers that there has been no traffic impact, and the functionality of the Routed DDoS service remains unaffected. All operations and protections associated with the service continue to function normally. For any additional concerns or questions, please do not hesitate to reach out to us via your established support channels.

4. monitoring Jul 17, 2026, 12:27 AM UTC

   The F5 Distributed Cloud team has resolved the previously identified accessibility issue affecting the Routed DDoS functions in the XC Console. The XC Console Routed DDoS functions have been fully restored, and the issue is now under monitoring. Core Routed DDoS services remain operational, and there has been no impact to traffic processing or protection capabilities throughout the incident. Our teams will continue monitoring the environment to ensure continued stability before closing the incident.

5. resolved Jul 17, 2026, 11:04 PM UTC

   The F5 Distributed Cloud team has successfully resolved the issue affecting the Routed DDoS functions in the XC Console and no further impact is expected. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.

Read the full incident report →

Started Jul 15, 2026, 11:43 AM UTC· resolved Jul 15, 2026, 03:26 PM UTC

1. investigating Jul 15, 2026, 11:43 AM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting support ticket creation in the Distributed Cloud console. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 11:35 AM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. monitoring Jul 15, 2026, 12:43 PM UTC

   The F5 Distributed Cloud team is pleased to inform you that the issue preventing customers from submitting support tickets through the Distributed Cloud Console has been resolved. The console is now fully operational for ticket submissions. We will continue to proactively monitor the situation to ensure the stability of our services. Should you encounter any further issues or have any concerns, please do not hesitate to reach out to us via your established channels.

3. resolved Jul 15, 2026, 03:26 PM UTC

   The issue affecting support ticket creation in Distributed Cloud Console has been fully resolved, and all services are operating normally. Our teams have validated system stability and will continue to monitor to ensure consistent performance. Thank you for your patience while we worked to resolve this issue. If you have any questions or concerns, please feel free to reach out to our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding and cooperation as we continue to improve our services. Sincerely, F5 Distributed Cloud

Read the full incident report →

Started Jul 08, 2026, 09:48 PM UTC· resolved Jul 09, 2026, 05:00 AM UTC

1. investigating Jul 08, 2026, 09:48 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting metrics missing on the Distributed Cloud dashboards. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 9:40 PM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Jul 08, 2026, 10:17 PM UTC

   The F5 Distributed Cloud support team has identified an issue affecting the display of metrics within the customer dashboard and CE´s showing as down. This is a visual-only anomaly and does not impact traffic processing, core functionalities, or data log generation. Our team is actively working to resolve the issue at the earliest. We will keep you informed with updates as progress is made. Thank you for your understanding and patience as we work to address this issue.

3. monitoring Jul 08, 2026, 11:57 PM UTC

   The F5 Distributed Cloud support team has applied the fix and the display of metrics within the customer dashboard and CE´s are recovering. We will keep you informed as updates become available. Thank you for your understanding and patience as we work to address this issue.

4. resolved Jul 09, 2026, 05:00 AM UTC

   The F5 Distributed Cloud team has successfully resolved the issue affecting display of metrics within the customer dashboard and CE´s, and no further impact is expected. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.

Read the full incident report →

Started Jul 06, 2026, 03:09 PM UTC· resolved Jul 10, 2026, 12:48 AM UTC

1. investigating Jul 06, 2026, 03:09 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting DNS. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 07/06/2026, 15:03 UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Jul 06, 2026, 04:20 PM UTC

   F5 Distributed Cloud is currently investigating an issue affecting the DNS visualization status. We have confirmed that this is a cosmetic display issue only and that there is no impact to production traffic or DNS functionality. DNS propagation is working as expected, and the requested changes have been successfully propagated. However, the visualization currently continues to display the status as "In Progress", despite the propagation having completed successfully. Our engineering teams are actively investigating the root cause and working toward a resolution. We will provide additional updates as soon as more information becomes available.

3. monitoring Jul 06, 2026, 06:21 PM UTC

   The issue affecting DNS visualization status delay, has been identified and resolved, and all services are operating normally. Our teams have validated system stability and will continue to monitor to ensure consistent performance. Thank you for your patience while we worked to resolve this issue. If you have any questions or concerns, please feel free to reach out to our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding and cooperation as we continue to improve our services. Sincerely, F5 Distributed Cloud

4. monitoring Jul 07, 2026, 04:12 AM UTC

   The issue that caused a delay in DNS visualization status updates has been resolved, and services are operating normally. Our teams have confirmed system stability, and we will continue to closely monitor DNS to ensure ongoing stability and consistent performance. Thank you for your patience while we worked to restore normal operation. If you have any questions or need assistance, please contact our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding as we continue working to improve our services. Sincerely, F5 Distributed Cloud

5. monitoring Jul 07, 2026, 12:49 PM UTC

   The issue affecting the DNS visualisation status has been resolved, and services are operating normally. Our teams have confirmed system stability, and we will continue to closely monitor DNS to ensure reliability and consistent performance. Thank you for your patience while we worked to restore normal operation. If you have any questions or need assistance, please contact our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding as we continue working to improve our services. Sincerely, F5 Distributed Cloud

6. monitoring Jul 08, 2026, 02:10 AM UTC

   The issue that caused delays in DNS visualization status updates has been resolved, and DNS services are operating normally. Our teams have verified stability and will continue monitoring DNS closely to ensure ongoing reliability and consistent performance. Thank you for your patience while we worked to restore normal service. If you have any questions or need assistance, please contact our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding as we continue to improve our services. Sincerely, F5 Distributed Cloud

7. monitoring Jul 08, 2026, 02:05 PM UTC

   The issue affecting the DNS visualisation status has been resolved, and services are operating normally. Our teams have confirmed system stability, and we will continue to closely monitor DNS to ensure reliability and consistent performance. Thank you for your patience while we worked to restore normal operation. If you have any questions or need assistance, please contact our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding as we continue working to improve our services. Sincerely, F5 Distributed Cloud

8. monitoring Jul 09, 2026, 02:20 PM UTC

   The issue affecting DNS visualization status has been resolved, and all services are now operating normally. Our teams have verified that the system is stable and will continue to monitor DNS services to ensure reliable and consistent performance. We appreciate your patience and understanding throughout this period. If you have any questions or require further assistance, please feel free to contact our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding as we continue working to improve our services. Sincerely, F5 Distributed Cloud

9. resolved Jul 10, 2026, 12:48 AM UTC

   The issue affecting DNS visualization status has been fully resolved, and all services are operating normally. Our teams have validated system stability and will continue to monitor to ensure consistent performance. Thank you for your patience while we worked to resolve this issue. If you have any questions or concerns, please feel free to reach out to our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding and cooperation as we continue to improve our services. Sincerely, F5 Distributed Cloud

Read the full incident report →

Started Jul 01, 2026, 09:03 PM UTC· resolved Jul 02, 2026, 01:03 PM UTC

1. investigating Jul 01, 2026, 09:03 PM UTC

   The F5 Distributed Cloud is currently investigating a degradation affecting Global Log Receiver (GLR) in the EU region. Our engineering teams are actively working to identify the root cause. We are closely monitoring the environment to ensure continued platform stability and will provide additional updates as more information becomes available. Please note that there is no traffic interruption and all core Distributed Cloud Console services remain fully operational. We will share further updates as more information becomes available. We appreciate your patience and understanding.

2. monitoring Jul 01, 2026, 10:58 PM UTC

   The issue has been identified and EU GLR log processing lag has been restored to normal levels. Our engineering teams are continuing to monitor closely to ensure the service returns to and remains at normal operating levels. We will provide additional updates as needed

3. monitoring Jul 02, 2026, 10:07 AM UTC

   The F5 Distributed Cloud team has identified and mitigated the issue that was impacting Global Logs Receiver. Please note that all other Distributed Cloud Console services remain fully operational We will continue to monitor the platform to ensure ongoing service stability. If you have any questions or concerns, please contact us at [email protected].

4. resolved Jul 02, 2026, 01:03 PM UTC

   The F5 Distributed Cloud team has successfully resolved the issue affecting GLR log streaming in the Distributed Cloud console. Live log visibility has now been restored. The system is currently operating normally, and no further impact is expected. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.

Read the full incident report →

Started Jun 26, 2026, 11:58 AM UTC· resolved Jun 26, 2026, 05:14 PM UTC

1. investigating Jun 26, 2026, 11:58 AM UTC

   This advisory is to inform you that we are currently investigating reports of latency and intermittent timeouts with specific service provider. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 11:50 AM UTC • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Jun 26, 2026, 01:10 PM UTC

   F5 has received reports from customers in the India region about connectivity issues, including increased latency and request timeouts when accessing applications.We are actively monitoring the situation and will continue to provide updates as and when additional information becomes available.

3. resolved Jun 26, 2026, 05:14 PM UTC

   We would like to provide an update on the previously reported connectivity issues affecting customers in the India region. The issue has now been resolved, and services have returned to normal operation. The disruption was caused by an external network fiber cut impacting connectivity between Singapore and India. We will continue to closely monitor the environment to ensure continued service stability. Thank you for your patience and understanding.

4. postmortem Jun 26, 2026, 07:54 PM UTC

   ## **Root Cause Statement** The incident was caused by a **fiber cut on a major regional ISP’s network \(Airtel\) between Indonesia and India.** This disruption led to **widespread congestion throughout the region, and across multiple networks with dependencies on Airtel. F5’s network and infrastructure remained fully operational throughout the event and did not experience any outage or service degradation.** As a result of the fiber cut, **some Internet traffic to/from India and nearby regions was degraded, leading to increased latency, intermittent timeouts/packet loss, and slowness.** **Mitigation: Upon detection of the event, F5 implemented traffic engineering measures within the F5 Distributed Cloud backbone to re-route our traffic away from the fault in Airtel’s network,** deliberately avoiding the impacted network segment, reducing our exposure to the provider’s outage, and improving overall service performance for our customers.

Read the full incident report →

Started Jun 24, 2026, 06:10 PM UTC· resolved Jun 27, 2026, 05:10 PM UTC

1. identified Jun 24, 2026, 06:10 PM UTC

   We are currently monitoring an incident affecting one of our service providers. We have implemented mitigations to reduce or prevent customer impact; however, if conditions worsen, customers may experience a loss of Global Log Receiver (GLR) services. Our teams are actively engaged and will continue to monitor closely. We will provide additional updates as needed. Thank you for your understanding.

2. identified Jun 24, 2026, 06:49 PM UTC

   We have confirmed the situation has worsened at our service provider, and as a result GLR services are currently unavailable. We are working closely with the provider to restore service as quickly as possible, while also exploring additional mitigation options to minimize impact to your services.We will provide additional updates as needed. Thank you for your patience and understanding.

3. identified Jun 24, 2026, 07:21 PM UTC

   We would like to provide an update regarding current service conditions. Due to an ongoing heatwave in Europe, our service provider’s data center is experiencing cooling constraints. This has led to capacity limitations at the affected site. While traffic has successfully rerouted to the nearest Regional Edge, certain services and features are currently impacted. At this time, the following services and features may be impacted: - GLR services in Europe – currently unable to send logs to customer environments, all other regions are online - Firewall deployments – may experience delays in provisioning - Tunnel provisioning – may experience delays - Route advertisements to F5 Distributed Cloud requiring RPKI validation – may be delayed until RPKI services are fully restored We have confirmed the situation at the provider has worsened, and we are working closely with them to stabilize conditions and restore full operational capacity as quickly as possible. In parallel, we are evaluating additional mitigation options to further reduce any impact. We will continue to share updates as new information becomes available. Thank you for your patience and understanding

4. identified Jun 24, 2026, 09:28 PM UTC

   We would like to provide an update regarding current service conditions. We remain actively engaged with our service provider and are continuing mitigation efforts to address service stability across all affected services. While some services may still experience delays, we are working diligently to minimize impact and ensure consistent operation. We will continue to share updates as new information becomes available. Thank you for your patience and understanding as we work to restore full services.

5. identified Jun 24, 2026, 11:56 PM UTC

   We would like to share a further update regarding current service conditions. We remain actively engaged with our service provider and continue to monitor the situation closely while progressing mitigation efforts to support stability across the affected services. Some services may still experience delays, and we are working to minimize impact and restore consistent operation as quickly as possible. We will provide additional updates as more information becomes available. Thank you for your continued patience and understanding as we work to restore full services.

6. identified Jun 25, 2026, 02:08 AM UTC

   We would like to provide another update regarding current service conditions. We remain actively engaged with our service provider and are continuing to monitor the situation closely while advancing mitigation efforts to improve stability across the affected services. Some services may still experience delays, and we are working to reduce impact and return to consistent operation as quickly as possible. We will share further updates as additional information becomes available. Thank you for your continued patience and understanding as we work to restore full services.

7. identified Jun 25, 2026, 06:26 AM UTC

   We would like to provide an update regarding the current service conditions. We continue to actively collaborate with our service provider and are closely monitoring the situation while advancing mitigation efforts to stabilize the affected services. While some services may still experience delays, we are working diligently to minimize the impact and restore consistent operations as quickly as possible. Further updates will be shared as more information becomes available. Thank you for your patience and understanding.

8. identified Jun 25, 2026, 10:44 AM UTC

   We would like to provide a further update regarding the ongoing service conditions. Mitigation and recovery efforts are progressing, and we continue to actively monitor the environment to ensure service stability. Services continue to operate as usual, but there may be delays in the delivery of access logs. We will continue to provide updates as more information becomes available. Thank you for your patience and understanding.

9. identified Jun 25, 2026, 02:54 PM UTC

   We would like to provide a further update regarding the ongoing service conditions. Recovery efforts continue to make steady progress, and we remain actively engaged in restoring the affected services while closely monitoring overall service stability. Services continue to operate as usual; however, customers may experience delays in the delivery of access logs and GLR data while recovery activities remain underway. We will continue to provide updates as more information becomes available. Thank you for your continued patience and understanding.

10. identified Jun 25, 2026, 06:59 PM UTC

    We would like to provide an additional update regarding the current service conditions. Recovery activities continue to advance steadily, and our teams remain fully engaged in restoring the affected services while closely monitoring overall platform stability. While services are largely operating as expected, some customers may continue to experience delays in the availability of access logs and GLR data as recovery efforts progress. We will share further updates as additional information becomes available. We appreciate your continued patience and understanding.

11. identified Jun 25, 2026, 09:44 PM UTC

    We would like to share a further update on the current service situation. Progress on recovery remains ongoing, and our teams continue to work diligently to restore all impacted services while maintaining close oversight of overall system health. At this time, we are still within the recovery phase as these activities proceed. Although the majority of services are functioning normally, some customers may continue to encounter delays in the processing and availability of access logs and GLR data during this period. We will continue to provide additional updates as more details become available. We sincerely appreciate your patience and understanding.

12. identified Jun 26, 2026, 02:22 AM UTC

    We would like to provide an additional update regarding the current service conditions. Progress on recovery remains ongoing, and our teams continue to work diligently to restore all impacted services while maintaining close oversight of overall system health. At this time, we are still within the recovery phase as these activities proceed. Although the majority of services are functioning normally, some customers may continue to encounter delays in the processing and availability of access logs and GLR data during this period. We will continue to provide additional updates as more details become available. We sincerely appreciate your patience and understanding.

13. identified Jun 26, 2026, 06:28 AM UTC

    We would like to share a further update on the current service situation. Recovery efforts continue to progress, and our teams remain fully engaged in restoring complete service stability while maintaining close oversight of overall system health. We are pleased to report continued improvements across the platform. In addition, the previously observed access log lag has now been fully resolved. While overall system performance has improved, GLR is still experiencing some residual processing lag, which our teams are actively working to remediate. We will continue to closely monitor the situation and share further updates as additional progress is made. We sincerely appreciate your continued patience and understanding.

14. identified Jun 26, 2026, 10:33 AM UTC

    We would like to provide a further update on the current service situation. Recovery efforts have continued to progress, and we are pleased to report that platform services are now operating within expected parameters. Access logs and GLR processing have now returned to normal operating levels. Our teams remain actively engaged in monitoring the environment to ensure continued service stability and will continue to closely observe the platform as recovery activities progress. We sincerely appreciate your continued patience, understanding, and support throughout this event.

15. identified Jun 26, 2026, 02:27 PM UTC

    We would like to provide a further update on the current service situation. The overall service status remains unchanged. Platform services continue to operate within expected parameters, with access logs and GLR processing remaining at normal operating levels. Our teams remain actively engaged in monitoring the environment to ensure continued service stability and will maintain close observation of the platform as recovery activities continue. We sincerely appreciate your continued patience, understanding, and support throughout this event.

16. monitoring Jun 26, 2026, 07:08 PM UTC

    We would like to provide a further update on the current service situation. All services have fully recovered and are operating normally. Access logs and GLR processing have returned to expected levels across the platform. There is no ongoing impact to customers, and the platform remains stable. Our teams will continue to closely monitor the environment to ensure ongoing stability. Thank you for your patience, understanding, and support throughout this event.

17. monitoring Jun 27, 2026, 06:55 AM UTC

    We would like to provide a further update on the current service situation. All services have fully recovered and are operating normally. Platform stability has been restored, and access logs along with GLR processing are back to expected levels.There is no ongoing impact to customers. Our teams will continue monitoring the environment closely to ensure continuous stability. Thank you for your patience and support throughout this event.

18. resolved Jun 27, 2026, 05:10 PM UTC

    We are pleased to confirm that the issue has been fully resolved. All affected services have been restored and are operating normally, with no ongoing customer impact. Platform functionality has returned to expected operating levels, and this incident is now considered closed. We appreciate your patience and support throughout this incident.

Read the full incident report →

Started Jun 23, 2026, 11:29 AM UTC· resolved Jun 24, 2026, 12:15 AM UTC

1. investigating Jun 23, 2026, 11:29 AM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting one or more services. We will provide more details as they become available. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 11:25 AM UTC. • Our incident response team has been fully mobilized. • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Jun 23, 2026, 12:09 PM UTC

   The F5 Distributed Cloud support team has identified an issue where customers might experience delays in config propagation when creating a new endpoint or modifying an existing one. Please note that all other services remain fully operational and existing configurations are not impacted. Our teams are actively investigating the issue and we will share further updates as more information becomes available. Thank you for your patience and understanding.

3. investigating Jun 23, 2026, 02:02 PM UTC

   Our engineering teams remain actively engaged in investigating the issue. Please note that all other services remain fully operational and existing configurations are not impacted. We will continue to provide updates as recovery efforts progress and more information becomes available. We appreciate your patience and understanding.

4. investigating Jun 23, 2026, 07:13 PM UTC

   Our engineering teams remain actively engaged in investigating the issue impacting the ability to perform changes in XC components and dashboard loading. Please note that all other services remain fully operational and existing configurations are not impacted. We will continue to provide updates as recovery efforts progress and more information becomes available. We appreciate your patience and understanding.

5. monitoring Jun 23, 2026, 08:51 PM UTC

   Our engineering teams have recovered the ability to perform changes in XC components and dashboard loading. Services are now operational and our engineering teams are closely monitoring the environment to ensure ongoing stability. We appreciate your understanding and will continue to provide additional updates as needed.

6. resolved Jun 24, 2026, 12:15 AM UTC

   Following a period of post-restoration monitoring, we have confirmed the issue impacting the ability to perform changes in Distributed Cloud components and Customer Dashboard loading has been resolved. Customers should now be able to create and modify endpoint configurations normally, and dashboards should load as expected. Services are fully operational. Thank you for your patience and understanding throughout this incident.

Read the full incident report →

Started Jun 17, 2026, 06:36 PM UTC· resolved Jun 17, 2026, 07:18 PM UTC

1. investigating Jun 17, 2026, 06:36 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting one or more services in Paris. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 06/17/2026, 18:34 UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

Read the full incident report →

Started Jun 16, 2026, 09:36 AM UTC· resolved Jun 17, 2026, 11:04 AM UTC

1. investigating Jun 16, 2026, 09:36 AM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting F5 CDN distribution. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 09:35 AM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating Jun 16, 2026, 10:06 AM UTC

   F5 Distributed Cloud team is aware of an issue causing both existing and newly created CDN distributions to become stuck in a pending state. Existing CDN services remain operational, and traffic processing is not impacted. Our engineering teams are actively investigating the issue and working to restore normal functionality as quickly as possible. We will provide further updates as additional information becomes available. Thank you for your patience and understanding.

3. investigating Jun 16, 2026, 11:47 AM UTC

   Our engineering teams are actively engaged and continue to work toward identifying the potential cause and implementing a resolution. Existing CDN services remain operational, and traffic processing is not impacted. We will continue to provide regular updates as our investigation progresses.

4. investigating Jun 16, 2026, 01:40 PM UTC

   Our engineering teams remain actively engaged in investigating the issue affecting CDN distributions that are becoming stuck in a pending state. At this time, there are no changes to the scope or impact of the issue. Existing CDN services continue to operate normally, and traffic processing remains unaffected. The team is continuing its analysis and working toward identifying the cause and implementing a resolution. We appreciate your continued patience and will provide further updates as additional information becomes available.

5. investigating Jun 16, 2026, 01:59 PM UTC

   As part of our ongoing efforts to resolve the issue affecting CDN distributions that are becoming stuck in a pending state, our engineering teams will be performing a restart of the CDN service, existing and newly created CDN distributions to become stuck in a pending state during this period and expected failures of Dashboard population and Purge config operation services. Traffic processing is not expected to be impacted. We are closely monitoring the environment throughout the maintenance and will provide further updates on the outcome of these actions. Thank you for your continued patience and understanding.

6. identified Jun 16, 2026, 04:18 PM UTC

   The F5 CDN Dashboard and Purge services have been successfully restored and are functioning normally. Restoration activities for CDN distribution provisioning remain in progress, and our engineering teams continue to actively monitor the environment to ensure service stability. Existing CDN services remain operational, and traffic processing continues to be unaffected. We will provide further updates as restoration efforts continue.

7. monitoring Jun 16, 2026, 06:22 PM UTC

   The F5 CDN issue for existing and newly created CDN distributions has been restored, and the CDN Services are now operating normally. Our engineering teams have completed recovery activities and are actively monitoring the environment to ensure continued stability. Existing CDN services and traffic processing remain fully operational. We will continue to monitor the situation closely and provide further updates as necessary.

8. monitoring Jun 17, 2026, 12:45 AM UTC

   The F5 CDN service has been fully restored, and traffic processing remains operational. Our engineering teams are actively monitoring the environment to ensure continued stability. We appreciate your patience and will share further updates as necessary.

9. monitoring Jun 17, 2026, 07:28 AM UTC

   The F5 CDN service remains stable and operational, and traffic processing continues to function as expected. Our engineering teams are closely monitoring the environment to ensure ongoing stability. We appreciate your understanding and will provide additional updates as needed.

10. resolved Jun 17, 2026, 11:04 AM UTC

    Our engineering teams have restored full functionality for CDN Distributions, the CDN Dashboard and Purge Services. Traffic is flowing normally and this incident has now been resolved. If you are still experiencing any issues please do not hesitate to contact F5 Support.

Read the full incident report →

Started Jun 09, 2026, 11:52 AM UTC· resolved Jun 10, 2026, 07:20 PM UTC

1. identified Jun 09, 2026, 11:52 AM UTC

   F5 Distributed Cloud customers may experience a delay in GLR log streaming. Our teams are actively investigating the Global Log Receiver functionality. Please note that there is no traffic interruption and all core XC Console services remain fully operational. We will share further updates as more information becomes available. We appreciate your patience and understanding.

2. identified Jun 09, 2026, 04:01 PM UTC

   F5 Distributed Cloud customers may experience a delay in GLR log streaming. Our teams have identified the issue and are actively working to recover the service and restore normal log delivery as soon as possible. Please note that there is no traffic interruption, and all core XC Console services remain fully operational. We will continue to provide updates as recovery efforts progress and more information becomes available. We appreciate your patience and understanding.

3. monitoring Jun 10, 2026, 07:15 AM UTC

   The F5 Distributed Cloud team has confirmed that Global Log Receiver processing has fully recovered and returned to normal operations. Both live logs and backfill logs are now being generated and accessible within the XC Console. This ensures users can effectively access and audit activities as needed. As previously communicated, all XC Console core services remained fully functional throughout the duration of this event. This maintained the reliability and integrity of the platform in a steady state. To further reinforce stability, proactive monitoring will continue to ensure Global Log Receiver services operate as usual. If any issues arise, users are encouraged to contact the F5 support team for assistance. We sincerely appreciate your continued trust in F5.

4. resolved Jun 10, 2026, 07:20 PM UTC

   The issue affecting the F5 Distributed Cloud Global Log Receiver has been resolved. All XC Console core services remains fully operational, and the incident is now closed. Please contact support if you continue to experience any issues.

Read the full incident report →

Started Jun 08, 2026, 02:58 PM UTC· resolved Jun 09, 2026, 03:07 AM UTC

1. investigating Jun 08, 2026, 02:58 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting Global Logs Receiver (GLR). We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 2:52 PM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. monitoring Jun 08, 2026, 09:09 PM UTC

   The F5 Distributed Cloud team is actively working to resolve the issue. The GLR log processing is recovering. There is no traffic impact and all core XC Console services remain fully operational. We will share further updates as they become available. Thank you for your patience and understanding.

3. resolved Jun 09, 2026, 03:07 AM UTC

   The issue affecting the F5 Distributed Cloud GLR (Global Logs Receiver) has been resolved. The service remains fully operational, and the incident is now closed. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.

Read the full incident report →

Started Jun 06, 2026, 09:20 PM UTC· resolved Jun 07, 2026, 06:01 PM UTC

1. monitoring Jun 06, 2026, 09:20 PM UTC

   Following a scheduled maintenance window on June 6th 2026 at 14:00 UTC, we identified a performance degradation caused by false positives in rate-limiting policies. Our teams were immediately engaged, and corrective actions were taken to resolve the issue. The incident was resolved at 18:00 UTC and all systems are now operating normally. We sincerely apologize for any inconvenience caused and appreciate your patience as we worked to resolve the issue.

2. resolved Jun 07, 2026, 06:01 PM UTC

   The F5 Distributed Cloud team has successfully resolved the issue that was causing the false positives in rate-limiting policies. Services are now functioning as expected, and we will continue to monitor to ensure ongoing stability. If you have any questions or continue to experience issues, please reach out to our support team through your established channels. This incident is now considered resolved. We appreciate your patience and understanding while we worked to restore service.

Read the full incident report →

Started May 26, 2026, 01:56 PM UTC· resolved May 26, 2026, 02:35 PM UTC

1. investigating May 26, 2026, 01:56 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting GLR logs. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 01:49 PM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. resolved May 26, 2026, 02:35 PM UTC

   The F5 Distributed Cloud team has successfully resolved the issue affecting GLR log streaming. The system is currently operating normally, and no further impact is expected. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don’t hesitate to reach out to our support team.

Read the full incident report →

Started May 24, 2026, 08:09 PM UTC· resolved May 25, 2026, 12:55 AM UTC

1. investigating May 24, 2026, 08:09 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting the synthetic monitoring. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 20:00 UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating May 24, 2026, 08:15 PM UTC

   We are continuing to investigate this issue.

3. identified May 24, 2026, 09:03 PM UTC

   The issue has been identified and a fix is being implemented.

4. identified May 24, 2026, 09:33 PM UTC

   The F5 Distributed Cloud team had identified a service degradation on the synthetic monitoring. Our teams are actively working on the recovery. Please note that all core XC Console services remain fully operational. We will share further updates as more information becomes available. If you're experiencing any service degradation, please contact our support team. We appreciate your patience and understanding.

5. monitoring May 24, 2026, 10:45 PM UTC

   The F5 Distributed Cloud team has recovered the issue that was affecting the Synthetic Monitoring. Services are now functioning as expected and under monitoring. If you have any questions or concerns, please feel free to reach out to our support team.

6. resolved May 25, 2026, 12:55 AM UTC

   The F5 Distributed Cloud team has successfully resolved the issue that was causing Synthetic Monitoring service degradation. Services are now functioning as expected, and we will continue to monitor to ensure ongoing stability. Please note that all core XC Console services remained fully operational throughout the incident. If you have any questions or continue to experience issues, please reach out to our support team through your established channels. This incident is now considered resolved. We appreciate your patience and understanding while we worked to restore service.

Read the full incident report →

Started May 21, 2026, 12:39 AM UTC· resolved May 22, 2026, 03:58 AM UTC

1. investigating May 21, 2026, 12:39 AM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting the F5 XC's internal CDN edge nodes. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 00:30 PM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating May 21, 2026, 02:33 AM UTC

   The F5 Distributed Cloud CDN services are experiencing service degradation issue, It is impacting our CDN capabilities during this duration. Customers may experience intermittent traffic disruptions and increased latency as traffic is being rerouted to healthy CDN nodes during this period. We will continue to monitor the situation closely and share timely updates as additional information becomes available.

3. identified May 21, 2026, 04:18 AM UTC

   The F5 Distributed Cloud team has identified the the issue affecting CDN services and are actively working on corrective measures. We will share further updates on the progress as they become available, please feel free to reach out to our support team for prompt assistance.

4. identified May 21, 2026, 07:23 AM UTC

   The F5 Distributed Cloud team is actively working on the recovery of affected CDN nodes. We can confirm that traffic disruption is no longer expected, users may continue to experience latency during this period. We will share further updates on the progress as they become available, please feel free to reach out to our support team for prompt assistance.

5. monitoring May 21, 2026, 05:23 PM UTC

   The F5 Distributed Cloud team confirms that all CDN nodes are fully operational. Traffic is flowing normally and no further disruption is expected at this time. We remain in a monitoring phase to ensure continued stability and optimal performance. Please contact our support team if you need assistance. Thank you for your patience and understanding.

6. resolved May 22, 2026, 03:58 AM UTC

   The F5 Distributed Cloud team confirmed that all CDN services and nodes are fully operational. Traffic is flowing normally, and this incident has now been resolved. If you're still experiencing any issues, please do not hesitate to contact F5 Support for assistance.

Read the full incident report →

Started May 20, 2026, 05:01 PM UTC· resolved May 20, 2026, 09:55 PM UTC

1. investigating May 20, 2026, 05:01 PM UTC

   This advisory is to inform you that we are currently investigating reports of service degradation affecting our DNS services. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 04:50 PM UTC; • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

2. investigating May 20, 2026, 05:56 PM UTC

   At approximately 16:25 UTC, we identified DNS-related issues resulting in availability degradation for some services. Customers utilizing F5 DNS may be affected. Our engineering teams are actively working on corrective measures to address these resolution issues. Additionally, we are investigating the root cause and implementing further mitigation strategies to prevent recurrence. We are committed to keeping you informed and will share another update within 60 minutes, or sooner if more information becomes available. Thank you for your patience as we work to resolve this issue.

3. monitoring May 20, 2026, 06:58 PM UTC

   The F5 Distributed Cloud team has successfully resolved the issue that was causing intermittent DNS resolution failures. All services are now operating normally, and we are closely monitoring the environment to ensure continued stability and performance.

4. resolved May 20, 2026, 09:55 PM UTC

   The issue affecting DNS resolution has been fully resolved, and all services are operating normally. Our teams have validated system stability and will continue to monitor to ensure consistent performance. Thank you for your patience while we worked to resolve this issue. If you have any questions or concerns, please feel free to reach out to our support team. Contact information - Email support: [email protected] - Phone support: For region-specific contact details, please visit: https://my.f5.com/manage/s/article/K000135931 We appreciate your understanding and cooperation as we continue to improve our services. Sincerely, F5 Distributed Cloud

Read the full incident report →