But today there was an announcement for this issue in the downtime-notify 
group, so either Google is improving its communication or this was wide spread 
enough that could not be ignored.

> Date: February 24, 2015 at 3:24:42 AM PST
> Subject: Elevated latency in deploying applications to App Engine
> From: Google Cloud Platform Status <nore...@cloud-status-prod.appspotmail.com>
> To: google-appengine-downtime-not...@googlegroups.com
> Reply-To: google-appengine-downtime-not...@googlegroups.com
> 
> Starting at Tuesday, 2015-02-24 00:00, Google App Engine showed increased 
> latency when deploying applications possibly leading to timeouts. This 
> incident with Google App Engine deployment was resolved as of Tuesday, 
> 2015-02-24 01:54 (all times are in US/Pacific). We apologize for the 
> inconvenience and thank you for your patience and continued support. Please 
> rest assured that system reliability is a top priority at Google, and we are 
> making continuous improvements to make our systems better.
> 
> -- 


> On Feb 24, 2015, at 3:14 AM, Gerrit Vermeulen <ger...@nomanini.com> wrote:
> 
> This seems to be fixed for us now across all our apps. What on earth...?
> 
> On Tuesday, February 24, 2015 at 11:29:28 AM UTC+2, Gerrit Vermeulen wrote:
> Having a similar issue with our apps as well. Everything seems to work fine 
> until "Checking if deployment succeeded", at which point it just keeps 
> checking every minute until it times out. This started happening today - we 
> first noticed it at 08h30 UTC.
> 
> 11:11 AM Starting deployment.
> 11:11 AM Checking if deployment succeeded.
> 11:11 AM Will check again in 1 seconds.
> 11:11 AM Checking if deployment succeeded.
> 11:11 AM Will check again in 2 seconds.
> 11:11 AM Checking if deployment succeeded.
> 11:11 AM Will check again in 4 seconds.
> 11:11 AM Checking if deployment succeeded.
> 11:11 AM Will check again in 8 seconds.
> 11:12 AM Checking if deployment succeeded.
> 11:12 AM Will check again in 16 seconds.
> 11:12 AM Checking if deployment succeeded.
> 11:12 AM Will check again in 32 seconds.
> 11:12 AM Checking if deployment succeeded.
> 11:12 AM Will check again in 60 seconds.
> 11:13 AM Checking if deployment succeeded.
> 11:14 AM Will check again in 60 seconds.
> 11:15 AM Checking if deployment succeeded.
> 11:15 AM Will check again in 60 seconds.
> 11:16 AM Checking if deployment succeeded.
> 11:16 AM Will check again in 60 seconds.
> 11:17 AM Checking if deployment succeeded.
> 11:17 AM Will check again in 60 seconds.
> 11:18 AM Checking if deployment succeeded.
> 11:18 AM Will check again in 60 seconds.
> 11:19 AM Checking if deployment succeeded.
> 11:19 AM Will check again in 60 seconds.
> 11:20 AM Checking if deployment succeeded.
> 11:20 AM Will check again in 60 seconds.
> 11:21 AM Checking if deployment succeeded.
> 11:21 AM Will check again in 60 seconds.
> 11:22 AM Checking if deployment succeeded.
> 11:22 AM Will check again in 60 seconds.
> 
> On Tuesday, February 24, 2015 at 9:04:46 AM UTC+2, Vinny P wrote:
> On Mon, Feb 23, 2015 at 3:54 PM, aleena davy <arlet...@gmail.com <>> wrote:
> app id : aleenadavy1. Is there any way to solve this issue?
> 
> 
> 
> 
> When you say deployment is taking forever, do you mean deployment takes a 
> long time but eventually deploys your app, or deployment takes forever and 
> never finishes the process?
> 
> For the first situation, don't worry about it. That happens when the Google 
> servers are busy but your deployment will go through sooner or later. If 
> you're experiencing the second situation: how long have you been unable to 
> deploy, and have you changed anything about your Google account recently?
>  
>  
> -----------------
> -Vinny P
> Technology & Media Consultant
> Chicago, IL
> 
> App Engine Code Samples: http://www.learntogoogleit.com 
> <http://www.learntogoogleit.com/>
>  
>  
> 
> On Mon, Feb 23, 2015 at 3:54 PM, aleena davy <arlet...@gmail.com <>> wrote:
> 
> 
>  
> <https://lh4.googleusercontent.com/-I7jXN5x21gk/VOuhN6UV6kI/AAAAAAAABiI/BuclbyfRhc8/s1600/stuck.PNG>
> app id : aleenadavy1. Is there any way to solve this issue?
> 
> 
> 
> 
> 
>  
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-appengine+unsubscr...@googlegroups.com 
> <mailto:google-appengine+unsubscr...@googlegroups.com>.
> To post to this group, send email to google-appengine@googlegroups.com 
> <mailto:google-appengine@googlegroups.com>.
> Visit this group at http://groups.google.com/group/google-appengine 
> <http://groups.google.com/group/google-appengine>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/706afee2-ab25-480c-864f-25a681f28115%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/google-appengine/706afee2-ab25-480c-864f-25a681f28115%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.


PK
p...@gae123.com




-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8B73B130-1381-465D-A0D1-AE86380248F0%40gae123.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to