4 ms·

It's interesting to note the cascading effects. For example, I was immediately hit by three problems: * Slack file sharing no longer works, hangs forever (no w

It's interesting to note the cascading effects. For example, I was immediately hit by three problems: * Slack file sharing no longer works, hangs forever (no way to hide the permanently rolling progress bar except quitting) * Github.com file uploads (e.g. dropping files into a Github issue) don't work. * Imgur.com is completely down. * Docker Hub seems to be unavailable. Can't pull/push images.

Ph4nt0m 10y ago
* Hipchat file sharing no longer works, hangs forever * CircleCI cannot access artifacts
mcphilip 10y ago
A doctor's office that's unable to process patients due to the outage: https://mobile.twitter.com/drjincali/status/836657863887998976 https://mobile.twitter.com/drjincali/status/8366578638879989...
- cookiecaper 10y ago
  I mean, that's not really AWS's problem, is it? Outages happen. If you have a mission-critical service like health care, you really shouldn't write systems with single points of failure like this, especially not systems that depend on something consumer-grade like S3. This appears to be a normal doctor's office where there are routine appointments. Emergencies would be referred to the ER anyway. And while I obviously don't know the details of how his office is run, you'd think that you could get by on a pen-and-paper fallback to manage the office. Maybe that's an advantage to keeping experienced office staff on board.
  - mcphilip 10y ago
    I work in the healthcare industry and there's a big push from AWS into offering HIPAA compliant services for things like patient records. It's becoming much more common to tie in third party services into electronic healthcare software. Obviously no mission critical system should have a single point of failure and doctor's offices should have fallback plans for handling service outages, but most care providers don't have staff onsite with the technical expertise to understand the extent of the coupling. I'm just closely watching this space and found that tweet interesting in relation to the parent comment's remark about realizing the scope of this S3 outage. There's no blame unique to AWS here, but it is becoming an increasingly important piece of plumbing in the industry.
    - inferiorhuman 10y ago
      Fine. But that's just buying into one of the very common misconceptions about AWS (or any hosting provider), no? This idea that Amazon sells a fault tolerant product. They don't. Amazon sells you tools that can make a fault tolerant product, but making your own product resilient is entirely upon you.
  - ArlenBales 10y ago
    Whatever software that doctor is using should have been built with offline capability (local storage, syncs to servers when network connectivity is restored).
chrisper 10y ago
Heroku has issues too.
cylinder 10y ago
AWS - too big to fail.
azernik 10y ago
My own service was running just fine, until I tried to push out a (fairly critical) bugfix. Sadly, my deploy procedure relies on my build server pushing docker images to quay.io, and prod servers pulling them back down from quay.io, and quay.io hosts their Docker registry in S3. Time to make some apologies and excuses to my users...
jasonsync 10y ago
We're still up and running (Sync.com) if you need to share some files.
pweissbrod 10y ago
i was unable to purchase cat food at my local pet store with a credit card because their POS software was down
monksy 10y ago
On the upside.. no one is stealing more data from the CloudPets thing we were talking about earlier today.
kevin2r 10y ago
I was also trying to open gotomeeting web client, no luck.
- smackfu 10y ago
  Zoom was down too.

Ph4nt0m 10y ago

* Hipchat file sharing no longer works, hangs forever * CircleCI cannot access artifacts

mcphilip 10y ago

A doctor's office that's unable to process patients due to the outage: https://mobile.twitter.com/drjincali/status/836657863887998976 https://mobile.twitter.com/drjincali/status/8366578638879989...

cookiecaper 10y ago
I mean, that's not really AWS's problem, is it? Outages happen. If you have a mission-critical service like health care, you really shouldn't write systems with single points of failure like this, especially not systems that depend on something consumer-grade like S3. This appears to be a normal doctor's office where there are routine appointments. Emergencies would be referred to the ER anyway. And while I obviously don't know the details of how his office is run, you'd think that you could get by on a pen-and-paper fallback to manage the office. Maybe that's an advantage to keeping experienced office staff on board.
- mcphilip 10y ago
  I work in the healthcare industry and there's a big push from AWS into offering HIPAA compliant services for things like patient records. It's becoming much more common to tie in third party services into electronic healthcare software. Obviously no mission critical system should have a single point of failure and doctor's offices should have fallback plans for handling service outages, but most care providers don't have staff onsite with the technical expertise to understand the extent of the coupling. I'm just closely watching this space and found that tweet interesting in relation to the parent comment's remark about realizing the scope of this S3 outage. There's no blame unique to AWS here, but it is becoming an increasingly important piece of plumbing in the industry.
  - inferiorhuman 10y ago
    Fine. But that's just buying into one of the very common misconceptions about AWS (or any hosting provider), no? This idea that Amazon sells a fault tolerant product. They don't. Amazon sells you tools that can make a fault tolerant product, but making your own product resilient is entirely upon you.
- ArlenBales 10y ago
  Whatever software that doctor is using should have been built with offline capability (local storage, syncs to servers when network connectivity is restored).

chrisper 10y ago

Heroku has issues too.

cylinder 10y ago

AWS - too big to fail.

azernik 10y ago

My own service was running just fine, until I tried to push out a (fairly critical) bugfix. Sadly, my deploy procedure relies on my build server pushing docker images to quay.io, and prod servers pulling them back down from quay.io, and quay.io hosts their Docker registry in S3. Time to make some apologies and excuses to my users...

jasonsync 10y ago

We're still up and running (Sync.com) if you need to share some files.

pweissbrod 10y ago

i was unable to purchase cat food at my local pet store with a credit card because their POS software was down

monksy 10y ago

On the upside.. no one is stealing more data from the CloudPets thing we were talking about earlier today.

kevin2r 10y ago

I was also trying to open gotomeeting web client, no luck.

smackfu 10y ago
Zoom was down too.