JFrog: Outage in AWS USE1
Timeline of updates
- resolved
There was an outage in this region because of a sharp spike in memory on the underlying database resource. This resulted in JFrog platform unable to connect to the DB for a subset of customers. The incident is resolved now.
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 2020-10-02 14:15 UTC, resolved after 0 min, 1 update(s).
- Title
- Outage in AWS USE1
- Vendor
- JFrog
- Date
- URL
- https://rewindex.com/company/jfrog/incidents/l2kpr2t14c36
JFrog profileRecent JFrog incidentsAll outages on October 2, 2020JFrog in October 2020MarkdownJSON