Cloudinary: Incorrect reported usage in the report
Timeline of updates
- resolved
The numbers in the Reports page was corrected. If you do suspect there's still an issue with the numbers in your Reports page, please open a support ticket at https://support.cloudinary.com/hc/en-us/requests/new (opens in new tab) and we'll be happy to help further.
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: minor) posted by Cloudinary, started 2020-08-27 19:00 UTC, resolved after 3 d, 1 update(s).
- Title
- Incorrect reported usage in the report
- Vendor
- Cloudinary
- Date
- URL
- https://rewindex.com/company/cloudinary/incidents/v2lhh59r1488
Cloudinary profileRecent Cloudinary incidentsAll outages on August 27, 2020Cloudinary in August 2020MarkdownJSON