I was experienced this issue with my spotify app. Initially thought, it was my internet issue lol.
Error 404 (Not Found)
151–160 of 197 posts
Re: Error 404 (Not Found)
#152Half the internet is down because of a Google Cloud global issue on their load balancers, including Spotify and Etsy and GCP status is all green: https://status.cloud.google.com If you ever wondered why GCP is a distant third runner in the enterprise cloud space, here is your answer.
Expecting an instant public post is a bit unrealistic. They had a post up just over 20 minutes after the incident start, which is not that crazy, given that they needed time to triage all of the alarms and understand which component was actually breaking and confirm some technically correct information around it, even if the actual internal incident response can run without the public post.
Re: Error 404 (Not Found)
#153Etsy is 404 too: https://www.etsy.com Seems to be a bigger issue. edit: Nest is down too: http://nest.com Fitbit.com is 404 too: https://www.fitbit.com Big GCP issue? edit2: Downdetector.com shows multiple website and services as down, including Pokemon GO or Rocket League. GCP status page is still green all over the board: https://status.cloud.google.com 19:10 CET update: Some websites are coming back, including spo…
Another cloud issue? Wow, nearly a week's uptime. https://news.ycombinator.com/item?id=29197832
Re: Error 404 (Not Found)
#154Re: Error 404 (Not Found)
#155Affecting us. Busiest time of the year and now down 20 min. It's the Global Load Balancer, so god knows what bit of the global edge has been taken out.
At least you don't run your own servers
Re: Error 404 (Not Found)
#156Half the internet is down because of a Google Cloud global issue on their load balancers, including Spotify and Etsy and GCP status is all green: https://status.cloud.google.com If you ever wondered why GCP is a distant third runner in the enterprise cloud space, here is your answer.
The big three cloud platforms all have this issue of delayed status updates. Why do you think it's just GCP?
...and there's a reason for that. Automations to update the status page are rarely acceptable, since the status page statuses have legal and financial implications. Therefore, the IM usually has to update it (or tell someone to update it). But, realistically, when you get paged, you first need to figure out what exactly is wrong and at least a vague idea of why. Then, you need to tell someone to update the page. Then, it gets updated.
The status page will always lag the outage. It's not a conspiracy.
Re: Error 404 (Not Found)
#157This is clearly the hottest thing on HN right now, and it was bumped from #1 to #6, anyone knows why? Is it some kind of bot protection?
User flags, because outages are a fact of everyday life.
Re: Error 404 (Not Found)
#158Etsy is 404 too: https://www.etsy.com Seems to be a bigger issue. edit: Nest is down too: http://nest.com Fitbit.com is 404 too: https://www.fitbit.com Big GCP issue? edit2: Downdetector.com shows multiple website and services as down, including Pokemon GO or Rocket League. GCP status page is still green all over the board: https://status.cloud.google.com 19:10 CET update: Some websites are coming back, including spo…
I’m assuming all these websites point to Google web frontend servers and for some reason it’s no longer able to map the Host header to the proper backend to proxy to.
For what it's worth, not only HTTP(S) load balancers went down. We have a couple TCP proxy load balancers that went down too.
Re: Error 404 (Not Found)
#159back up as of now (10:10a PDT) This sure makes it easy to know who is hosted by google by going to downdetector.com.
Hmm it shows the same spike for instagram and aws as well. Would be funny to me if something on their end depends on GCP.
https://downdetector.com/status/aws-amazon-web-services/
https://downdetector.com/status/instagram/
Re: Error 404 (Not Found)
#160Half the internet is down because of a Google Cloud global issue on their load balancers, including Spotify and Etsy and GCP status is all green: https://status.cloud.google.com If you ever wondered why GCP is a distant third runner in the enterprise cloud space, here is your answer.
Expecting an instant public post is a bit unrealistic. They had a post up just over 20 minutes after the incident start, which is not that crazy, given that they needed time to triage all of the alarms and understand which component was actually breaking and confirm some technically correct information around it, even if the actual internal incident response can run without the public post.
It's Google though.. they stop automating everything?
At least make the screen not show all green or something automatically