
Yeah, it's not an issue with Chrome, it's an issue with Google.
It has only just started happening today and affects stable, beta and dev channels, of which none have been updated today, so the problem must lie server side.
Also, using terminology 'latest' version is confusing, because there are 3 latest versions, stable, beta and dev channels.
Best to put the version number, unlike most of the muppets in that linked Google thread.