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.