The latest Tweets from App Engine (@app_engine). Hey everyone — we’ve updated our handle to @googlecloud, hit us up there! Love, Google App Engine. Google Cloud Platform outage brings down Spotify, Snapchat, and more Google App Engine: Build and deploy applications on a fully. Snapchat, Spotify, Discord, and Pokémon Go all went down for portions of the Google Cloud’s app engine took out several popular apps.
|Published (Last):||12 May 2016|
|PDF File Size:||16.69 Mb|
|ePub File Size:||16.22 Mb|
|Price:||Free* [*Free Regsitration Required]|
Google Cloud issues trip up Snapchat, Spotify and others Sign in to comment Be respectful, keep it civil and stay on topic. Google did no such thing. The billing eventually went down but to this day we have no way of knowing which one outaage our changes fixed it.
For the first couple oufage years things worked fine, we had some issues to be sure e. Multiple projects have been in progress to allow us to further scale our traffic routers, reducing the likelihood of cascading failures in the future.
The cause of the issue is unclear, but problems began at First published July 17, 1: We will follow up directly with the few remaining affected applications. About today’s App Engine outage Friday, October 26, As designed, App Engine automatically redirected requests to other datacenters away from the overload – which reduced the error rate. We will provide more information by This was a disaster since we were getting a bill so large it nearly wiped our revenue.
Be respectful, keep it civil and stay on topic.
Why (and How) we Left App Engine After it Almost Destroyed Us
We delete comments that violate our policywhich we encourage you to read. This morning we failed to live up to our promise, and Google App Engine applications experienced increased latencies and time-out errors. Since launching the High Replication Datastore in JanuaryApp Engine has not experienced appenbine widespread system outage. We will provide another status update by The company also said it would provide a more detailed analysis of what happened after the investigation.
Check us out on Stack Overflow.
Fixing this at Clearly something in our code broke, right? Discussion threads can be closed at any time at our discretion. Your trust is important to us and we will continue to all we can to earn and keep that trust. We know you rely on App Engine to create applications that are easy to develop and manage without having to worry about downtime. We still liked app engine after that and we even did a talk at JavaOne where we discussed how helpful it has been for us to scale our business rapidly.
We will also change how applications are otuage so that the traffic routers are not called and also modify that the system’s retry behavior so that it cannot trigger this type of failure. Thanks for your reports! We’ve identified the cause of our connectivity issues to GCPcloud which is also impacting other popular apps such as SnapChat. Being bootstrapped and in the early stages of monetization this had the potential of sending us into ouyage.
For additional information on these services, please visit cloud.
Current data indicates that Applications in us-central are affected by this issue. PT, the company updated the status, indicating it had initiated a fix.
Google Cloud Platform Blog: About today’s App Engine outage
A Google representative confirmed that the issues had been resolved. PT, the company later wrote. We are still investigating the issue with App Engine apis being unavailable.
We apologize for this outage, and in particular for its duration and severity. As part of this procedure, we first move a proportion of apps to a new datacenter in which capacity has already been provisioned.
Incidents reported in the last 365 days
There is no need to make any code or configuration changes to your applications. On Thursday 11 August from CNET’s best of Open-source, multiplayer, dedicated game-server hosting built on Kubernetes Why you should pick strong consistency, whenever possible. Don’t show this again. If you are experiencing an issue not listed here, please contact Support. We then gracefully drain traffic from an equivalent proportion of servers in the downsized datacenter in order to reclaim resources.
Never miss a story from Hacker Noonwhen you sign up for Medium. I did meet with a couple of Google reps at their local offices before upgrading to gold and had some discussions about app engine with them but mostly abstract line of business talks.
We know that hundreds of thousands of developers rely on App Engine to provide a stable, scalable infrastructure for their applications, and we will continue to improve our systems and processes to live up to this expectation.
Here’s what I learned. We are experiencing an issue with App Engine apis being unavailable beginning at Thursday, Some manually-scaled instances started up slowly, resulting in the App Engine system retrying the start requests multiple times which caused a spike in CPU load on the traffic routers. We know that you choose to run your applications on Google App Engine papengine obtain flexible, reliable, high-performance service, and in this incident we have not delivered the level of reliability for which we strive.
To prevent issues like the downtime we had from recurring we decided to pay for gold support extra USD per month so such issues will not recur.
But first some background, our startup uses a very complex set of servers hosted almost everywhere thru the years… From Azure, to AWS, Linode, Digital Ocean appengkne many others… The reason for this complexity relates to our core product which requires domain specific servers. Although there was sufficient capacity in the system to handle the load, the traffic routers did not immediately recover due to retry behavior which amplified the volume of requests.