# JFrog: S3 outage reported by AWS in USE

> JFrog status incident “S3 outage reported by AWS in USE” on 2017-02-28: impact minor (vendor’s label), 5.3 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/jfrog/incidents/2rr4qjqbdntt
Last updated: 2017-02-28T22:56:00Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2017-02-28 17:40 UTC · Resolved: 2017-02-28 22:56 UTC · Duration: 5.3 h
- Updates: 1
- [Vendor status page: https://status.jfrog.io/incidents/2rr4qjqbdntt](https://status.jfrog.io/incidents/2rr4qjqbdntt)
- [Company: JFrog](https://rewindex.com/company/jfrog.md)

## Timeline of updates

- **resolved** 2017-02-28 22:56 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/jfrog/incidents/2rr4qjqbdntt
- Citation: JFrog, “S3 outage reported by AWS in USE” (2017-02-28 17:40 UTC). Archived by Rewindex: https://rewindex.com/company/jfrog/incidents/2rr4qjqbdntt (CC BY 4.0).
- Markdown link: `[JFrog: S3 outage reported by AWS in USE (2017-02-28)](https://rewindex.com/company/jfrog/incidents/2rr4qjqbdntt)`


---
Canonical: https://rewindex.com/company/jfrog/incidents/2rr4qjqbdntt · Markdown: https://rewindex.com/company/jfrog/incidents/2rr4qjqbdntt.md · JSON: https://rewindex.com/api/v1/companies/jfrog/incidents/2rr4qjqbdntt · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T13:58:07.579Z