atom / atom.io

🌐 A place for feedback on the atom.io website and package API
161 stars 98 forks source link

Atom.io downloads are not working until Amazon S3 outage is resolved #112

Closed skull-squadron closed 7 years ago

skull-squadron commented 7 years ago

https://atom-installer.github.com/v1.14.4/atom-mac.zip?s=1488270996&ext=.zip on https://atom.io/

Error 503 Connection timed out

Connection timed out

Guru Mediation:

Details: cache-ams4124-AMS 1488309373 3483990621

Varnish cache server

Also, this presents in the app with the following error:

There was an error checking for updates.

Update download failed. The server sent an invalid response. Try again later.
skull-squadron commented 7 years ago

Temporary workaround: Download from github directly. Github also uses S3 US-EAST-1, so they're down too.

BinaryMuse commented 7 years ago

This is due to an S3 outage:

Update at 10:33 AM PST: We're continuing to work to remediate the availability issues for Amazon S3 in US-EAST-1. AWS services and customer applications depending on S3 will continue to experience high error rates as we are actively working to remediate the errors in Amazon S3.

I'll leave this open for now (cc @lee-dohm) so others can find it until things are resolved.

skull-squadron commented 7 years ago

Ah thanks.

danielesegato commented 7 years ago

Do you have any temporary mirror / alternatives for downloading installers?

rsese commented 7 years ago

Do you have any temporary mirror / alternatives for downloading installers?

I don't believe so, looks like there's an issue with this request though /cc https://github.com/atom/apm/issues/488.

BinaryMuse commented 7 years ago

This should be resolved; only writes to S3 are still broken.

rsese commented 7 years ago

Do you have any temporary mirror / alternatives for downloading installers?

I don't believe so, looks like there's an issue with this request though /cc atom/apm#488.

Sorry just realized you were asking about installers not packages @danielesegato :bow:

skull-squadron commented 7 years ago

All good now. AWS status page was also out-of-date because it depended upon S3 US-EAST-1 az. (Circular-dependency, whoops.)