Appears to correspond to the rollout of 53.0/2785.55.

And looks to pretty definitively only be present on ChromeOS.

Is this related to  issue 610436 ?  (Spike in EMPTY_RESPONSE on android on all channels?)

Also, rch, can you confirm that this issue is specifically around EMPTY_RESPONSE?  If so, I'll change the title.  (The link in the initial post seems to lead to a graph that's about EMPTY_RESPONSE.)

If it is around EMPTY_RESPONSE, I consider the same analysis I made in  issue 610436  to apply, and I'll make it Pri 3 & Available (meaning I don't expect anyone to work on it anytime soon).

Oh, yes sorry. I cut/paste from the chirp alert and it looks like that lost the actual error :( But yes, it was EMPTY_RESPONSE

Thanks, Ryan!

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

There's no active discussion for a long while on this thread. Since the histogram is time sensitive. Archiving this one.