Cloudinary: Delivery slowdown
Timeline of updates
- resolved
"Rush hour" slowdowns which affected the service daily since Tuesday, did not occur today. During the previous hours, we've made changes to our Load balancer's scaling configuration with the help of AWS support, tested and confirmed that the changes work. Now that the critical load hours have passed, we conclude that the solution worked.
From Cloudinary’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.cloudinary.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Cloudinary, started 2016-01-14 20:18 UTC, resolved after 23 h, 1 update(s).
- Title
- Delivery slowdown
- Vendor
- Cloudinary
- Date
- URL
- https://rewindex.com/company/cloudinary/incidents/lfcmcpgmmmdf
Cloudinary profileRecent Cloudinary incidentsAll outages on January 14, 2016Cloudinary in January 2016MarkdownJSON