rewindex

CompaniesSnykIncidents

Snyk: Reporting Freshness Delay

No impact listedStatus: resolvedStarted Resolved (34 d)1 updatestatus.snyk.io (opens in new tab)

Timeline of updates

  1. resolved

    We've implemented several fixes to bring our reporting freshness well within SLO, and improve its robustness. We're considering this issue resolved.

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-02-01 14:13 UTC, resolved after 34 d, 1 update(s).

Title
Reporting Freshness Delay
Vendor
Snyk
Date
URL
https://rewindex.com/company/snyk/incidents/4cm5gc420gxc

Snyk profileRecent Snyk incidentsAll outages on February 1, 2022Snyk in February 2022MarkdownJSON