Final status: We’ve restarted the affected infrastructure and confirmed that the service is healthy.
Scope of impact: While we weren’t aware of any customer reports of impact, our monitoring indicated that some users may have been affected.
Start time: Friday, October 7, 2016, at 1:33 AM UTC
End time: Friday, October 7, 2016, at 1:57 AM UTC
Preliminary root cause: Infrastructure responsible for processing message requests was in an unresponsive state.
– We’ll continue to monitor the service while we develop preventative actions to stop this issue from occurring again.
This is the final update for the event.