13 February 2026, 23:15 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.

What’s next? What do I have to do?

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.

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.