- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
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 1h 22m it lasted.
Anything that failed between 2017-09-14 19:03 UTC and 2017-09-14 20:25 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 5
- investigating
We are currently investigating this issue.
provider
- identified
Appears that increased error rate is connected with increased error rate for S3.
provider
- monitoring
Error rates are decreasing.
provider
- monitoring
Our diagnostic tools show that all subsystems are back to normal. We continue monitoring of the situation.
provider
- resolved
This incident has been resolved.
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-dd991917bf
Is Uploadcare still down?
No, this incident was resolved 2017-09-14 20:25 UTC. For Uploadcare's live state, see https://down.guide/providers/uploadcare.
How long did it last?
1h 22m, from 2017-09-14 19:03 UTC to 2017-09-14 20:25 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.