GMail Experiences Serious Outage

JacobSteelsmith was one of many readers to note an ongoing problem with Gmail: "As I type this, GMail is experiencing a major outage. The application status page says there is a problem with GMail affecting a majority of its users. It states a resolution is expected within the next 1.2 hours (no, not a typo on my part). However, email can still be accessed via POP or IMAP, but not, it appears, through an Android device such as the G1." It's also affecting corporate users: Reader David Lechnyr writes "We run a hosted Google Apps system and have been receiving 502 Server Error responses for the past hour. The unusual thing about this is that our Google phone support rep (which paid accounts get) indicated that this outage is also affecting Google employees as well, making it difficult to coordinate."

Comments

hahahaha

[Anonymous Coward]

"The unusual thing about this is that our Google phone support rep (which paid accounts get) indicated that this outage is also affecting Google employees as well, making it difficult to coordinate."

HAHAHHAHAHAHHA

Re:Anti-Slashdot Effect

[Kamokazi]

Same here, I was just on Gmail 5 minutes ago. Funny how our Postfix server at work hasn't had any unplanned downtime in over three years, and my personal Exchange playbox hasn't had any self-induced downtime either. You really think Google could...you know...have a backup? Especially for paid customers. Just another reason for us to stay on our own server.

Re:Wow

[Anonymous Coward]

This is truth. I remember one job a sysadmin had left his username and password the same. They warned him 6 times in 2 weeks to change it. Then someone hacked the system. He had copied ssh keys all over the systems and put himself in as passwordless sudoers everywhere. But was too damn lazy to change his password from his own fscking name.

Did he get fired? No. Did he keep screwing up? Yes. He kept screwing up repeatedly. A week later he took all the servers in our data center off the internet 'cuz he took *all* the routers off line at the same damn time to replace them.

Later we found out he was rebooting the Linux servers by pulling the cords out the back.

We were paying for off site data backups and tape storage. He was sending the wrong goddamn tapes. Moron was sending the new blank fscking tapes!

Did he get fired? noooo... he left for a new job that paid more money. We gave him the most awesome references because we had to get rid of this bastard. Now he works at... wait... OMFG I'm pretty sure that he went to work at AIG just before they failed and had to get bailed out... holy effing... OMFG I've got to make some phone calls. Where the hell is he working now? Where ever it is I've got to warn Obama!

I doubt it. Once you get out of high school and work in the real world, you'll find that just because something happens, people don't always get fired. Why, because usually you'll be firing one of your best employee's a 20 percenter, one of the ones that actually does the work and knows what is going on. And even if it wasn't a 20 percenter , you don't want to send out the message, that if you do something and it causes a problem you're going to get fired. I can hear it now, "Remember Bob, he was like us, then one day he went out and did something, something went wrong, so they shit canned him. That was five years ago and we haven't done anything since."

Re:Depend on something... pay for admin

[selven]

such a large component of libertarians

Weird, I see a large component of libertarian haters who don't even understand what libertarianism is.

Re:Indeed

[Grishnakh]

The problem is so many companies run Exchange and Outlook, which are complete pieces of shit.

I use Outlook/Exchange at my current job, and just reading a single email can frequently take 30-60 seconds (it takes that long to show up after clicking on it). Luckily, I don't have to read much email as an engineer, or I'd go mad.

Re:Indeed

[drachenstern]

You obviously had the power supply fire moments after booting the server, and haven't replaced the power supply yet. That's probably the best idea. Sacrifice a virgin Exchange server to the server room, and leave it's charred ashes as a measure of penitence.

I applaud you and your willingness to set an example. You sir win +1 Internets.

-- I'll try again.

Yeah, you're supposed to hook up the network cables too. (similarly bad version: How do you know if an Exchange server is going to cause problems? It's connected to the internet.)

--I'll try again.

Your email server has a GUI? GAHHHH, the googles, they do nothing!

--I'll not try again. Those were all lousy.

Full disclosure: I actually babysit an Exchange server as part of a SBS 2k3 domain. In 30 days I won't be (there). I don't know if I plan to char the carcass of that beast when I do leave tho, so let's see what the 30th has in store, shall we?

Crap, I guess I gotta start emailing people now and telling them about the transition, huh? Stupid server...