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.

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.

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.

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.

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.

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.