See https://uma.googleplex.com/timeline_v2?q=%7B%22day_count%22%3A%2290%22%2C%22end_date%22%3A%222016%2F05%2F18%22%2C%22window_size%22%3A3%2C%22filters%22%3A%5B%7B%22fieldId%22%3A%22channel%22%2C%22operator%22%3A%22EQ%22%2C%22study%22%3A%22%22%2C%22selected%22%3A%5B%224%22%5D%7D%2C%7B%22fieldId%22%3A%22platform%22%2C%22operator%22%3A%22EQ%22%2C%22study%22%3A%22%22%2C%22selected%22%3A%5B%22A%22%5D%7D%2C%7B%22fieldId%22%3A%22milestone%22%2C%22operator%22%3A%22GE%22%2C%22study%22%3A%22%22%2C%22selected%22%3A%5B%2248%22%5D%7D%5D%2C%22histograms%22%3A%5B%5B%22Net.AutoReload.ErrorAtFirstSuccess%22%5D%5D%2C%22default_entry_values%22%3A%7B%22measureModel%22%3A%7B%22measure%22%3A%22%22%2C%22buckets%22%3A%5B%5D%2C%22percentiles%22%3A%5B%2250%22%5D%2C%22selectedFormulas%22%3A%5B%5D%2C%22allFormulas%22%3A%5B%5D%7D%2C%22zeroBased%22%3Atrue%2C%22logScale%22%3Afalse%2C%22showLowVolumeData%22%3Afalse%2C%22showVersionAnnotations%22%3Atrue%7D%2C%22entries%22%3A%5B%7B%22measureModel%22%3A%7B%22measure%22%3A%22bucketProp%22%2C%22buckets%22%3A%5B%22352%22%5D%7D%2C%22zeroBased%22%3Afalse%2C%22showLowVolumeData%22%3Atrue%7D%5D%7D

Analysis posted to chrome-network-debugging:

This spike in SPDY_PING_FAILED (unlike the Windows Dev one) isn't coincident with a volume change, and is fairly large compared to previous proportions of that error in this histogram.  Having said that, it's a small proportion of the errors compared to other platforms (though that probably just means that Android is much more frequently tripping something like CONNECTION_CLOSED or INTERNET_DISCONNECTED :-}), isn't coincident with a Chrome release, and isn't large if you look at the 90 day timeline (note that I still think it's real, just that we've accepted worse in the past).