Resolved -
The F5 Distributed Cloud team has successfully completed all ongoing Regional Edge (RE) upgrades, including B-Ashburn DC12. The issue that caused the widespread 503 errors has been resolved. Our services have remained stable and although at this time we are closing this incident, F5 will continue to closely monitor our services to ensure ongoing stability.
For any concerns or issues, please contact F5 Support for assistance. Thank you for your patience and understanding.
Jul 6, 06:26 UTC
Update -
The F5 Distributed Cloud team has successfully completed all ongoing Regional Edge (RE) upgrades, including B-Ashburn DC12. We have observed a significant decline of 503 errors globally across customer traffic. Our services remain stable and we will continue to monitor the environment to ensure service stability.
For any concerns or issues, please contact F5 Support for assistance. Thank you for your patience and understanding.
Jul 6, 05:28 UTC
Monitoring -
The F5 Distributed Cloud team has successfully completed all ongoing Regional Edge (RE) upgrades with the exception of B-Ashburn DC12 which will be handled during a separate ongoing maintenance. F5 has observed a significant decline of 503 errors globally across customer traffic. We continue actively working to ensure full stability of services.
We will continue to share updates as progress is made, at this time though unless anything changes updates will now occur every 12 hours.
Jul 5, 23:05 UTC
Update -
The F5 Distributed Cloud team remains actively engaged in remediation efforts. Subsequent batch of Regional Edges (REs) has been successfully upgraded. We will continue to share timely updates as progress is made.
Jul 5, 19:55 UTC
Update -
The F5 Distributed Cloud team remains dedicated to resolving this issue and is making consistent progress. We'll continue to share timely updates as developments occur.
We sincerely appreciate your ongoing trust, patience, and support.
Jul 5, 17:53 UTC
Update -
The F5 Distributed Cloud team is fully committed to resolving this issue and making steady progress. We will continue to keep you informed with timely updates as we move forward.
Thank you for your continued trust, patience, and understanding.
Jul 5, 15:44 UTC
Update -
The F5 Distributed Cloud team remains actively engaged in remediation efforts. Subsequent batch of Regional Edges (REs) has been successfully upgraded. We will continue to share timely updates as progress is made.
We appreciate your continued patience and understanding.
Jul 5, 13:58 UTC
Update -
The F5 Distributed Cloud team remains actively engaged on remediation of the issue causing 503 response errors through ongoing upgrade activities. We will continue to share timely updates as we progress further. Thank you.
Jul 5, 12:11 UTC
Update -
The F5 Distributed Cloud team remains actively engaged on resolving the 503 response issues. The upgrade activities are ongoing and there is significant improvement seen with the deployments done so far. More updates shall be provided as we progress further. Thank you for your continued patience and understanding.
Jul 5, 10:09 UTC
Update -
The F5 Distributed Cloud team remains focused on resolving the 503 response issues through ongoing upgrade activities, which have already yielded measurable improvements. We will continue to communicate progress through regular updates.
Jul 5, 08:02 UTC
Update -
The F5 Distributed Cloud team remains actively engaged in remediation efforts. Subsequent batch of Regional Edges (REs) has been successfully upgraded. We will continue to share timely updates as progress is made.
Jul 5, 06:05 UTC
Update -
The F5 Distributed Cloud team remains committed in driving their remediation efforts to address the 503 responses. Upgrade activities are still underway and there are significant improvement seen with the deployments done so far. More updates shall be provided as we progress further.
Jul 5, 04:01 UTC
Update -
The F5 Distributed Cloud team continues their remediation efforts to address the 503 responses. Another batch of Regional Edges (REs) have been successfully completed. We will provide further updates upon the successful completion of the next phase of upgrades.
Jul 5, 01:29 UTC
Update -
The F5 Distributed Cloud team continues to implement remediation efforts to address the issue of 503 responses. Upgrade activities are currently underway, and preliminary results from the already upgraded batch of Regional Edges (REs) are promising. We will provide further updates upon the successful completion of the next phase of upgrades.
Thank you for your patience and understanding.
Jul 4, 22:49 UTC
Update -
The F5 Distributed Cloud team is working to resolve the issue that is resulting in 503 responses. At this time, an upgrade is being applied to several Regional Edges (REs) as part of our remediation strategy. This process is being conducted in a controlled and phased manner to ensure stability and minimize impact.
We appreciate your patience and will continue to provide updates as progress is made.
Thank you for your understanding.
Jul 4, 20:25 UTC
Update -
The F5 Distributed Cloud team is dedicated to resolving the root cause of the 503 errors experienced. Our team is committed to keeping you informed as service restoration progresses. We truly appreciate your patience and trust in F5.
Jul 4, 18:10 UTC
Update -
The F5 Distributed Cloud team is continuously working to address the root cause of the 503 errors. We will provide further updates as additional information becomes available. We sincerely appreciate your patience and understanding during this time.
Jul 4, 15:53 UTC
Update -
The F5 Distributed Cloud team remains actively engaged in working towards a fix of the issue causing 503 errors. We will share updates as more information becomes available. Thank you for your patience and understanding.
Jul 4, 14:04 UTC
Update -
The F5 Distributed Cloud team is working across multiple REs to fix the issue causing 503 errors. We are closely monitoring the progress and shall keep you updated. Thank you for your patience and understanding.
Jul 4, 10:45 UTC
Identified -
The F5 Distributed Cloud team remains actively engaged in working towards a resolution of the issue causing 503 errors. We will keep you updated on the progress. Thank you for your understanding.
Jul 4, 08:15 UTC
Update -
The F5 Distributed Cloud team remains actively engaged in working towards a resolution of the issue. We will share updates as more information becomes available. Thank you for your patience and understanding.
Jul 4, 05:50 UTC
Update -
The F5 Distributed Cloud team has identified an issue causing 503 error codes. Our team is actively working to resolve this matter, and we are committed to keeping you informed with updates as they become available. Thank you for your patience and understanding.
Jul 4, 03:48 UTC
Investigating -
This advisory is to inform you that we are currently investigating reports of 503 error codes affecting multiple customers.
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:38 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.
Jul 4, 02:37 UTC