Uploadcare services have degraded performance

What to do

• Check whether your product depends on Uploadcare. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 5h 55m it lasted.

  Anything that failed between 2017-02-28 17:48 UTC and 2017-02-28 23:43 UTC may need a replay.

• Subscribe to Uploadcare's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=uploadcare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Uploadcare 8

1. investigatingFeb 28, 2017, 5:48 PM UTC

   Our CDN is down. Investigating.

   provider

2. identifiedFeb 28, 2017, 5:58 PM UTC

   AWS S3 is experiencing increased error rates that results in all of our buckets going AWOL.

   provider

3. identifiedFeb 28, 2017, 9:24 PM UTC

   AWS has fixed working with existing S3 objects, so CDN and subset of REST API are working at the moment. More details on AWS status: https://status.aws.amazon.com/

   provider

4. monitoringFeb 28, 2017, 10:33 PM UTC

   AWS has reported that everything is green. We're working on recovering affected Uploadcare components. Currently, everything should work but higher latency and error rate are expected.

   provider

5. monitoringFeb 28, 2017, 10:48 PM UTC

   AWS Autoscaling is still down, we're deploying new instances manually.

   provider

6. identifiedFeb 28, 2017, 10:54 PM UTC

   Upload API went down.

   provider

7. monitoringFeb 28, 2017, 10:59 PM UTC

   Upload API is up again. We continue monitoring all components.

   provider

8. resolvedFeb 28, 2017, 11:43 PM UTC

   Currently, Uploadcare service is fully working. We continue monitoring the situation closely.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.