- Level
- confirmed
- Worst impact
- Major outage
- Components
- CDN
- Regions
- us
- Down Index
- 46of 100
What to do
Check whether you use Uploadcare CDN in us. 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 3h 35m it lasted.
Anything that failed between 2019-07-19 15:59 UTC and 2019-07-19 19:35 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.
Root cause
Create an service that could be used to quickly redirect ucarecdn.com (http://ucarecdn.com) traffic to backup CDNs in case of any issues with the main one \(not only due to certificates\)
Category: Certificate expiry
Read the postmortemUpdates from Uploadcare 5
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
- postmortem
What happened On 19th July 2019 at 15:30 UTC certificate used to serve traffic from ucarecdn.com (http://ucarecdn.com) and www.ucarecdn.com (http://www.ucarecdn.com) has expired. All HTTPS traffic to these domains effectively stopped. We were able to quickly \(within minutes\) redirect www.ucarecdn.com (http://www.ucarecdn.com) traffic to alternative CDN provider with proper certificate installed. It took us approximately 105 minutes since start of the incident to fix the issue with ucarecdn.com (http://ucarecdn.com).  Why that happened 1. Our CDN partner's certificate management system failed to renew the certificate in question and needed an input from our team. 2. It did sent an email 5 days prior to expiration requesting manual input. 3. This email wasn't noticed, because it was sent to a team member that was off the grid on vacation. What we should do to improve 1. Change notification system settings, so any issues with certificates with our CDN partners are sent to a team, not a person \[done\] 2. Use 3rd party service to monitor certificate expiration and other settings \[done\] 3. Use CDN partner's APIs to actively and automatically monitor certificates \[in progress\] 4. Create an service that could be used to quickly redirect ucarecdn.com (http://ucarecdn.com) traffic to backup CDNs in case of any issues with the main one \(not only due to certificates\)
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-7d214e8496
Is Uploadcare still down?
No, this incident was resolved 2019-07-19 19:35 UTC. For Uploadcare's live state, see https://down.guide/providers/uploadcare.
How long did it last?
3h 35m, from 2019-07-19 15:59 UTC to 2019-07-19 19:35 UTC, by the times Uploadcare posted.
What was affected?
Uploadcare named CDN in us.
What caused it?
Certificate expiry. Uploadcare wrote: "Create an service that could be used to quickly redirect ucarecdn.com (http://ucarecdn.com) traffic to backup CDNs in case of any issues with the main one \(not only due to certificates\)" The postmortem: http://stspg.io/83c90dd88
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.