My non-gmail was working perfectly :) Why dont we all use exactly the same provider so we can all be offline at the same time!

Pheewww... dunno about causing "outrage in the blogosphere", because I couldn't log into my Blogger account to post about it. Or My Google Docs. Strangely though, Google Reader and Calendar still worked.

I still can't log into Blogger this morning, although Gmail is working again now. Cookie problem, probably.

Think it was on Saturday afternoon, couldn't find Google (.com or .co.uk) or YouTube in DNS, and couldn't log on to Google Talk, for a period of a few hours. All other sites that I tried were fine. This was from my home Linux and Windows boxes, as well as the web browser on my Wii, and tried resetting the Bebox several times. Think that it must have been localised to my ISP (Be Unlimited) or my exchange, as I didn't see it mentioned anywhere.

I didn't even notice.

and yahoo now offer ymail.com addresses for those who failed to get a half decent address with gmail the first time around.

so that won't be confusing at all.

Well I use the paid-for Gmail service so I can use my own domain and wasn't too bothered about the short outage. What fuss.

I noticed this as well. Changed the DNS servers to OpenDNS and it worked ok. With BeUnlimited as well, so must have been a dns issue.

Once again, yesterday evening, I was unable to access my .mac/me mail.

And now I hear gmail was down.

Computers suck.

Google Apps suffered the same email outage last night, but Premier and Education Edition customers have an SLA.

Frankly, as much as it inconvenienced me, writing and sending out press releases via my Google Apps setup, the fact that it was up before midnight was good enough for me.

The outage had some effect though... they upgraded Google Apps to almost the latest version of Gmail (Google Apps does not have the "Always use HTTPS" option yet, but the new style interface is now available). At least my data did not go missing, which is more than what can be said for other providers.

Yup it seems to have been a Be(there)-only problem. Exact same symptoms seen on my Be connection, but could log in fine over my O2 mobile connection. Read somewhere that it's been posted on the website as a known outage.

That's the first problem I've had in my 8 months with them, best ISP I've had since EFH got gobbled by the plus.net borg.

Be/O2 had some serious routing problems on Saturday. Something to do with peering issues or something. I did try to find out more at the time, but could not get on-line....

It was a BeThere (and therefore also an O2) problem. No reg, no google (which also breaks eclipse.org it seems, downside to having google powered search..) but Beeb still worked.

Traceroute was dying at BeThere's routers.

Like someone said its a beta, and I never remeber reading anything where Google said you get 100% uptime with any of their services.

John Delaney - This was due to a fault on the Be/o2 network, two stories one is of a fire - very unlikly. The other option and the better one was a massive firewall config cock up, o2 stores lost connection to their internatl network which runs over a Be cloud, similar home broadband was the same. Some ports work eg VPN/RDC but port 80 was out.

Sounds like port 80 got blocked on the firewall, at the same time locking out o2 from it, so sent a man with a laptop to console up to fix

Kimbie

"Cos the same time GMail went tits-up, MobileMe was also having one of its regular lie downs in a darkened room.

I do not see what all the fuss is about, if it is that critical that people have 100% up time maybe they should spend some cash on a proper multi site high availability solution. Oh, but that costs money.

www.cobweb.com

If anything on the internet vanishes, I suspect my ISP first.

Yesterday, I had an embarassing outbreak of caffiene deficiency syndrome, and missed all the opportunities for outrage.

>>>Beta, to me, doesn't strike me as meaning 100% uptime.

>>>Why the 'outrage' then?

Could it be that it's been a "beta" for years?? Face it, slapping a "beta" jpg on the site does not a beta make. There comes a point where whether you call it a beta or not, it's in production use, and you have to take that responsibility seriously.

Too many places call things "betas" just so they have a fallback position when they almost inevitably break stuff. It's a byproduct of, and a crutch for the "deploy it now, test it later" development culture that web 2.0 has thrust us into. If gmail is a beta, we should have to pay for it by having ads displayed.

Once you start making commercial gain from a product, you can't really call it a beta anymore.

Geeze, I really never noticed. You mean I missed all that great action