Yea, sure, but that's like saying "company X stopped selling poison, it's Shop Y's fault that they're still selling it".

Nope. This is still Microsoft's fault while non-auth servers update.

First we wanted to see Microsoft update the authoritative nameservers, then move on to monitoring propagation. Conflating the two makes it difficult to monitor whether Microsoft actually fixed it correctly this time, as they appear to have screwed up their first attempt.

I wasn't attempting to address blame since I figured that was obvious enough.