JFrog: Artifactory slowness/degraded performance in AWS USE1 region on May 29 between 11:45 PM Pacific Time to 1:00 PM Pacific Time
Timeline of updates
- resolved
The source of the issue was found to be with a specific Tomcat process. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent this 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: none) posted by JFrog, started 2018-05-30 21:42 UTC, resolved after 22 h, 1 update(s).
- Title
- Artifactory slowness/degraded performance in AWS USE1 region on May 29 between 11:45 PM Pacific Time to 1:00 PM Pacific Time
- Vendor
- JFrog
- Date
- URL
- https://rewindex.com/company/jfrog/incidents/lmb6r6zq8r4r
JFrog profileRecent JFrog incidentsAll outages on May 30, 2018JFrog in May 2018MarkdownJSON