Snyk: Reporting freshness delayed
Timeline of updates
- resolved
Reporting freshness is no longer a problem and the incident is resolved. We are working on fixing past data and as a result, some customers may see: - Data dips on the Issues Over time graph between the 5th and 8th of July 2022 - That the exposure window graph is possibly not accurate from 5th July 2022 to the present day UPDATE: - The past data has been fixed as of 10:30 GMT, 14.07.2022.
From Snyk’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.snyk.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Snyk, started 2022-07-04 18:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Reporting freshness delayed
- Vendor
- Snyk
- Date
- URL
- https://rewindex.com/company/snyk/incidents/8rt3cb0782bb
Snyk profileRecent Snyk incidentsAll outages on July 4, 2022Snyk in July 2022MarkdownJSON