mike | Shared With: Everyone - Jul 02 2009 | google, appengine, outage, fail
mike | Shared With: Everyone - Oct 20 2007 | google, realability, outage, adsenseSystem down message in 27 languages (including once in American English, and once in British English - in case you are confused by the spelling of "apologize", you can scroll down a page and read it 'correctly' spelled as "apologise").
Quoted: The Google AdSense website is temporarily unavailable. Please try back later.
We apologize for any inconvenience.
mike | Shared With: Everyone - Aug 16 2007 | skype, reliability, outage, voip
mike | Shared With: Everyone - Feb 20 2007 | flickr, web services, outage, data center, operations, reliability
FlickR is down today. Blog claims it's back up - but it isn't. The FlickR home page says FlickR is having a "massage". Why is it that people feel that humor is a good way to deal with service outages. To me, it just makes me more angry that the people who run it find it so easy to interpret their inconveniencing me as a joke.
mike | Shared With: Everyone - Dec 06 2005 | Google, Outage
Anyone else seeing the Google home page crap out today. I use Google's personalized home page, but I haven't been able to bring up Google for a while. I think their login-system may be down (or at least, I can't get to it). Unfortunately, I couldn't even use the non-personalized generic google home page as the main one would keep redirecting me, and the login would take forever (hang).
So, I deleted all my cookies, got onto to google.com again. Still can't log in, but I changed my home page to this one (google.com/webhp) - hopefully that will always point to the generic page, with no redirects so I can use google even when the personalization system is broken).
Related Content from Around Faves
-
Google's Calendar widget builder. Support for multiple calendars to display, and some style options. This always results in a single iframe tag to embed on your site.
It seems odd that the builder has to sent size information to the embedded iframe url. Why is this not just rendered on the client where it has access to it's frame size?
1 FaverViewed: 13 Times - mike - 11 days ago1 FaverViewed: 3 Times
- mike - Feb 19 20091 FaverViewed: 30 Times
reliability
-
We inadvertently provisioned a few database machines with MyISAM instead of InnoDB, and it has been a nightmare. I strongly advice against using MyISAM -- ever.
With MyISAM, we periodically get these incorrect "duplicate key" errors that don't go away until you run the lenghty "repair table" command that somehow fixes everything.
1 FaverViewed: 3 TimesQuoted: Use MyISAM when: The data isn't too critical ( "unreliable and slow, related to table size, table repair process" )
...
Use InnoDB for tables when: The table will be big (100Mb+ - "For reliability and performance, we use InnoDB for almost everything at Wikipedia - we just can't afford the downtime implied by MyISAM use and check table for 400GB of data when we get a crash." ) - mike - Aug 11 20081 FaverViewed: 1 Time
- mike - Apr 14 20073 FaversViewed: 6 Times

