not even 24hrs after I as I release my 1st app engine app tweetc.com, it goes down, great!

for the sake of equidistribution, i hope it’s not china. Make it be the Saudis

What about the fact that it’s so biased towards Python? Why is the Java API so crippled and a year behind the Python version? Is it because one of the major Python guys involved in the Google App Engine?

There goes the cloud. Our corporate site is down.

Guess that’s why they call it a Preview Release

It started at 7:53am PST, as a Memcashe and and Datastore outage, since my small app ( http://www.geognos.com ) handles those errors it run with some minor problems for some time, currently the whole sytem has intermitent anomalies. ( http://code.google.com/status/appengine/ )
Also panoramio.com (a Google company) looks down from my part of the world (East Europe) – Is panoramio hosted in GAE ?

The datastore is hosed but running in read only mode now….. http://code.google.com/status/appengine/detail/datastore/2010/02/24#ae-trust-detail-datastore-get-error_rate

And it’s back up: http://twitter.com/api_status/status/9585861420

We are back too.

As of 9:48am, all applications should now be available in read-only mode.
Panoramio is up also and yes it looks like hosted on GAE see: http://www.panoramio.com/forum/viewtopic.php?t=25504

I like it!

We are monitoring Appengine quite closely. It went down around 7:34am PST

Socialwok (http://socialwok.com) – Business social networking for Google Apps is running on it. We are back online as of 10am ! :-)

Ming

And we are back too!

With AppBrain (http://www.appbrain.com) – the web based Android market to discover great apps and install directly to the phone.

And also all our app engine powered android apps: funny jokes, love poems, pickup lines, etc..

It’s back in read-only mode meaning no writing to the datastore.
Our iPhone app relies on it so we see the errors first hand.

I worked a little with App Engine for Java on a weekend project (well…since everybody else is not-so-subtly plugging: nicksmap.org) and, while I would not say that the Java flavor of App Engine is crippled, I will never implement a web application in Java again. I’ll stick to languages and frameworks that are a little more DRY. Only real benefit of GWT is that you get a bunch of abstractions for AJAXey widgets, but the trade-off is that you have to deal with a mess of configuration files. My simple project wound up consisting of something like 35 .java files, 10 configuration files, a pair of .html and .css files, and a Python script to do batch processing (necessary because App Engine imposes a 30-second cutoff for processes). Had I gone the Python/Django route, I’m sure I could have reduced the size of this thing by about 85% and wound up with something that was a greater pleasure to manage. That’s my 2 cents.

Atleast it’s way more stable than the Twitter API. That thing is down so much and has discrepencies in data that it becomes hard to work with.

Fun with google voice
I love google voice, the translations are awesome.

http://www.gvwtf.com

this is just one problem with relying on google. just look at their hosted apps solution. if you delete a user you can’t recreate the same user for 5 days.

but their system now, for over a month, has been broken and you can’t recreate a user. they acknowledged the problem back in January and still have not released a fix.

rely on google and the cloud at your own peril

Blatant (yet relevant) plug – I made a t-shirt for just such an occasion. “The Cloud is Down.”

http://www.zazzle.com/yummymelon

“Google employees are being discouraged from using Python for new projects:

Well, simple common sense is going to limit Python’s applicability when operating at Google’s scale: it’s not as fast as Java or C++, threading sucks, memory usage is higher, etc.”

http://groups.google.com/group/unladen-swallow/browse_thread/thread/4edbc406f544643e?pli=1

3:00 and all is still not well in the Google cloud:

As of 1:00pm PST, we are seeing lingering write issues with a small
percentage of datastore entity groups. As well, a small percentage of
cron jobs are not running correctly. We believe both issues are
linked to the unforeseen outage earlier today and we are treating them
as high priority. We will update this thread hourly with more
information going forward.

As of 2:00pm PST, we are continuing to investigate the lingering
datastore and cron issues. We will continue to update this thread as
we progress.

As of 3:00pm PST, we have determined the datastore writes and only
reads within transactions are affected. We are working on a fix for
the issue.

Post-mortem on Google Groups: https://groups.google.com/group/google-appengine/browse_thread/thread/a7640a2743922dcf

Here we are again ? http://code.google.com/status/appengine/