Yammer down?

%3CLINGO-SUB%20id%3D%22lingo-sub-24171%22%20slang%3D%22en-US%22%3EYammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24171%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20the%20past%20hour%20we%20have%20been%20getting%20this%20message%20when%20trying%20to%20log%20into%20Yammer%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3EOur%20services%20aren't%20available%20right%20now%3CP%3EWe're%20working%20to%20restore%20all%20services%20as%20soon%20as%20possible.%20Please%20check%20back%20soon.%3C%2FP%3E%3C%2FDIV%3E%3CDIV%3EFor%20more%20details%2C%20please%20check%20%3CA%20href%3D%22https%3A%2F%2Fstatus.yammer.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstatus.yammer.com%2F%3C%2FA%3E%3CSPAN%3ERef%20A%3A%209FF0495297CF4F6DA00EDE2CFEA0B421%20Ref%20B%3A%20E193E01A78339C923272E6FCF3848299%20Ref%20C%3A%20Fri%20Oct%2021%2010%3A57%3A29%202016%20PST%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fstatus.yammer.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstatus.yammer.com%3C%2FA%3Eis%20not%20showing%20any%20updates%20for%20this%20issue.%20Also%20no%20updates%20in%20the%20Office%20365%20Admin%20Center.%20Anyone%20else%20experiencing%20this%3F%20Any%20idea%20whats%20going%20on%3F%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-24171%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24282%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24282%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20back%20up!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24266%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24266%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20waiting%20on%20ours%20to%20be%20available%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24263%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24263%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20client%20side%20or%20server%20side%3F%20%26nbsp%3BMeaning%20is%20it%20possible%20that%20my%20network%26nbsp%3Bis%20accessible%20from%20some%20areas%20but%20not%20others%3F%20%26nbsp%3BThe%20news%20articles%20seems%20to%20suggest%20that%20the%20effect%20is%20specific%20to%20locale.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24260%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24260%22%20slang%3D%22en-US%22%3E%3CP%3ESeems%20like%20my%20instance%20is%20back%20up.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24239%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24239%22%20slang%3D%22en-US%22%3E%3CP%3EInternet's%20busted%20today.%20%26nbsp%3BPartially.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.bloomberg.com%2Fnews%2Farticles%2F2016-10-21%2Finternet-service-disrupted-in-large-parts-of-eastern-u-s%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.bloomberg.com%2Fnews%2Farticles%2F2016-10-21%2Finternet-service-disrupted-in-large-parts-of-eastern-u-s%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fmashable.com%2F2016%2F10%2F21%2Fsites-across-internet-struggle-after-cyberattack%2F%23IpT7ghFR5OqH%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fmashable.com%2F2016%2F10%2F21%2Fsites-across-internet-struggle-after-cyberattack%2F%23IpT7ghFR5OqH%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeems%20to%20be%20limited%20to%20Northeastern%20US.%20%26nbsp%3BMostly.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24212%22%20slang%3D%22en-US%22%3ERE%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24212%22%20slang%3D%22en-US%22%3EYes%2C%20we%20continue%20to%20work%20to%20resolve%20the%20issue%2C%20but%20as%20David%20points%20out%2C%20it's%20a%20much%20larger%20issue%20than%20just%20Yammer.%20Appreciate%20your%20patience.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24204%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24204%22%20slang%3D%22en-US%22%3EFinally%20got%20an%20update%20from%20%3CA%20href%3D%22https%3A%2F%2Fstatus.yammer.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstatus.yammer.com%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EYA82277%20%7C%20Can%E2%80%99t%20access%20yammer.com%3CBR%20%2F%3E%3CBR%20%2F%3EUser%20impact%3A%20Users%20may%20be%20unable%20to%20access%20yammer.com.%3CBR%20%2F%3E%3CBR%20%2F%3ECurrent%20status%3A%20We%E2%80%99ve%20determined%20that%20incoming%20connections%20to%20the%20service%20had%20become%20degraded%20on%20a%20portion%20of%20server%20infrastructure.%20We%E2%80%99ve%20taken%20corrective%20steps%20to%20route%20connections%20through%20healthy%20infrastructure%20in%20order%20to%20mitigate%20impact%20and%20we%E2%80%99re%20currently%20monitoring%20service%20health%20to%20confirm%20service%20restoration.%3CBR%20%2F%3E%3CBR%20%2F%3EScope%20of%20impact%3A%20A%20few%20customers%20have%20reported%20this%20issue%2C%20and%20our%20analysis%20indicates%20that%20any%20user%20served%20through%20the%20affected%20infrastructure%20will%20experience%20this%20problem.%3CBR%20%2F%3E%3CBR%20%2F%3EStart%20time%3A%20Friday%2C%20October%2021%2C%202016%2C%20at%203%3A52%20PM%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EPreliminary%20root%20cause%3A%20Incoming%20connections%20to%20the%20service%20had%20become%20degraded%20on%20a%20portion%20of%20server%20infrastructure.%3CBR%20%2F%3E%3CBR%20%2F%3ENext%20update%20by%3A%20Friday%2C%20October%2021%2C%202016%2C%20at%207%3A30%20PM%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24195%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24195%22%20slang%3D%22en-US%22%3EWe%20saw%20an%20outage%20earlier%20as%20well%2C%20but%20for%20about%2015%20mins%20or%20so.%20It's%20been%20over%20an%20hour%20this%20afternoon.%20No%20update.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24189%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24189%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20not%20in%20my%20Service%20Health.%26nbsp%3B%20I%20wonder%20why.%26nbsp%3B%20We%20are%20enterprise%20but%20non-profit.%26nbsp%3B%20I%20have%20refreshed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24187%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24187%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20wondering%20if%20it%20was%20related%20to%20that.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24186%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24186%22%20slang%3D%22en-US%22%3E%3CP%3EUs%20too.%26nbsp%3B%20I%20contacted%20MS%20Support%20and%20have%20received%20a%20few%20messages%20from%20them.%3C%2FP%3E%3CP%3EThis%20came%20after%20this%20mornings%20interruption.%3C%2FP%3E%3CP%3E%22Please%20be%20informed%20that%20we%20had%20a%20Service%20Interruption%20happened%20today%20and%20we%20just%20got%20an%20update%20from%20the%20Operations%20Team%20that%20the%20services%20on%20Yammer%20is%20operational%20now%20and%20you%20should%20be%20able%20to%20access%20to%20your%20Yammer%20without%20any%20issues.%22%3C%2FP%3E%3CP%3EI%20have%20not%20gotten%20another%20followup%20for%20this%20afternoons%20outage%26nbsp%3Bbut%20I%20have%20had%20a%20lot%20of%26nbsp%3Bsuccess%20with%20support%20so%20I%20am%20hopeful%20and%20I%20like%20the%20commitment%20to%20transparency%20of%20service%20health.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EChristine%20Stack%20%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EIT%20Director%20for%20Program%20Development%3C%2FP%3E%3CP%3EJesuits%20of%20Canada%20and%20the%20USA%3C%2FP%3E%3CP%3E1016%2016th%20Street%20NW%2C%20suite%20400%3C%2FP%3E%3CP%3EWashington%2C%20D.C.%2020036%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24185%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24185%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fdowndetector.com%2Fstatus%2Flevel3%2Fmap%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fdowndetector.com%2Fstatus%2Flevel3%2Fmap%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24182%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24182%22%20slang%3D%22en-US%22%3E%3CP%3ECheck%20this%20out%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYammer%20is%20on%20the%20list%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fgizmodo.com%2Fthis-is-probably-why-half-the-internet-shut-down-today-1788062835%3Futm_source%3Ddigg%26amp%3Butm_medium%3Dfacebook%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fgizmodo.com%2Fthis-is-probably-why-half-the-internet-shut-down-today-1788062835%3Futm_source%3Ddigg%26amp%3Butm_medium%3Dfacebook%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24180%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24180%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20an%20update%20for%20this%20hit%20the%20Office%20365%20Admin%20Center%20just%20now%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3ERestoring%20service%20-%20Oct%2021%2C%202016%201%3A12%20PM%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22%22%3ETitle%3A%20Can%E2%80%99t%20access%20yammer.com%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3EUser%20Impact%3A%20Users%20may%20be%20unable%20to%20access%20yammer.com.%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3ECurrent%20status%3A%20We%E2%80%99ve%20determined%20that%20incoming%20connections%20to%20the%20service%20had%20become%20degraded%20on%20a%20portion%20of%20server%20infrastructure.%20We%E2%80%99ve%20taken%20corrective%20steps%20to%20route%20connections%20through%20healthy%20infrastructure%20in%20order%20to%20mitigate%20impact%20and%20we%E2%80%99re%20currently%20monitoring%20service%20health%20to%20confirm%20service%20restoration.%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3EScope%20of%20impact%3A%20A%20few%20customers%20have%20reported%20this%20issue%2C%20and%20our%20analysis%20indicates%20that%20any%20user%20served%20through%20the%20affected%20infrastructure%20will%20experience%20this%20problem.%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3EStart%20time%3A%20Friday%2C%20October%2021%2C%202016%2C%20at%203%3A52%20PM%20UTC%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3EPreliminary%20root%20cause%3A%20Incoming%20connections%20to%20the%20service%20had%20become%20degraded%20on%20a%20portion%20of%20server%20infrastructure.%3C%2FDIV%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%26nbsp%3B%3C%2FDIV%3ENext%20update%20by%3A%20Friday%2C%20October%2021%2C%202016%2C%20at%207%3A30%20PM%20UTC%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-24173%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20down%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-24173%22%20slang%3D%22en-US%22%3E%3CP%3EYes!%20I'm%20seeing%20the%20same%20issues.%20First%20earlier%20this%20morning%20and%20then%20now%20for%20the%20past%2020%20mins.%20Any%20updates%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ecc%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F22%22%20target%3D%22_blank%22%3E%40Anna%20Chu%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62%22%20target%3D%22_blank%22%3E%40Pavan%20Tapadia%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3506%22%20target%3D%22_blank%22%3E%40Juliet%20Wei%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

For the past hour we have been getting this message when trying to log into Yammer:

 

Our services aren't available right now

We're working to restore all services as soon as possible. Please check back soon.

For more details, please check https://status.yammer.com/Ref A: 9FF0495297CF4F6DA00EDE2CFEA0B421 Ref B: E193E01A78339C923272E6FCF3848299 Ref C: Fri Oct 21 10:57:29 2016 PST
 
https://status.yammer.com is not showing any updates for this issue. Also no updates in the Office 365 Admin Center. Anyone else experiencing this? Any idea whats going on?
15 Replies

Yes! I'm seeing the same issues. First earlier this morning and then now for the past 20 mins. Any updates??

 

cc @Anna Chu@Pavan Tapadia@Juliet Wei

Looks like an update for this hit the Office 365 Admin Center just now:

 

Restoring service - Oct 21, 2016 1:12 PM

 

Title: Can’t access yammer.com
 
User Impact: Users may be unable to access yammer.com.
 
Current status: We’ve determined that incoming connections to the service had become degraded on a portion of server infrastructure. We’ve taken corrective steps to route connections through healthy infrastructure in order to mitigate impact and we’re currently monitoring service health to confirm service restoration.
 
Scope of impact: A few customers have reported this issue, and our analysis indicates that any user served through the affected infrastructure will experience this problem.
 
Start time: Friday, October 21, 2016, at 3:52 PM UTC
 
Preliminary root cause: Incoming connections to the service had become degraded on a portion of server infrastructure.
 
Next update by: Friday, October 21, 2016, at 7:30 PM UTC

Us too.  I contacted MS Support and have received a few messages from them.

This came after this mornings interruption.

"Please be informed that we had a Service Interruption happened today and we just got an update from the Operations Team that the services on Yammer is operational now and you should be able to access to your Yammer without any issues."

I have not gotten another followup for this afternoons outage but I have had a lot of success with support so I am hopeful and I like the commitment to transparency of service health. 

 

Christine Stack

IT Director for Program Development

Jesuits of Canada and the USA

1016 16th Street NW, suite 400

Washington, D.C. 20036

I was wondering if it was related to that. Thanks!

Still not in my Service Health.  I wonder why.  We are enterprise but non-profit.  I have refreshed.

We saw an outage earlier as well, but for about 15 mins or so. It's been over an hour this afternoon. No update.
Finally got an update from https://status.yammer.com/

YA82277 | Can’t access yammer.com

User impact: Users may be unable to access yammer.com.

Current status: We’ve determined that incoming connections to the service had become degraded on a portion of server infrastructure. We’ve taken corrective steps to route connections through healthy infrastructure in order to mitigate impact and we’re currently monitoring service health to confirm service restoration.

Scope of impact: A few customers have reported this issue, and our analysis indicates that any user served through the affected infrastructure will experience this problem.

Start time: Friday, October 21, 2016, at 3:52 PM UTC

Preliminary root cause: Incoming connections to the service had become degraded on a portion of server infrastructure.

Next update by: Friday, October 21, 2016, at 7:30 PM UTC

Yes, we continue to work to resolve the issue, but as David points out, it's a much larger issue than just Yammer. Appreciate your patience.

Seems like my instance is back up.

Is it client side or server side?  Meaning is it possible that my network is accessible from some areas but not others?  The news articles seems to suggest that the effect is specific to locale.

Still waiting on ours to be available again.

We are back up!