JFrog: Artifactory degraded performance in AWS EUC1
Timeline of updates
- resolved
We identified the cause of the slowness/degraded performance to be related to load on the instances. We have rebalanced the instances, so that the load is distributed evenly and verified that the instance is back to normal. We will work on adding additional monitoring to our infrastructure, which should help us to prevent these issues from happening again.
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 2018-05-30 17:03 UTC, resolved after 1.1 h, 1 update(s).
- Title
- Artifactory degraded performance in AWS EUC1
- Vendor
- JFrog
- Date
- URL
- https://rewindex.com/company/jfrog/incidents/ydm3qf8r7dz3
JFrog profileRecent JFrog incidentsAll outages on May 30, 2018JFrog in May 2018MarkdownJSON