News for hackers. Stuff that matters.
Re:Gmail service disruption by blhack on Monday September 23, 2013 @04:23PM (#6433883)
This is really frustrating for me.

I argued up and DOWN with people about us switching to google apps for our email.

Up until recently, we were hosting our own mail on a server in our switch room.

"It's more reliable!" I would insist.

Well...it hasn't been more reliable. There has been more than one longish-term downtime that I can remember since we switched over.

When I was hosting it myself, I could give people status updates, an estimate for when it would be fixed, some kind of explanation.

Now, all I can give them is "it's broken. I don't know why, and google isn't telling anybody why."

Very frustrating, especially considering how much we pay every month for it.

Re:Gmail service disruption by jlgaddis on Monday September 23, 2013 @08:08PM (#6434989)
You've just described one of my biggest problems w/ outsourcing mail, etc.

Really, downtime isn't a big deal (to an extent, of course) because most people realize that "shit happens" and there will be the occasional downtime regardless of who's handling mail.

The problem is that you are, in effect, helpless in these situations. Like you mentioned, you can at least keep your customers updated when it's a problem with your own machines. When you've outsourced it to someone else, you're at their mercy, so to speak.

"What's wrong with the mail system?" "I dunno." "When do you think it will be fixed?" "I dunno." "Today? Tomorrow? Next week?" "I dunno."

Re:Gmail service disruption by jfoster on Monday September 23, 2013 @09:21PM (#6435264)
It's true that it can be awkward in such situations, but there are two things that still make it "better":

1. Google will bring it back up in a timeframe that is very comparable (if not better) than your average in-house IT team would.

2. Given (1), if you ask people how much per year they are willing to pay for transparency in such circumstances, most businesses will not be willing to dedicate very much of their budget towards it unless it increases reliability. The "helpless" feeling is just because you can't see Google's engineers working to fix it. Surely no one doubts that they are doing their utmost to bring it back.

Re:Gmail service disruption by chuckp on Monday September 23, 2013 @04:53PM (#6434079)
This was pretty much my reaction. We switched about 3 years ago from a self hosted Exchange system and up until now it has been pretty good. Only issues were isolated accounts offline for under a hour.

Back then I could say we are about 75% back and give a full description of the issue in laymans terms which usually curbed the anxieties. Today I basically pointed them to the status page saying that this is all I have to work with. In my experience Google's support has been pretty bad but that is because most of the time their products work well, but yea I feel in the dark when something like this occurs. Still their uptime has been better than having that "oh shit" moment because a DC is degraded.

In the end, everyone could still access the email and nothing was lost.

Re:Gmail service disruption by enneff on Monday September 23, 2013 @07:43PM (#6434904)
But how much actual downtime have you had, by comparison?
Re:Gmail service disruption by kmfrk on Monday September 23, 2013 @04:32PM (#6433940)
What's customer service like in a situation like that, given that you're paying for it?
Re:Gmail service disruption by blhack on Monday September 23, 2013 @05:02PM (#6434137)
Because you asked, I tracked down a support number and called it. It said that: "we are experiencing a problem with gmail. Check google.com/appstatus for updates. If your issue is NOT about gmail, please stay on the line."

So...nothing.

Re:Gmail service disruption by kmfrk on Monday September 23, 2013 @05:05PM (#6434159)
Jesus. I know that was the answer I expected, but it still amazes me.
Re:Gmail service disruption by cenhyperion on Monday September 23, 2013 @06:26PM (#6434584)
It's a mess, but on the flip side what could support do for you? They knew about it and I'm guessing every engineer on the team was working on getting service back online.

All they really can do is tell you "It's down. We're aware of the issue. We're actively working to resolve it."