This appears to be working correctly again.
On Wednesday, May 25, 2016 at 3:11:25 PM UTC-7, David Fischer wrote:
>
> Starting a few minutes ago, I'm not able to write to Cloud Storage from
> Appengine whatsoever:
>>
>>
>> Exception: Expect status [201] from Google
Starting a few minutes ago, I'm not able to write to Cloud Storage from
Appengine whatsoever:
>
>
> Exception: Expect status [201] from Google Storage. But got status 503.
> Path: u'/...'.
> Request headers: {'x-goog-resumable': 'start', 'x-goog-api-version': '2',
> 'accept-encoding': 'gzip,
ST today.
>
> We have applied a fix and the error rate has been steadily decreasing
> since 13:25.
>
> I will post to this thread if we have any significant updates.
>
> John Lowry
>
> On Monday, February 22, 2016 at 1:57:53 PM UTC-8, David Fischer wrote:
>>
I'm seeing elevated error levels with the request to "get_serving_url" and
for completely valid images and formats (PNGs and JPGs). It is not failing
100% but I'm seeing errors at a much higher rate than normal. I've had
about 100 errors in the past hour and it started about an hour ago.
Is
As of about 4PM PST yesterday, this is resolved.
On Wednesday, January 20, 2016 at 2:20:04 PM UTC-8, David Fischer wrote:
>
> Starting at about 8AM PST today, I'm seeing elevated error levels on my
> app on Appengine. I see batches of requests where my code on Appengine is
> not e
Starting at about 8AM PST today, I'm seeing elevated error levels on my app
on Appengine. I see batches of requests where my code on Appengine is not
even executed and I simply receive a generic server error (not my normal
custom 500 page) that says "Error: Server Error - The server encountered
ture and having zero visibility into issues related to
>>> them is really a pain when things like this happen. It's understandable
>>> that issues occur, but it sure would be nice to be able to know that Google
>>> engineers are aware of them and are working on them wit
I think this is the status for this
event: https://status.cloud.google.com/incident/appengine/15024
On Wednesday, December 2, 2015 at 11:55:04 AM UTC-8, Jim wrote:
>
> Can anyone from Google comment on this?
>
>
> On Wednesday, December 2, 2015 at 8:40:24 AM UTC-6, John Wheeler wrote:
>>
>>
utes tops. Lots of churn on the
> instances.
>
>
>
> On Tuesday, December 1, 2015 at 11:11:14 AM UTC-6, David Fischer wrote:
>>
>> I'm seeing something similar. Our task queues are also filling up with
>> tasks and our traffic hasn't changed. For us, it looks like th
I'm seeing something similar. Our task queues are also filling up with
tasks and our traffic hasn't changed. For us, it looks like this started
about a week ago. Our tasks are not generating more errors than normal.
Our tasks are run by different instances than our front-end website. Our
Yes, I am seeing exactly the same. It started at 11:10 PST. Most of our
searches are failing but some are succeeding. It seems to apply to certain
indexes. We have some search indexes where we are seeing ~100% success rate
and some where we are seeing 100% failure.
On Wednesday, August 12,
As of 11:46 PST, my searches are back to normal.
On Wednesday, August 12, 2015 at 11:42:29 AM UTC-7, David Fischer wrote:
Yes, I am seeing exactly the same. It started at 11:10 PST. Most of our
searches are failing but some are succeeding. It seems to apply to certain
indexes. We have some
As of just a couple minutes ago, this appeared on the status
page: https://status.cloud.google.com/
On Wednesday, August 12, 2015 at 11:51:18 AM UTC-7, Mike Schlanser wrote:
Yeah, same here. Seems to be back to normal now.
On Wednesday, August 12, 2015 at 2:46:53 PM UTC-4, David Fischer
I'm seeing the same problem on Appengine production (and not with
dev_appserver) and I'm using the same Twitter library. However, I was
seeing some tweets succeeding and some failures. After another user in the
Twitter Dev forum posted, I looked at the content of the tweets. The
failing tweets
14 matches
Mail list logo
