FYI.

This story is over 5 years old.

Tech

Google Docs Went Down and Everybody Freaked Out

Hope you saved your work in the CMS!

Google Docs decided it was time for everyone to throw in the towel on this Friday workday a few hours early after it started experiencing difficulties in the afternoon, locking many users out.

It's still unclear what is going on with the service, although a Google spokesperson told us "We're investigating now," and promised an update by 5:10 PM ET.

Meanwhile, it's becoming clear just how many people depend on Google Docs for work. Hope you saved your work in the CMS!

Advertisement

Raise your hand if you feel personally victimized by Google Docs being down pic.twitter.com/lPblcNbpfe
— Mediabistro (@Mediabistro) October 9, 2015

Google Drive is down? Well then… pic.twitter.com/53LT4FO4p4
— Jason Abbruzzese (@JasonAbbruzzese) October 9, 2015

"google docs is down" ::the reporter turns on johnny cash, does shot of cocaine, cracks knuckles:: "time to write in the CMS"
— ಠ_ಠ (@MikeIsaac) October 9, 2015

Waiting for Google Drive to come back online like (HT @justinsb) pic.twitter.com/5BAjNtNwjp
— Kaleigh Rogers (@KaleighRogers) October 9, 2015

Tfw Google Docs goes down but you already saved all your posts in the CMS :) pic.twitter.com/oQHFkcMco0
— Media Steph (@Media__Steph) October 9, 2015

As of now, the service is still spotty, but we will update this story if we get any word from Google.

Update, 5:23 PM: According to Google's status board, "Google Drive service has already been restored for some users, and we expect a resolution for all users in the near future. Please note this time frame is an estimate and may change."

Google also sent a statement by email at 6:22 PM:

Google Drive, Docs editors and Classroom have been restored for 99.5% of affected users as of 1:01 PM Pacific, and for the remaining 0.5% of users by 2:10 PM Pacific. During the event, our top priority was to restore service. We are now turning our attention to understanding what caused the outage; our preliminary diagnosis is that this was caused by a code push which behaved differently in widespread use than it had during testing. If you were affected, we apologize for the disruption this caused. We are calculating the impact to our business customers and will issue SLA credits as appropriate. Full details will follow in our incident report.