F5 outage history and live incidents

Nov 9, 23:49 UTC
Resolved - We are pleased to confirm that the service degradation related to delayed Access Logs has been fully resolved. All services have now fully recovered and are functioning as expected.

Our F5 Distributed Cloud team has continued to closely monitor the platform to ensure ongoing stability, and no further issues have been detected.

If you continue to experience any issues or have further questions, please do not hesitate to 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

We sincerely appreciate your patience and understanding throughout the resolution process.

Sincerely,
F5 Distributed Cloud

Nov 9, 18:31 UTC
Update - F5 Distributed Cloud team have confirmed that the Access logs service continues to operate normally with no further delays or anomalies detected. All F5 Distributed Cloud services remain stable and fully functional.

While standard performance metrics have been restored across all environments, our teams will continue proactive monitoring throughout the day to ensure ongoing stability and sustained performance.

Nov 9, 13:24 UTC
Monitoring - The F5 Distributed Cloud team has validated and confirmed the issue with delay of Access logs functionality has been restored and no more issues are being observed. All other services remain fully operational. We will continue to monitor our service for the next few hours and ensure they are performing as expected. Please contact our support team if you have any further questions or concerns accordingly.

Nov 9, 12:19 UTC
Update - The F5 Distributed Cloud Team has detected an issue with the delay of access logs in the UI. Please note that all XC Console core services are fully operational. Engineering team is actively working to resolve this matter and restore full service as soon as possible. We will keep you updated with any new information.

Thank you for your patience and understanding.

Nov 9, 12:07 UTC
Investigating - This advisory is to inform you that we are currently investigating reports of service degradation affecting Distributed Cloud Access 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 12:06 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.

Nov 7, 23:55 UTC
Resolved - F5 Distributed Cloud services in the SV10 and b-SV10 regions have been restored, and all systems are operating normally. Monitoring has confirmed stable performance, and this incident is now closed.

If you continue to experience issues, please contact F5 Support:

• Email: [email protected]
• Phone: F5 Support phone numbers

Nov 7, 19:40 UTC
Monitoring - The F5 Distributed Cloud team confirms that the issue affecting configuration processing across the SV10 and b-SV10 Regional Edges is fully resolved. Services remain stable and are functioning as expected. Our teams are actively monitoring system performance before final closure. We appreciate your patience and understanding.

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.

Nov 7, 16:40 UTC
Identified - The F5 Distributed Cloud team has identified an issue affecting configuration processing across the SV10 and b-SV10 Regional Edges. Traffic has already been rerouted to ensure ongoing service stability. Please note that Customer Edge (CE) sites connected to the SV10 region will experience a delay in configuration propagation during this period. Additionally, temporary reporting delays may cause tunnel metrics to display an incorrect down status.

All other services remain operational. Our engineers are actively working on a resolution, and we will share further updates as they become available.

Contact Information:
- Email Support: [email protected]
- Phone Support: [https://my.f5.com/manage/s/article/K000135931](https://my.f5.com/manage/s/article/K000135931)

Nov 7, 15:59 UTC
Investigating - This advisory is to inform you that we are currently investigating reports of service degradation affecting connectivity issues San Jose (SV10) region.

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 03:48 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.

Nov 5, 22:22 UTC
Resolved - The F5 Distributed Cloud team confirms that the response code classification issue is fully resolved. Services have remained stable and are functioning as expected. This incident is now marked as resolved.

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

Nov 5, 10:49 UTC
Monitoring - The hotfix addressing the response code classification issue has been successfully deployed across all Regional Edges (REs). F5 Distributed Cloud services continue to operate normally, with no functional or performance impact to end-user traffic.

Our teams are actively monitoring the environment to ensure sustained stability before final closure. If you experience any lingering issues, please reach out to F5 Support.

Contact Information:
- Email Support: Reach us at [email protected] for any questions or assistance.
- Phone Support: For region-specific contact details, please visit [https://my.f5.com/manage/s/article/K000135931].

Nov 4, 07:51 UTC
Identified - We have successfully completed testing and validation of the hotfix and are preparing to deploy it to production. This fix addresses the issue where http2.remote_reset appears alongside various HTTP response codes.

To minimize any disruption, the deployment will be rolled out progressively. Separate maintenance notifications detailing specific windows and impact for each region will be published on the F5 Distributed Cloud Status page.

F5 Distributed Cloud services continue to operate normally, with no functional or performance impact to end-user traffic. If you are experiencing critical business impact, please contact us through your established F5 support channels.

Nov 3, 07:51 UTC
Update - Our investigation and remediation efforts regarding the reporting of various HTTP response codes accompanied by http2.remote_reset remain on track.

F5 Distributed Cloud services continue to operate normally, with no functional or performance impact to end-user traffic.

Testing and validation in our lower environments are currently in progress, and we will share further details once complete. If you are experiencing any critical business impact, please reach out via your established F5 support channels.

Nov 2, 07:29 UTC
Update - Our investigation and remediation efforts regarding the reporting of HTTP 200 responses accompanied by http2.remote_reset remain on track.

F5 Distributed Cloud services continue to operate normally, with no functional or performance impact to end-user traffic.

Testing and validation are currently in progress, and we will share further details once complete. If you are experiencing any critical business impact, please reach out via your established F5 support channels.

Nov 1, 06:53 UTC
Update - Our investigation and remediation efforts regarding the reporting of HTTP 200 responses accompanied by http2.remote_reset remain on track. There is no functional or performance impact to end-user traffic, and F5 Distributed Cloud services continue to operate normally.
We will share further details and the deployment schedule once validation is complete. If you are experiencing any critical business impact, please reach out via your established F5 support channels.

Oct 31, 07:26 UTC
Update - Our investigation into the reporting of HTTP 200 responses accompanied by http2.remote_reset remains ongoing. There is no end-user impact associated with this behavior, and F5 Distributed Cloud services continue to operate normally.

We are continuing to assess the response classification and test potential corrections to ensure accurate reporting. Further updates will be published on the F5 Cloud Status page as additional information becomes available.

If you are experiencing a critical business impact, please reach out through your established support channels. We appreciate your patience as we work to resolve this issue.

Oct 30, 06:07 UTC
Investigating - We are investigating reports of HTTP 200 responses accompanied by http2.remote_reset, first identified on October 17 at 10:00 UTC. This behavior does not indicate an end-user issue, and F5 Distributed Cloud services continue to operate normally.

Our teams are reviewing how these responses are classified, conducting additional tests to determine the root cause, and working on a fix to ensure accurate reporting. We will share further details and any necessary mitigation guidance as they become available.

Please visit the F5 Cloud Status page (https://www.f5cloudstatus.com/) for the latest updates. If you are experiencing a critical business impact, please contact our support team through your established support channels.

Thank you for your patience and continued trust in F5.

Oct 28, 18:55 UTC
Investigating - This advisory is to inform you that we are currently investigating reports of service degradation affecting BGP sessions flapping on STO

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:46 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.

Oct 28, 03:09 UTC
Resolved - The F5 Distributed Cloud team would like to inform you that the issue affecting Distributed Cloud Services in the Toronto, Canada Point of Presence (PoP) has been resolved. We are pleased to confirm that services have remained stable and are functioning as expected. This incident is now marked as resolved.

If you continue to experience any issues, please contact the F5 Support team for further assistance.

- 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

Oct 27, 22:54 UTC
Monitoring - Our engineering team has mitigated the issue affecting Distributed Cloud Services in the Toronto, Canada Point of Presence (PoP) and restored normal traffic routing.

Traffic was initially rerouted away from the Toronto, Canada site on October 27, 2026, at 18:18 UTC to prevent service disruption while our operations team performed recovery and health validations on the affected infrastructure. Those validations are now complete, and the Toronto, Canada PoP has been returned to active service as of 20:55 UTC.

Our teams are closely monitoring the environment to ensure continued stability. If you experience any lingering issues in the region, please reach out to F5 Support.

Contact Information:
- Email Support: Reach us at [email protected] for any questions or assistance.
- Phone Support: For region-specific contact details, please visit https://my.f5.com/manage/s/article/K000135931.

Oct 27, 18:29 UTC
Investigating - Our engineering team is investigating a failures affecting Distributed Cloud Services.

During this period, customers may experience response timeouts. Our engineering teams are actively troubleshooting to isolate the root cause and restore normal performance levels.

We will share further updates as more information becomes available. We appreciate your patience and understanding.

Contact Information:
- Email Support: Reach us at [email protected] for any questions or assistance.
- Phone Support: For region-specific contact details, please visit https://my.f5.com/manage/s/article/K000135931.

Oct 31, 06:52 UTC
Resolved - The F5 Distributed Cloud team confirms that the performance degradation affecting multiple F5 Distributed Cloud Regional Edge sites is fully resolved. Services have remained stable and are functioning as expected. This incident is now marked as resolved.

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

Oct 31, 06:52 UTC
Update - The F5 Distributed Cloud team confirms that the performance degradation affecting multiple F5 Distributed Cloud Regional Edge sites is fully resolved. Services have remained stable and are functioning as expected. This incident is now marked as resolved.

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

Oct 27, 09:46 UTC
Update - All Distributed Cloud Regional Edges are operating normally globally, with traffic processing and XC console core services running in a steady state.

Our engineering teams are actively monitoring system health to maintain expected performance. We will share further updates as we move closer to full resolution.

Thank you for your continued patience and support.

Oct 26, 20:38 UTC
Update - Distributed Cloud Regional Edges globally are operating normally. Traffic processing and XC console core services are in a steady state.

Our engineering teams continue to closely monitor service health and stability to ensure sustained performance. We will provide further updates as we progress toward full resolution.

Thank you for your continued patience.

Oct 26, 11:16 UTC
Monitoring - We are monitoring performance across the affected F5 Distributed Cloud Regional Edge sites. Our engineering teams are closely observing service health and stability. We will share further updates as more information becomes available.

Thank you for your continued patience.

Note: An HTTP 200 response accompanied by http2.remote_reset does not indicate an end-user issue. We are reviewing the classification of this response code, which is unrelated to the current incident.

Oct 26, 08:25 UTC
Update - We are continuing to investigate performance degradation affecting multiple F5 Distributed Cloud Regional Edge sites and our engineering teams are actively working to determine the underlying cause and return services to normal operation. We will share further updates as more information becomes available.

Thank you for your continued patience.

Oct 26, 06:00 UTC
Update - We continue to investigate performance degradation affecting multiple F5 Distributed Cloud Regional Edge sites. Our engineering teams are working to isolate the root cause and restore normal performance. We will share further updates as more information becomes available.

Thank you for your continued patience and understanding.

Oct 26, 04:14 UTC
Update - We are investigating a performance degradation issue affecting multiple F5 Distributed Cloud Regional Edge sites.
During this period, customers may experience intermittent connection timeouts. Our engineering teams are actively troubleshooting to isolate the root cause and restore normal performance levels.

We will share further updates as more information becomes available. We appreciate your patience and understanding.

Oct 26, 03:33 UTC
Update - We are investigating a performance degradation issue affecting multiple F5 Distributed Cloud Regional Edge sites.
During this period, customers may experience intermittent connection timeouts. Our engineering teams are actively troubleshooting to isolate the root cause and restore normal performance levels.

We will share further updates as more information becomes available. We appreciate your patience and understanding.

Oct 26, 02:34 UTC
Investigating - This advisory is to inform you that we are currently investigating reports of service degradation affecting XC services in few 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 02:26 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.

Oct 14, 11:53 UTC
Resolved - Following a period of monitoring, functionality for the Global Log Receiver (GLR) and console access logs has fully returned to normal operations, with traffic processing remaining stable and operating normally throughout this service event.

This incident has now been marked as resolved. Thank you for your continued patience, support, and trust in F5.

Oct 14, 11:20 UTC
Monitoring - On October 14 2026, at approximately 10:35 UTC, F5 Distributed Cloud team detected a service degradation affecting Global Log Receiver (GLR) and console access logs. Currently, all affected services have been restored and are functioning as intended. However, services will remain under monitoring to ensure continued stability.

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.

Oct 14, 10:40 UTC
Investigating - This advisory is to inform you that we are currently investigating reports of service degradation affecting Global Log Relay (GLR) and console access logs 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 10/14/2026, 10:35 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.

Aug 25, 23:19 UTC
Investigating - This advisory is to inform you that we are currently investigating reports of service degradation affecting Network Traffic in WES and MB2.

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/25/2026, 23:07 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.

Jun 17, 18:36 UTC
Investigating - 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.