JFrog: Outage affecting a subset of customers in AWS USE1
Timeline of updates
- resolved
There was a sudden spike of connections to one of the databases in the region which caused an outage for a small set of customers. The DB recovered by itself and the incident is resolved now. The technical teams are working towards further reducing the load on this database and prevent future spikes.
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: none) posted by JFrog, started 2020-10-15 16:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Outage affecting a subset of customers in AWS USE1
- Vendor
- JFrog
- Date
- URL
- https://rewindex.com/company/jfrog/incidents/9p9q8pbtzzsx
JFrog profileRecent JFrog incidentsAll outages on October 15, 2020JFrog in October 2020MarkdownJSON