Arguable, but there is something to be said for pushing it out there. Maybe it would have been better as a staggered release, but it's not like they need to wait for the next update to solve these problems. These are all issues with server-side map quality, which can be updated on-the-fly.
We can only hope they're aggressively removing dead POIs and adding new ones. If it has been a week and nothing has changed for anyone, I would start to worry.
"Brighton, UK", Satellite - a major UK city is so blurry you can't see streets.
"Grand Cayman, Cayman Islands" - ends up in the middle of the sea, and no roads on the islands at all.
"Colchester" - satellite shows clouds, in B&W
"Senkaku Islands" - compare satellite with standard to see duplicates of these disputed islands.
"Puno,Peru"- in lake Titicaca
etc.
They probably had to rush this out, but it's really not ready for widespread use in some areas; they'd have done better to cut back the features and massively extend their testing (or use a crowd-sourced alternative). Given how extensively this is used in iOS, both by apps using Mapkit and by customers every day round the world, it's vital that is it correct, and getting it wrong in such obvious ways is a massive strategic error on Apple's part.