F5 Outage History

F5 is up right now

There were 20 F5 outages since February 5, 2026 totaling 1208h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.f5cloudstatus.com

Notice April 16, 2026

Informational: Introduction of New Regional Edge Cluster Chicago (ch2-chi)

Detected by Pingoru
Apr 16, 2026, 03:07 PM UTC
Resolved
Apr 23, 2026, 04:35 AM UTC
Duration
6d 13h
Affected: Chicago, IL, United States
Timeline · 2 updates
  1. monitoring Apr 16, 2026, 03:07 PM UTC

    Dear Valued Customers, We are pleased to announce the launch of a new Regional Edge cluster Chicago (ch2-chi), which marks a significant step in enhancing the resilience and reliability of our North America Regional Edge infrastructure. The addition of the Ch2-chi Regional Edge cluster brings substantial improvements to our operational capabilities by: Enhancing Redundancy: By distributing workloads across this new cluster, we ensure better failover capabilities, minimizing service disruptions during potential outages. Reinforcing Fault Tolerance: The Ch2-chi cluster strengthens our overall infrastructure by efficiently managing traffic spikes and better balancing regional workloads, ultimately offering a more robust and reliable experience for our users. This development underscores our commitment to delivering greater availability, stability, and service quality across the North America Regional Edge network. Time: Ch2-chi will go live on April 23 2026 at 4:00 am UTC If you have any questions or concerns, please do not hesitate to contact us at [email protected]

  2. resolved Apr 23, 2026, 04:35 AM UTC

    Chicago Regional Edge site is now live

Read the full incident report →

Minor April 11, 2026

F5 Distributed Cloud - Service Degradation - Delay in GLR logs - INC-20260411-451

Detected by Pingoru
Apr 11, 2026, 11:51 PM UTC
Resolved
Apr 12, 2026, 03:08 PM UTC
Duration
15h 16m
Affected: Global Log Receiver (GLR)
Timeline · 3 updates
  1. investigating Apr 11, 2026, 11:51 PM UTC

    The F5 Distributed Cloud customers may experience a slight 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. investigating Apr 12, 2026, 02:29 AM UTC

    The F5 Distributed Cloud team has detected a delay in GLR log streaming and access log lag in the Console. We are actively working to resolve this issue. We will share further updates as they become available. Thank you for your patience and understanding.

  3. resolved Apr 12, 2026, 03:08 PM UTC

    The F5 Distributed Cloud team has successfully resolved the issue affecting GLR log streaming and access log delays in the Distributed Cloud console. Live log visibility has now been restored, and any delayed logs have been successfully backfilled. 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 →

Notice April 8, 2026

Informational: Introduction of New Regional Edge Cluster Atlanta (At1-atl)

Detected by Pingoru
Apr 08, 2026, 03:21 AM UTC
Resolved
Apr 16, 2026, 03:02 PM UTC
Duration
8d 11h
Affected: Atlanta, GA, United States
Timeline · 3 updates
  1. monitoring Apr 08, 2026, 03:21 AM UTC

    Dear Valued Customers, We are pleased to announce the launch of a new Regional Edge cluster Atlanta (At1-atl), which marks a significant step in enhancing the resilience and reliability of our North America Regional Edge infrastructure. The addition of the At1-atl Regional Edge cluster brings substantial improvements to our operational capabilities by: Enhancing Redundancy: By distributing workloads across this new cluster, we ensure better failover capabilities, minimizing service disruptions during potential outages. Reinforcing Fault Tolerance: The At1-atl cluster strengthens our overall infrastructure by efficiently managing traffic spikes and better balancing regional workloads, ultimately offering a more robust and reliable experience for our users. This development underscores our commitment to delivering greater availability, stability, and service quality across the North America Regional Edge network. Time: At1-atl will go live on April 16 2026 at 4:00 am UTC If you have any questions or concerns, please do not hesitate to contact us at [email protected].

  2. monitoring Apr 14, 2026, 04:59 PM UTC

    We've updated our notification for F5 Distributed Cloud Atlanta Regional Edge PoP commissioning. The commissioning and integration is scheduled for April 16, 2026 at 4:00 am UTC and not April 15, 2025 as previously communicated. We apologize for any confusion this may have caused. Questions? Our team is here to help. Reach out to us at [email protected]. — The F5 Distributed Cloud Team

  3. resolved Apr 16, 2026, 03:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 6, 2026

F5 Distributed Cloud - Service Degradation - DNS resolution failures for CDN domain - INC-20260406-450

Detected by Pingoru
Apr 06, 2026, 02:49 PM UTC
Resolved
Apr 07, 2026, 07:40 AM UTC
Duration
16h 51m
Affected: CDN Control Plane
Timeline · 5 updates
  1. investigating Apr 06, 2026, 02:49 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting DNS resolution. 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 14:44 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 Apr 06, 2026, 04:44 PM UTC

    We are currently investigating intermittent DNS resolution failures for the CDN domain in the Europe region. Some customers may experience occasional failures when attempting to reach certain endpoints or services that rely on DNS lookups. Our engineering team is actively working to identify the root cause and restore full stability. At this time, the impact appears to be localized to the Europe region, and all other regions are operating normally. We will provide updates here as more information becomes available. Thank you for your patience and understanding.

  3. identified Apr 06, 2026, 06:09 PM UTC

    The F5 Distributed Cloud team identified and addressed connectivity failures that were impacting CDN traffic processing in the Europe region. To mitigate the intermittency experienced, a workaround was implemented, stabilizing the affected services and reducing disruption. At this time, all XC Console core services remain operational and in a steady state. Our team is actively pursuing a permanent resolution to the issue. Additional updates will be provided as soon as further information becomes available.

  4. monitoring Apr 07, 2026, 04:52 AM UTC

    The intermittent DNS resolution failures affecting CDN traffic in the European regions have been successfully resolved. All impacted services are now operating normally. Our engineering team has completed the required remediation steps, and no further disruptions are expected. We will continue to closely monitor system performance to ensure ongoing stability. Should you encounter any related issues, please contact our support team for further assistance. Thank you for your patience while we worked to restore full service.

  5. resolved Apr 07, 2026, 07:40 AM UTC

    This incident has now been marked as resolved. All other services remained fully operational throughout the incident. If you continue to experience issues, please contact the F5 Support team for assistance. Thank you for your patience and understanding while we worked to restore full service.

Read the full incident report →

Minor March 27, 2026

F5 Distributed Cloud - Service Degradation - DNS resolution failures for CDN domain - INC-20260327-448

Detected by Pingoru
Mar 27, 2026, 11:00 PM UTC
Resolved
Mar 28, 2026, 04:08 AM UTC
Duration
5h 7m
Affected: CDN Control Plane
Timeline · 4 updates
  1. investigating Mar 27, 2026, 11:00 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting DNS resolution 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 03/27/2026, 21:59 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 Mar 27, 2026, 11:45 PM UTC

    We are currently investigating an intermittent DNS resolution failures for CDN domain in the U.S. region. Some customers may experience occasional failures when attempting to reach certain endpoints or services that rely on DNS lookups. Our engineering team is actively working to identify the root cause and restore full stability. At this time, the impact appears to be localized to the US region, and all other regions are operating normally. We will provide updates here as more information becomes available. Thank you for your patience and understanding.

  3. monitoring Mar 28, 2026, 12:31 AM UTC

    The intermittent DNS resolution failures affecting the CDN domain in the U.S. region have been successfully resolved. All impacted services are now operating normally. Our engineering team has completed the required remediation steps, and no further disruptions are expected. We will continue to closely monitor system performance to ensure ongoing stability. Should you encounter any related issues, please contact our support team for further assistance. Thank you for your patience while we worked to restore full service.

  4. resolved Mar 28, 2026, 04:08 AM UTC

    The intermittent DNS resolution failures affecting the CDN domain in the U.S. region have now been fully resolved. All impacted services are operating normally. Our engineering team has completed the necessary remediation steps, and we do not anticipate any further disruption. If you experience any related issues, please reach out to our support team for assistance. Thank you for your patience and understanding while we worked to restore full service.

Read the full incident report →

Notice March 26, 2026

Informational: Introduction of New Regional Edge Cluster Mil1-Mil (Milan)

Detected by Pingoru
Mar 26, 2026, 09:33 PM UTC
Resolved
Apr 03, 2026, 04:46 AM UTC
Duration
7d 7h
Affected: Customer Dashboard
Timeline · 2 updates
  1. monitoring Mar 26, 2026, 09:33 PM UTC

    Dear Valued Customers, We are pleased to announce the launch of a new Regional Edge cluster, Mil1-Mil (Milan), which marks a significant step in enhancing the resilience and reliability of our EU Regional Edge infrastructure. The addition of the Mil1-Mil Regional Edge cluster brings substantial improvements to our operational capabilities by: Enhancing Redundancy: By distributing workloads across this new cluster, we ensure better failover capabilities, minimizing service disruptions during potential outages. Reinforcing Fault Tolerance: The Mil1-Mil cluster strengthens our overall infrastructure by efficiently managing traffic spikes and better balancing regional workloads, ultimately offering a more robust and reliable experience for our users. This development underscores our commitment to delivering greater availability, stability, and service quality across the EU Regional Edge network. Time: MIL1-MIL will go live on March 27 2025 at 4:00 am UTC If you have any questions or concerns, please do not hesitate to contact us at [email protected].

  2. resolved Apr 03, 2026, 04:46 AM UTC

    Milan Regional Edge site is live and stable , closing the note

Read the full incident report →

Minor March 25, 2026

F5 Distributed Cloud - Service Degradation - CDN services - Incident Advisory: INC-20260325-447

Detected by Pingoru
Mar 25, 2026, 12:19 PM UTC
Resolved
Mar 25, 2026, 01:48 PM UTC
Duration
1h 29m
Affected: CDN Control Plane
Timeline · 2 updates
  1. identified Mar 25, 2026, 12:19 PM UTC

    The F5 Distributed Cloud team is investigating an issue affecting CDN purge operations. There is no impact to CDN traffic delivery and all other XC Console services remain fully operational. We are actively working on mitigation and will provide updates as more information becomes available.

  2. resolved Mar 25, 2026, 01:48 PM UTC

    The issue affecting CDN purge operations on the Distributed Cloud Console has been resolved. CDN purge functionality is now fully restored and operating as expected. This incident has been marked as resolved.

Read the full incident report →

Notice March 25, 2026

Incident Advisory: INC-20260325-447

Detected by Pingoru
Mar 25, 2026, 08:24 AM UTC
Resolved
Mar 25, 2026, 11:17 AM UTC
Duration
2h 53m
Timeline · 2 updates
  1. investigating Mar 25, 2026, 08:24 AM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting CDN. 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:20 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. resolved Mar 25, 2026, 11:17 AM UTC

    The issue has been mitigated, and services are operating normally. This was a non-service-impacting event with no impact to traffic or core services. Everything is functioning as expected and we continue to monitor stability.

Read the full incident report →

Minor March 23, 2026

F5 Distributed Cloud - Service Degradation - Delay in GLR logs - INC-20260323-446

Detected by Pingoru
Mar 23, 2026, 10:39 AM UTC
Resolved
Mar 26, 2026, 05:52 AM UTC
Duration
2d 19h
Affected: Global Log Receiver (GLR)
Timeline · 7 updates
  1. investigating Mar 23, 2026, 10:39 AM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting GLR lag 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 10:38 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 Mar 23, 2026, 11:20 AM UTC

    The F5 Distributed Cloud customers may experience a slight 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.

  3. identified Mar 23, 2026, 01:29 PM UTC

    The F5 Distributed Cloud team has identified the issue and is actively working to restore service. GLR log processing is recovering; however, logs for newly created objects are currently not available. We are actively working to resolve this issue. 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.

  4. identified Mar 23, 2026, 03:51 PM UTC

    The F5 Distributed Cloud team has confirmed that GLR processing has recovered and is operating normally. We are continuing to work on the remaining issue where logs for newly created objects are not currently available. There is no impact to traffic, and all core XC Console services remain fully operational. Further updates will be provided as they become available. Thank you for your patience and understanding.

  5. investigating Mar 23, 2026, 06:50 PM UTC

    The F5 Distributed Cloud team has confirmed that GLR (Global Log Repository) processing has recovered and continues operating normally. While GLR processing is stable, our team is actively addressing the log lag issues observed. However, there is no impact on network traffic at this time. All core XC Console services continue to function without disruption, maintaining the reliability and operational integrity of the platform. We appreciate your patience and understanding as we work to resolve the remaining issues towards service restoration.

  6. monitoring Mar 24, 2026, 04:22 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.

  7. resolved Mar 26, 2026, 05:52 AM UTC

    The F5 Distributed Cloud team has successfully resolved the issue impacting the Global Logs Receiver (GLR). Live log visibility has been fully restored in the Distributed Cloud console dashboard, and backfill logs have been recovered as expected. The system is now functioning normally, with no further impact anticipated. We sincerely appreciate your patience and understanding throughout the resolution process.

Read the full incident report →

Notice March 14, 2026

F5 Distributed Cloud - Service Degradation - Metrics Visualization Issue - INC-20260314

Detected by Pingoru
Mar 14, 2026, 05:09 PM UTC
Resolved
Mar 14, 2026, 11:20 PM UTC
Duration
6h 10m
Timeline · 2 updates
  1. investigating Mar 14, 2026, 05:09 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting access logs in Distributed Cloud. 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/14/2026, 16:58 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 Mar 14, 2026, 11:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 5, 2026

Incident Advisory: INC-20260305-444

Detected by Pingoru
Mar 05, 2026, 03:11 PM UTC
Resolved
Mar 05, 2026, 03:40 PM UTC
Duration
28m
Timeline · 3 updates
  1. investigating Mar 05, 2026, 03:11 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting XC DNS service 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 03/05/2026, 15:04 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 Mar 05, 2026, 03:39 PM UTC

    The issue has been identified, and we have taken mitigative measures to resolve the situation. This incident has been confirmed as a non-service-impacting issue.

  3. resolved Mar 05, 2026, 03:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 27, 2026

F5 Distributed Cloud - Service Degradation - XC Console down - INC-20260227-441

Detected by Pingoru
Feb 27, 2026, 03:25 PM UTC
Resolved
Mar 14, 2026, 12:01 AM UTC
Duration
14d 8h
Affected: Portal & Customer Login
Timeline · 15 updates
  1. investigating Feb 27, 2026, 03:25 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting the XC 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 02/27/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. monitoring Feb 27, 2026, 04:59 PM UTC

    XC console access has been restored, and we continue to actively monitor the environment to ensure stability. The XC Core services and traffic processing remain unaffected and operational. We appreciate your patience and understanding. If you experience any issues or have technical questions related to F5 Distributed Cloud Services, please get in touch with us at [email protected]

  3. monitoring Feb 28, 2026, 03:27 AM UTC

    XC console access has been restored, and we continue to actively monitor the environment to ensure stability. The XC Core services and traffic processing remain unaffected and operational. We appreciate your patience and understanding. If you experience any issues or have technical questions related to F5 Distributed Cloud Services, please get in touch with us at [email protected]

  4. monitoring Feb 28, 2026, 03:52 PM UTC

    XC console access continues in a steady state, and our XC platform services are operating business as usual. Proactive monitoring will remain active to ensure continued reliability and stability across the environment. XC Core services and traffic processing remain fully operational and unaffected. Thank you for your continued patience and understanding. If you experience any issues or have technical questions regarding F5 Distributed Cloud Services, please contact us at [email protected].

  5. monitoring Mar 01, 2026, 04:20 AM UTC

    XC console access remains stable, and our XC platform services continue to function normally. Proactive monitoring is still in place to maintain ongoing reliability and stability throughout the environment. All XC Core services and traffic processing are fully operational and remain unaffected. Thank you for your continued patience and understanding. If you encounter any issues or have technical questions related to F5 Distributed Cloud Services, please reach out to us at [email protected].

  6. monitoring Mar 01, 2026, 05:09 PM UTC

    Access to the XC console is stable, and all XC platform services are operating as expected. We remain committed to proactive monitoring to ensure the continued reliability and stability of the environment. All XC Core services and traffic processing are functioning normally and are unaffected. We appreciate your patience and understanding. Should you experience any issues or have technical inquiries regarding F5 Distributed Cloud Services, please don't hesitate to contact us at [email protected].

  7. monitoring Mar 02, 2026, 04:43 AM UTC

    XC console access continues in a steady state, and our XC platform services are operating business as usual. Proactive monitoring will remain active to ensure continued reliability and stability across the environment. XC Core services and traffic processing remain fully operational and unaffected. Thank you for your continued patience and understanding. If you experience any issues or have technical questions regarding F5 Distributed Cloud Services, please contact us at [email protected].

  8. investigating Mar 02, 2026, 02:34 PM UTC

    We are currently investigating an ongoing issue with the XC Console being unreachable. Please note that traffic processing and other XC core functionality remain unaffected. We appreciate your patience and understanding. If you experience any issues or have technical questions related to F5 Distributed Cloud Services, please get in touch with us at [email protected].

  9. monitoring Mar 02, 2026, 05:00 PM UTC

    Access to the XC console has been restored, and we are actively monitoring the environment to maintain stability. Please note that XC Core services and traffic processing have remained fully operational and unaffected throughout. Thank you for your ongoing patience and understanding. Should you encounter any issues or have technical inquiries regarding F5 Distributed Cloud Services, please feel free to contact us at [email protected].

  10. monitoring Mar 03, 2026, 03:23 AM UTC

    XC Console access remain fully operational. Users can connect to the Console and all other services are operating normally. This event remains in the monitoring phase as we work to ensure continued stability and optimal performance. We sincerely appreciate your patience and understanding during this time. If you experience any issues or have technical questions regarding F5 Distributed Cloud Services, please contact us at [email protected].

  11. monitoring Mar 04, 2026, 07:29 AM UTC

    XC Console access remain fully operational. Users can connect to the Console and all other services are operating normally. This event remains in the monitoring phase. The F5 Distributed Cloud team is actively working on a permanent fix and is currently validating changes in lower environments to ensure stability. We appreciate your continued patience and understanding. If you experience any issues or have technical questions regarding F5 Distributed Cloud Services, please contact us at [email protected]

  12. monitoring Mar 06, 2026, 08:47 PM UTC

    The XC Console remains fully operational, allowing users to connect seamlessly. In addition, all other services associated with the XC Console are functioning normally. The F5 Distributed Cloud team has applied a partial fix to address ongoing issues, and the implementation process is continuing. During this period, proactive monitoring will stay active to ensure the ongoing stability and reliability of our services. We sincerely appreciate your continued patience and understanding as we work to maintain and improve service quality. If you encounter any issues or have technical questions regarding F5 Distributed Cloud Services, please reach out to our support team at [email protected]

  13. monitoring Mar 07, 2026, 06:41 PM UTC

    The XC Console remains fully operational, and users are able to connect without any interruption. All related services within the XC platform are also functioning as expected. The F5 Distributed Cloud team is continuing work on the remaining implementation activities, and enhanced monitoring will remain in place to ensure ongoing stability and performance throughout this period. We sincerely appreciate your continued patience and understanding as we work to maintain and improve service quality. If you encounter any issues or have technical questions regarding F5 Distributed Cloud Services, please reach out to our support team at [email protected].

  14. monitoring Mar 08, 2026, 06:55 PM UTC

    The XC Console is fully operational, enabling users to connect without any interruptions. All associated services within the XC platform are functioning as anticipated. The F5 Distributed Cloud team continues to work on the remaining implementation tasks, with enhanced monitoring in place to ensure stability and performance throughout this time. We sincerely appreciate your continued patience and understanding as we work to maintain and improve service quality. If you encounter any issues or have technical questions regarding F5 Distributed Cloud Services, please reach out to our support team at [email protected].

  15. resolved Mar 14, 2026, 12:01 AM UTC

    The XC Console and all associated services within the XC platform are operating as expected, with no interruptions to functionality. Enhanced monitoring has successfully ensured stability and performance during the recent implementation tasks. This incident is now resolved, and the platform is fully restored to its optimal state. Should you experience any issues or have technical questions regarding F5 Distributed Cloud Services, please do not hesitate to contact our support team at [email protected]. Thank you for your patience and understanding throughout this process. We remain committed to delivering reliable and high-quality services.

Read the full incident report →

Notice February 25, 2026

F5 Distributed Cloud - Service Degradation - XC Console down - INC-20260225-441 #3

Detected by Pingoru
Feb 25, 2026, 07:46 PM UTC
Resolved
Feb 26, 2026, 12:09 AM UTC
Duration
4h 23m
Affected: Portal & Customer Login
Timeline · 3 updates
  1. investigating Feb 25, 2026, 07:46 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting the XC 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 02/25/2026, 19: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.

  2. monitoring Feb 25, 2026, 08:52 PM UTC

    F5 has identified the cause of the access issues to the Distributed Cloud Console, and a fix has been implemented. The accessibility to the console has been restored. During and after the event, other services remain fully operational. Our internal teams continue to monitor the environment closely to ensure stability. If you experience any issues, please contact F5 Support for further assistance

  3. resolved Feb 26, 2026, 12:09 AM UTC

    The F5 Distributed Cloud console continues to operate normally and remain in steady state. All other services remain fully operational. If you have any questions or concerns, please do not hesitate to contact our support team. This incident has been marked as resolved.

Read the full incident report →

Minor February 24, 2026

F5 Distributed Cloud - Service Degradation - XC Console down - INC-20260224-441 #2

Detected by Pingoru
Feb 24, 2026, 07:03 PM UTC
Resolved
Feb 25, 2026, 05:46 AM UTC
Duration
10h 42m
Affected: Portal & Customer Login
Timeline · 5 updates
  1. investigating Feb 24, 2026, 07:03 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting the XC 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 02/24/2026, 18:45 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 Feb 24, 2026, 07:25 PM UTC

    F5 is aware that the Distributed Cloud Console access issue reoccured. Currently access to the Distributed Cloud Console should be restored. The cause is identified and the same as previously communicated in INC-20260224-441 and we actively monitoring availability and working to ensure that this is mitigated properly to restore stability. There remains no impact to Traffic of Services.

  3. monitoring Feb 24, 2026, 09:05 PM UTC

    F5 is aware of continued intermittent impact to console availability. The Distributed Cloud Team is actively engaged on this issue and monitoring the availability of the Distributed Cloud Console. We will continue to update the status of the situation if it changes.

  4. monitoring Feb 25, 2026, 12:43 AM UTC

    F5 Distributed Cloud team has mitigated the access issue. All services remain fully operational. Users can connect to the Console and all other services are operating normally. We will continue the proactive monitoring to ensure the stability of our services.

  5. resolved Feb 25, 2026, 05:46 AM UTC

    The F5 Distributed Cloud console continues to operate normally and remain in steady state. All other services remain fully operational. If you have any questions or concerns, please do not hesitate to contact our support team. This incident has been marked as resolved.

Read the full incident report →

Critical February 24, 2026

F5 Distributed Cloud - Service Degradation - XC Console down - INC-20260224-441

Detected by Pingoru
Feb 24, 2026, 03:55 PM UTC
Resolved
Feb 24, 2026, 06:25 PM UTC
Duration
2h 29m
Affected: Portal & Customer Login
Timeline · 5 updates
  1. investigating Feb 24, 2026, 03:55 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting the F5 Distributed Cloud console login. 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:54 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 Feb 24, 2026, 04:06 PM UTC

    F5 is aware of issues accessing the Distributed Cloud Console. Traffic processing and services remain fully operational. The impact is limited to access to the Distributed Cloud console interface only. F5 is actively investigating this issue and working to resolve it. We will provide additional updates as our investigation continues.

  3. identified Feb 24, 2026, 04:28 PM UTC

    F5 has identified the cause for the access issues to the Distributed Cloud Console. We are actively working to resolve the cause of this issue, we have seen intermittent recovery but consider this impact to still be ongoing. Traffic and Services remain unimpacted.

  4. monitoring Feb 24, 2026, 04:53 PM UTC

    A fix has been implemented to address the cause of the Distributed Cloud Console access issue. Console access has been restored. Users may continue to experience some intermittent slowness while the system fully stabilizes. Customer traffic and services remain unaffected. Our internal teams continue to monitor the environment closely to ensure full performance recovery. We will provide additional updates as needed.

  5. resolved Feb 24, 2026, 06:25 PM UTC

    F5 has mitigated the Distributed Cloud Console service interruption. Users can connect to the Distributed Cloud Console and all other services are operating normally. We will continue the proactive monitoring to ensure the stability of our services. The service interruption was caused by an out-of-memory (OOM) condition triggered by a period of anomalous traffic patterns. To ensure immediate stability, we have scaled our memory resources to accommodate the increased load. The F5 Distributed Cloud team is currently investigating the underlying traffic behaviour and workings towards a comprehensive permanent resolution. Please reach out to [email protected] if you face F5 Distributed Cloud Services related issues or technical questions.

Read the full incident report →

Minor February 12, 2026

F5 Distributed Cloud - Service Degradation - Delay in access logs - INC-20260212-440

Detected by Pingoru
Feb 12, 2026, 12:47 PM UTC
Resolved
Feb 13, 2026, 12:16 AM UTC
Duration
11h 28m
Affected: Customer Dashboard
Timeline · 5 updates
  1. investigating Feb 12, 2026, 12:47 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting access logs in Distributed Cloud. 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/12/2026, 12:44 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 Feb 12, 2026, 01:17 PM UTC

    The F5 Distributed Cloud team has observed delay in access logs on the Distributed Cloud Console UI. Currently, there is no impact to live log availability; however, brief intervals of elevated latency may still be observed. The team continues to investigate and address the root cause of the issue. Please note that all core Distributed Cloud Console services remain fully operational. We are committed to keeping you informed and will provide further updates as more information becomes available. We sincerely appreciate your patience and understanding during this time.

  3. monitoring Feb 12, 2026, 02:48 PM UTC

    The F5 Distributed Cloud team can confirm that access logs on the Distributed Cloud Console UI are now fully restored and available on the dashboard. Please note that throughout this incident, all core Distributed Cloud Console services remained fully operational. The incident will now transition to the monitoring stage to ensure continued stability and performance. We sincerely appreciate your patience and understanding during this time and thank you for your trust in F5 Distributed Cloud.

  4. monitoring Feb 12, 2026, 07:47 PM UTC

    The F5 Distributed Cloud team confirms that the access logs on the Distributed Cloud Console UI are now fully operational and operating as expected. This event remains in the monitoring phase as we work to ensure continued stability and optimal performance. We sincerely appreciate your patience and understanding during this time and thank you for your trust in F5 Distributed Cloud.

  5. resolved Feb 13, 2026, 12:16 AM UTC

    The issue with the delay access logs on the Distributed Cloud Console UI has been resolved. All essential Distributed Cloud Console UI are now fully restored and available on the dashboard. This incident has been marked as resolved.

Read the full incident report →

Minor February 9, 2026

F5 Distributed Cloud - Service Degradation - BGP Sessions Flapping in London, Ashburn, New York & Frankfurt - INC-20260209-439

Detected by Pingoru
Feb 09, 2026, 11:20 PM UTC
Resolved
Feb 12, 2026, 04:59 PM UTC
Duration
2d 17h
Affected: Portal & Customer LoginAshburn (dc12), VA, United StatesSao Paulo, BrazilAmsterdam, NetherlandsSingapore, SingaporeSydney, AustraliaDubai, United Arab EmiratesFrankfurt (fr4), GermanyTokyo, JapanMelbourne, AustraliaTel Aviv, IsraelAshburn (b-dc12), VA, United StatesOsaka, JapanAshburn (c-dc12), VA, United StatesFrankfurt (b-fr4), GermanyNew York (ny8), NY, United StatesLondon (tn2), United KingdomHong Kong, AsiaMumbai, IndiaLondon (b-tn2), United KingdomNew York (b-ny8), NY, United StatesSan Jose (sv10), CA, United StatesParis (pa2), FranceChennai, IndiaParis (pa4), FranceSan Jose (b-sv10), CA, United StatesSeattle, WA, United StatesMadrid, SpainJakarta, IndonesiaLisbon, PortugalToronto, CanadaDallas (dal3), TX, United StatesStockholm, SwedenParis, France (Network)Dallas (b-dal3), TX, United StatesAtlanta, GA, United StatesRouted Originated ServicesMontreal, CanadaMiami, FL, United States (Network)Chicago, IL, United States
Timeline · 9 updates
  1. investigating Feb 09, 2026, 11:20 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting BGP sessions flapping on FRA and LON. 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 23:13 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 Feb 09, 2026, 11:55 PM UTC

    The F5 Distributed Cloud support team has identified an issue affecting some BGP sessions in London, Ashburn, New York and Frankfurt. 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 on addressing this issue.

  3. monitoring Feb 10, 2026, 01:13 AM UTC

    The F5 Distributed Cloud team has identified and mitigated the impact. Our services are operational and working as expected. We are actively monitoring to ensure stability on our services, If you continue to experience any issue, please reach out to the F5 Support team for assistance.

  4. monitoring Feb 10, 2026, 09:01 PM UTC

    The F5 Distributed Cloud Support team has identified a potential issue impacting GRE tunnels for some customers. We are actively working on resolving this matter. All other services remain fully operational. Updates will be shared as they become available.

  5. identified Feb 10, 2026, 10:23 PM UTC

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

  6. identified Feb 10, 2026, 11:46 PM UTC

    Our engineering teams have identified the root cause and are actively validating a fix ahead of a planned production rollout to restore full GRE tunnel functionality. At this time, the impact remains limited to GRE tunnels for some customers; all other F5 Distributed Cloud services continue to operate normally.

  7. identified Feb 11, 2026, 01:56 AM UTC

    Following our previous update, we would like to share the next steps toward fully restoring GRE tunnel functionality. Our engineering teams have completed the validation and are ready to implement the fix. Based on this progress, the production deployment of the fix has been scheduled as outlined below. Fix Deployment Window: Start Time: 11 Feb 2026, 02:00 UTC End Time: 11 Feb 2026, up to 08:00 UTC (timing may vary by region) Deployment Approach: Engineering teams will coordinate the rollout during the emergency change window. Execution has been prioritized based on non-business hours and the number of affected customers per region. During this window, the expected impact per region may range from approximately 15 minutes up to 1 hour, depending on: 1. The number of GRE tunnel updates required 2. BGP session re-establishment following the changes Current Impact Status: At this time, the impact remains limited to GRE tunnels for a subset of customers. All other F5 Distributed Cloud services continue to operate normally. Projected Impact During the Fix Roll-out: Customers with multiple GRE tunnels are expected to maintain service continuity during the update, while customers with a single GRE tunnel may experience brief connectivity interruptions as the fix is applied and routing converges. Contact Information: - Email Support: [email protected] - Phone Support: Region-specific contact details are available at https://my.f5.com/manage/s/article/K000135931 Thank you for your continued patience and cooperation as we work to restore full service functionality. Sincerely, F5 Distributed Cloud

  8. monitoring Feb 11, 2026, 08:22 AM UTC

    The F5 Distributed Cloud team has successfully applied the fix for this issue. Our services are operational and working as expected. We are actively monitoring the situation to ensure stability, and will provide further updates as necessary. In the meantime, if you continue to experience any issue, please reach out to the F5 Support team for further assistance regarding the same.

  9. resolved Feb 12, 2026, 04:59 PM UTC

    The issue with F5 Distributed Cloud that was causing BGP session flapping has been resolved, and the service is now fully operational. All other services remained fully operational throughout the incident. This incident has been marked as resolved. If you continue to experience issues, please contact the F5 Support team for assistance.

Read the full incident report →

Major February 8, 2026

F5 Distributed Cloud - Service Degradation - BGP Sessions Flapping in Chicago, Ashburn & New York - INC-20260208-438

Detected by Pingoru
Feb 08, 2026, 04:53 AM UTC
Resolved
Feb 09, 2026, 12:36 AM UTC
Duration
19h 43m
Affected: Ashburn (dc12), VA, United StatesNew York (ny8), NY, United StatesChicago, IL, United States
Timeline · 4 updates
  1. investigating Feb 08, 2026, 04:53 AM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting one or more 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 02/08/2026, 04:41 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 Feb 08, 2026, 05:51 AM UTC

    The F5 Distributed Cloud support team has identified an issue affecting some BGP sessions in Chicago, Ashburn and New York. 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 on addressing this issue.

  3. monitoring Feb 08, 2026, 06:48 AM UTC

    The F5 Distributed Cloud team has identified and applied a fix for this issue. Our services are operational and working as expected. We are actively monitoring the situation to ensure stability, and will provide further updates as necessary.

  4. resolved Feb 09, 2026, 12:36 AM UTC

    The Distributed Cloud team has confirmed that our services are stable and operating as expected. This incident has been resolved. If you continue to experience any issue, please reach out to the F5 Support team for assistance.

Read the full incident report →

Minor February 5, 2026

F5 NGINXaaS having issues to new deployments in East US2 and West US3 regions INC-20260205-437

Detected by Pingoru
Feb 05, 2026, 11:43 PM UTC
Resolved
Feb 09, 2026, 06:54 PM UTC
Duration
3d 19h
Affected: NGINXaaS for Azure
Timeline · 3 updates
  1. investigating Feb 05, 2026, 11:43 PM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting NGINXaaS for Azure deployment creation failing in eastus2 and westus3 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 02/05/2026, 23:39 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 Feb 06, 2026, 12:05 AM UTC

    The F5 NGINXaaS team has identified an issue where creation of new NGINXaaS for Azure deployments is failing in the East US2 and West US3 regions. Existing deployments are not affected and continue to operate normally. All other operations are functioning as expected, and all other regions are not impacted. Our partner team at Microsoft is actively investigating the issue and working toward a resolution. We will provide updates as more information becomes available. If you are experiencing a critical business impact, please contact our support team (https://my.f5.com/manage/s/createcase).

  3. resolved Feb 09, 2026, 06:54 PM UTC

    The F5 NGINXaaS team has implemented a fix to resolve this issue. NGINXaaS for Azure deployment creation is now functioning normally in the East US2 and West US3 regions. If you are still experiencing issues with your deployments, please reach out to our support team at https://my.f5.com/manage/s/createcase.

Read the full incident report →

Minor February 5, 2026

F5 Distributed Cloud - Service Degradation - Metrics Visualization Issue - INC-20250205-436

Detected by Pingoru
Feb 05, 2026, 08:36 AM UTC
Resolved
Feb 05, 2026, 02:38 PM UTC
Duration
6h 1m
Affected: Customer Dashboard
Timeline · 4 updates
  1. investigating Feb 05, 2026, 08:36 AM UTC

    This advisory is to inform you that we are currently investigating reports of service degradation affecting performance dashboard metrics 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 02/05/2026, 08:30 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 Feb 05, 2026, 09:37 AM UTC

    The F5 Distributed Cloud support team has identified an issue affecting the display of metrics within the customer dashboard. 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 Feb 05, 2026, 12:20 PM UTC

    Our service remains stable and we will continue to monitor the environment to ensure reliability and stability. Currently, the issue with metric visualisation has been resolved. If you experience any issue, please contact F5 Support for further assistance.

  4. resolved Feb 05, 2026, 02:38 PM UTC

    The F5 Distributed Cloud team monitored the services and confirmed the issue impacting metrics visualization is resolved. If you experience any issue, please contact F5 Support for further assistance.

Read the full incident report →

Looking to track F5 downtime and outages?

Pingoru polls F5's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when F5 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track F5 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring F5 for free

5 free monitors · No credit card required