Category Archives: Uncategorized

[UPDATE] UPCOMING SCHEDULED MAINTENANCE; January 3, 2015; 01:00am, PST

We will be performing scheduled maintenance on January 3, 2015. The maintenance will commence at 01:00am, PST, and will last up to an hour, until 02:00am, PST. Please expect Yammer.com to be unreachable during this time. We will post here … Continue reading

Posted in Uncategorized

UPCOMING SCHEDULED MAINTENANCE; January 3, 2015; 02:00am, PST

Update: The start time of this maintenance window has been changed to 01:00am, PST. Always check status.yammer.com for the latest updates. We will be performing scheduled maintenance on January 3, 2015. The maintenance will commence at 02:00am, PST, and will last … Continue reading

Posted in Uncategorized

UPCOMING SCHEDULED MAINTENANCE; December 20, 2014; 10:00AM, PDT

We will be performing scheduled maintenance on our load balancers on December 20, 2014. The maintenance will commence at 10:00am, PDT, and will last up to an hour, until 11:00am, PDT. Please expect Yammer.com to be unreachable during this time. We will … Continue reading

Posted in Uncategorized

[RESOLVED]: SERVICE INTERRUPTION: 12/10/14; 07:59 AM PST

The Yammer Engineering team was able to resolve the issue that was causing feeds to fail to load and service has now returned to normal. A Root Cause Analysis for this incident with additional details will be posted within the week.​

Posted in Uncategorized

SERVICE INTERRUPTION: 12/10/14; 07:32 AM PST

Yammer is currently experiencing an issue that is causing feeds to fail to load across Yammer networks. Our team is currently working to resolve this. We will update here with additional information as it becomes available.

Posted in Uncategorized

[RESOLVED] SERVICE INTERRUPTION; 12/03/2014; 7:52PM-7:56PM PST

Between 7:52PM PST to 7:56 PM PST there was a short outage. This issue has been resolved and all services are restored.

Posted in Uncategorized

[UPDATE]SERVICE INTERRUPTION: 27/11/2014; 6:59 AM PST

*Yammer feeds not loading intermittently* – This issue has now been resolved by our Engineering team Thank you for your patience

Posted in Uncategorized