- Level
- confirmed
- Worst impact
- Operational
- Uploadcare says
- 2016-12-05 19:00 to 22:00 UTC (3h)
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 10h 6m it lasted.
Anything that failed between 2016-12-05 22:33 UTC and 2016-12-06 08:39 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 2
- monitoring
We've experienced CDN service degradation for some of our end users that get content from edge servers in Moscow, Russia. We've identified and resolved the issue. Currently, we're monitoring the situation. The incident took place between 19:00 and 22:00 UTC.
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-76dad35256
Is Uploadcare still down?
No, this incident was resolved 2016-12-06 08:39 UTC. For Uploadcare's live state, see https://down.guide/providers/uploadcare.
How long did it last?
10h 6m, from 2016-12-05 22:33 UTC to 2016-12-06 08:39 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.