F5 Outage History
F5 is up right nowF5 had 65 outages in the last 2 years totaling 4806h 56m of downtime — averaging 2.7 incidents per month.
There were 65 F5 outages since August 27, 2025 totaling 4806h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
F5 Distributed Cloud - Jakarta (JK1) Region is Isolated - INC-20251105-409
Timeline · 4 updates
Issue with Email and SMS Alerts - INC-20251104-408
Timeline · 2 updates
- identified Nov 04, 2025, 06:01 PM UTC
F5 is aware of service degradation for our Alert notification system preventing Email based alerts from being delivered. We have identified the source of this issue and are actively working to resolve this.
- resolved Nov 04, 2025, 08:27 PM UTC
Dear Valued Customer, The recent issue affecting Email and SMS alerting functionality has been successfully resolved. The F5 Distributed Cloud team has completed their validation process and confirmed that the Email and SMS alerting functionality has been fully restored. All other services remained fully operational. This incident is now resolved, and no further impact is expected. Thank you for your patience and trust in F5 Distributed Cloud.
F5 Distributed Cloud - Service Degradation - Increase in 5xx responses - INC-20251029-406
Timeline · 4 updates
F5 NGINXaaS - Service Degradation - EastUS Basic Deployments - INC-20251023-405
Timeline · 4 updates
- investigating Oct 23, 2025, 06:02 PM UTC
Microsoft has issued a service alert regarding reduced availability of BS series virtual machines (VMs) in the EastUS region. This may impact data traffic for existing NGINXaaS deployments in the EastUS region that are utilizing the basic plan, as the basic plan relies on the BS VM type. We are monitoring the situation closely and recommend reviewing your deployment data traffic for potential disruption.
- identified Oct 23, 2025, 08:09 PM UTC
We are continuing to monitor this situation. Microsoft is currently working on the issue, however they have not provided a timeline for resolving the limitation. To minimize potential data traffic disruptions, we recommend you considering one of the following courses of action: 1. Recreate your deployments in an alternative Azure region such as East US 2. 2. If remaining in the East US region is necessary, transition to the NGINXaaS Standard V2 plan for improved stability and reliability. Please note that the NGINXaaS Basic plan does not include a Service Level Agreement (SLA) and is designed primarily for trials, development, and testing purposes. For further information, refer to the NGINXaaS for Azure documentation, including instructions on migrating from the Basic plan to the Standard V2 plan.
- identified Nov 13, 2025, 12:32 AM UTC
Microsoft has messaged that the limited capacity situation will remain for the foreseeable future. We are therefore accelerating a near term mitigation plan to replace the virtual machine (VM) type used in the East US region for all Basic deployments with a more readily available type. This effort will take approximately a week to be completed. If you need an alternative solution, you can take one of the following courses of action: 1. Recreate your deployments in an alternative Azure region such as East US 2. 2. If remaining in the East US region is necessary, transition to the NGINXaaS Standard V2 plan for improved stability and reliability. Please note that the NGINXaaS Basic plan does not include a Service Level Agreement (SLA) and is designed primarily for trials, development, and testing purposes. For further information, refer to the NGINXaaS for Azure documentation, including instructions on migrating from the Basic plan to the Standard V2 plan.
- resolved Nov 21, 2025, 06:46 PM UTC
F5 has update NGINXaaS for Azure to use a different VM type in the EastUS region. This will allow customers to resume creating Basic plan deployments in the region.
F5 Distributed Cloud - Service Degradation - Issue with delay in Access logs - INC-20251022-404
Timeline · 2 updates
Informational : New IP ranges for Distributed Cloud Regional Edge sites
Timeline · 4 updates
- monitoring Oct 21, 2025, 07:48 PM UTC
Dear Valued Customers, We are adding new IP ranges to our Regional Edge sites. To ensure uninterrupted access to our services, please whitelist these additional IP ranges before Nov 15th 2025. New IP Ranges: Americas: 185.94.142.128/25 159.60.177.0/24 159.60.175.0/24 159.60.179.0/24 159.60.181.0/24 159.60.183.0/24 Europe: 159.60.161.0/24 159.60.163.0/24 Asia: 159.60.185.0/24 Please update your firewall and security settings to allow traffic from these IPs. This change is necessary to maintain seamless connectivity and avoid disruptions. The full list of IP ranges can be found at https://docs.cloud.f5.com/docs-v2/platform/reference/network-cloud-ref If you have any questions, please feel free to contact us at [email protected]
- monitoring Nov 04, 2025, 10:17 PM UTC
Dear Valued Customers, Please note that the deadline to allowlist the new Regional Edge IP ranges has been updated to 27 November 2025 If you have any questions, please feel free to contact us at [email protected]
- monitoring Nov 06, 2025, 12:12 AM UTC
Dear Valued Customer, Please note that the deadline to allowlist the new Regional Edge IP ranges has been extended to January 5, 2026. These IP ranges will be used when we provision new Distributed Cloud Regional Edge sites. At this time, we do not yet have a confirmed date for when the new Regional Edge sites will go live. A separate notification will be sent in advance of those sites entering production. If you have any questions, please contact us at [email protected]
- resolved Apr 03, 2026, 04:47 AM UTC
This incident has been resolved.