Bad Debian repository cache on Docker Hub?

As can be seen at the bottom of this build log, and among other projects over the past couple of days, Docker Hub is failing on retrieving a package that matches it’s checksum. As the build works locally, and on other docker image build services, this would indicate that (if Docker Hub is using a cache for package repositories) that server revalidation is not being performed, and the cached package is either corrupt or not being retrieved properly.

Here is a snippet:

Get:124 http://httpredir.debian.org/debian/ wheezy/main sqlite3 amd64 3.7.13-1+deb7u2 [119 kB]
Get:125 http://httpredir.debian.org/debian/ wheezy/main sudo amd64 1.8.5p2-1+nmu3+deb7u1 [851 kB]
Get:126 http://httpredir.debian.org/debian/ wheezy/main python-dev all 2.7.3-4+deb7u1 [920 B]
Get:127 http://httpredir.debian.org/debian/ wheezy/main xml-core all 0.13+nmu2 [24.2 kB]
Get:128 http://httpredir.debian.org/debian/ wheezy/main python-imaging amd64 1.1.7-4+deb7u2 [460 kB]
Get:129 http://httpredir.debian.org/debian/ wheezy/main python-setuptools all 0.6.24-1 [449 kB]
Get:130 http://httpredir.debian.org/debian/ wheezy/main xauth amd64 1:1.0.7-1 [37.2 kB]
e[91mFailed to fetch http://httpredir.debian.org/debian/pool/main/g/gcc-4.7/cpp-4.7_4.7.2-5_amd64.deb  Hash Sum mismatch
e[0mFetched 125 MB in 15s (8028 kB/s)
e[91mE: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
e[0mRemoving intermediate container b9e920cdc682

Same problem here. Locally it works and not on docker cloud.