- Level
- confirmed
- Worst impact
- Degraded
- Components
- CDN
- Down Index
- 21of 100
What to do
Check whether you use Uploadcare CDN. 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 41m it lasted.
Anything that failed between 2018-05-15 14:32 UTC and 2018-05-15 16:13 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
Our CDN origin fleet is experiencing increased error rate.
provider
- monitoring
The issues were caused by network connectivity problems in AWS east-1 region.
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-31dceca3ac
Is Uploadcare still down?
No, this incident was resolved 2018-05-15 16:13 UTC. For Uploadcare's live state, see https://down.guide/uploadcare.
How long did it last?
1h 41m, from 2018-05-15 14:32 UTC to 2018-05-15 16:13 UTC, by the times Uploadcare posted.
What was affected?
Uploadcare named CDN.
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.