Same here, first it only affected some dev deployment (s3+cdn), now it spilled over to other buckets :-/