371–380 of 630 posts
When talking about GCE being down please also mention what regions you are talking about
us-central1 us-west1 us-west2 is what I’ve heard so far. east seems to be OK, and Europe too
Edit: just got one email from the downtime, so perhaps my initial conclusion was incorrect
Now is a good time to point out that the SLA of Google Cloud Storage only covers HTTP 500 errors: https://cloud.google.com/storage/sla . So if the servers are not responding at all then it's not covered by the SLA. I've brought this to their attention and they basically responded that their network is never down.
Cloud services live and die by their reputation, so I'd be shocked if Google ever tried to get out of following an SLA contract based on a technicality like that. It would be business suicide, so it doesn't seem like something to be too worried about?
Earlier quoted context omitted.
I have an instance in us-west-1 (Oregon) which is up, but an instance in us-west-2 (Los Angeles) which is down. Not sure if that means Oregon is unaffected though.
us-west-1 is Northern California (Bay area). us-west-2 is Oregon (Boardman).
Earlier quoted context omitted.
I use both services heavily at work. The networking in GCP is terrible. We experience minor service degradation multiple times a month due to networking issues in GCP (elevated latency, errors talking to the DB, etc). We've even had cases where there was packet corruption at the bare metal layer, so we ended up storing a bunch of garbage data in our caches / databases. Also, the networking is less understandable on G…
> We've even had cases where there was packet corruption at the bare metal layer, I'd love to know how this happens in the modern world. I've seen it myself only once (not GCP, but our own network with cisco equipment.) Is something in the chain not checking the packet's CRC?
That's in own datacenters, not cloud.
Earlier quoted context omitted.
And the illusion of superiority over non cloud offerings.
I keep trying to explain to people that our customers don’t care that there is someone to blame they just want their shit to work. There are advantages to having autonomy when things break. There’s a fine line or at least some subtlety here though. This leads to some interesting conversations when people notice how hard I push back against NIH. You don’t have to be the author to understand and be able to fiddle with…
Earlier quoted context omitted.
To clarify something: this outage doesn’t appear to be global, but it is hitting us particularly hard in parts of the US. So for the folks with working VMs in Mumbai, you’re not crazy. But for everyone with sadness in us-central1, the team is on it.
Some services are still impacted globally. Gmail over IMAP is unreachable for me. (Edit: gmail web is fine)
Earlier quoted context omitted.
Gosh, this was so scary... I thought someone had hacked in and deleted everything... I hope they come back. This is still pretty scary
[I am the Cloud SQL tech lead] This is a networking issue, and your data is safe. Cloud SQL stores instance metadata regionally, so it shares a failure domain with the data it describes. When the region is down or inaccessible, instances are missing from the list results, but that doesn't say anything about the instance availability from within region.
Earlier quoted context omitted.
> For the downvoters, please just link here the proof if you disagree. https://wasabi.com/
How can they possibly guarantee eleven nines? Considering I’ve never heard of this company and they offer such crazy-sounding improvements over the big three, it feels like there should be a catch.