JFrog: S3 outage reported by AWS in USE
Timeline of updates
- resolved
2:08 PM PST / 5:08 PM EST Operations have recovered. We believe there was no data loss from the incident and the only impact would have been on failed GET requests for artifacts.
From JFrog’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.jfrog.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by JFrog, started 2017-02-28 17:40 UTC, resolved after 5.3 h, 1 update(s).
- Title
- S3 outage reported by AWS in USE
- Vendor
- JFrog
- Date
- URL
- https://rewindex.com/company/jfrog/incidents/2rr4qjqbdntt
JFrog profileRecent JFrog incidentsAll outages on February 28, 2017JFrog in February 2017MarkdownJSON