# JFrog: JFrog service limitation in AWS USE1 Virginia region

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2020-09-29 16:15 UTC · Resolved: 2020-10-11 07:37 UTC · Duration: 12 d
- Updates: 1
- [Vendor status page: https://status.jfrog.io/incidents/c076q4jskstw](https://status.jfrog.io/incidents/c076q4jskstw)
- [Company: JFrog](https://rewindex.com/company/jfrog.md)

## Timeline of updates

- **resolved** 2020-10-11 07:37 UTC: The incident has been resolved. Root Cause: AWS Master Kubernetes node, where customers' applications run on, crashed for approximately 45 minutes. Afterward, all the applications tried to recover at the same time, which overloaded Ingress services in front of the applications. Pipelines exhibited higher sensitivity than the other applications from the slow recovery of the Ingress services. Mitigation: In order to reduce the region-wide impact, we isolated the impacted Pipelines services to dedicated ingress services, which immediately stabilized applications other than a subset of Pipelines. Furthermore, changes were applied to Pipelines and Ingress configurations to tune sensitive timeouts which regained stability to the rest of the Pipelines.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/jfrog/incidents/c076q4jskstw · Markdown: https://rewindex.com/company/jfrog/incidents/c076q4jskstw.md · JSON: https://rewindex.com/api/v1/companies/jfrog/incidents/c076q4jskstw · Generated 2026-10-18T13:31:22.876Z