- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Uploadcare. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 15m it lasted.
Anything that failed between 2017-04-10 11:17 UTC and 2017-04-10 12:32 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 3
- investigating
Automatic file copying is not working at the moment, we're investigating the cause of this.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
We have found and fixed the issue with backing up of stored files to S3. All files that were not backed up during the incident will be backed up eventually. Automatic copying of uploaded files to S3 buckets (Custom storage) was not affected by the issue.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c4817b78e8
Is Uploadcare still down?
No, this incident was resolved 2017-04-10 12:32 UTC. For Uploadcare's live state, see https://down.guide/uploadcare.
How long did it last?
1h 15m, from 2017-04-10 11:17 UTC to 2017-04-10 12:32 UTC, by the times Uploadcare posted.
What caused it?
Uploadcare hasn't published a root cause. If it does, it shows here.
Where does this come from?
Uploadcare's official status page, https://status.uploadcare.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.