It wasn't perfect. Some of you may have noticed our attempt at putting up maintenance pages, for instance. Our method for that was questionable in hindsight. Our old method had flaws aplenty and we consider this to be an improvement, but clearly we have a ways to go on that front.
The rest of the maintenance went quite well! Superior planning from the teams involved was the real victory, here.
Services went offline promptly at 0300 UTC (2200 EST) and primary services were restored at 0557 UTC (0057 EST). There were some lingering application issues we were cleaning up (spoiled queues, some email delays due to the queueing of email during the downtime, etc.), but full service was restored by 0626 UTC.
That said, I'm confident we could have shaved significant time off of this maintenance with additional planning and preparation. There were some procedural items, particularly regarding vendor equipment, we learned too late to be helpful this time. Fortunately, our procedures have been updated and the next time this happens it will go much faster!
If you're experiencing any trouble or if you have any questions, please don't hesitate to reach out to us!