Final Status: The investigation determined that a failure within a files database caused the service to become degraded. Engineers connected the service an alternate, healthy infrastructure, which remediated impact.
User Impact: Affected users were unable to access the Yammer service. After the service recovered, users may have experienced intermittent latency for a brief period of time.
Scope of Impact: A very limited number of customers and users appeared to be impacted. No customer reports of the issue were identified during this event.
Incident Start Time: Friday, April 15, 2016, at 7:58 AM UTC
Incident End Time: Friday, April 15, 2016, at 8:30 AM UTC
Preliminary Root Cause: A failure within a files database caused the service to become degraded.
– Analyze performance data and trends on the affected systems to help prevent this problem from happening again.
Please consider this service notification the final update on the event.