Elevated 425 responses in Google Chrome 145 release
Elevated 425 responses in Google Chrome 145 release
13 February 2026, 15:23 UTC
13 February 2026, 15:23 UTC
Fastly has received reports of increased
425 Too Early
responses affecting users on the latest release of Google Chrome (v145). The release contained a change in how the browser handles retries for 425 responses, particularly for requests containing query parameters.
While this is not a result of a change to the Fastly platform, our Engineering team is coordinating with the Chrome team to clarify expected browser behavior and resolve this issue. In the meantime, we are evaluating server-side configuration changes to ensure seamless delivery for these requests while maintaining our security standards.
If your users are impacted and you have dedicated IPs you may choose to temporarily disable 0-RTT, or move traffic to an IP with 0-RTT disabled until Chrome browser behavior is normalized. You may also disable HTTP/3 support to reduce the impact of this issue.
What’s next? What do I have to do?
Contact Information
Customers with any questions or concerns may engage with our Support team through
https://support.fastly.com
or by contacting your designated account management team members.
25 February 2026, 18:46 UTC
25 February 2026, 18:46 UTC
The Chrome team has confirmed that they've identified the contributing factor and are working to deploy a fix.
Fastly will temporarily disable 0-RTT to limit the scope of impact for customers currently using TLS 1.3 0-RTT TLS configurations at 19:30 UTC.
Customers using dedicated IPs your configurations will not be changed. If you wish to disable 0-RTT for your dedicated IPs as a precaution, please contact our Support team through https://support.fastly.com or by contacting your designated account management team members.
We will post a new update once the fix from the third party service provider has been released and we see signs of recovery.
03 March 2026, 16:36 UTC
03 March 2026, 16:36 UTC
The Chrome team has merged a fix on Google Chrome version 145.0.7632.115 or higher to address the elevated "425 Too Early" responses currently affecting users.
Following an investigation, the Chrome team has developed a fix to address a regression in the browser's retry logic. The issue was triggered when standard web requests (such as page loads or searches) included query parameters. In these cases, the browser was failing to automatically retry the request if it received a "Too Early" response from the network.
The fix ensures that these common, safe-to-retry requests are handled correctly by the browser, which will resolve the errors observed by Fastly customers.
While this behavior is limited to the browser client and not a defect in the Fastly platform, we are closely monitoring this fix by the Chrome team.
We will post a final update once full mitigation and recovery has been observed.
10 March 2026, 15:45 UTC
10 March 2026, 15:45 UTC
The Chrome team has confirmed that the impact resulting in 425 Too Early responses affecting users on the version 145 release of Google Chrome has been fully mitigated. Customers may have experienced 425 Too Early responses from February 13, 2026, at 15:23 to March 10, 2026 14:43 UTC.
Our Engineering team has confirmed this behavior was limited to Chromium-based browser clients and not a defect in the Fastly platform.
This incident is resolved.
Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.