# JFrog: JFrog Cloud Platform outage affecting subset of customers in AWS US East region

- Impact (vendor’s label): none
- Status: resolved
- Started: 2026-10-09 22:50 UTC · Resolved: 2026-10-09 23:20 UTC · Duration: 29 min
- Updates: 3 · Affected components: Distribution, US - East1 (N. Virginia) - AWS - Distribution, US - East1 (N. Virginia) - AWS - Webhook, Webhook, Security - Curation, US - East1 (N. Virginia) - AWS - Security - Curation, Pipelines, US - East1 (N. Virginia) - AWS - Pipelines, Security - Catalog, US - East1 (N. Virginia) - AWS - Security - Catalog, Artifactory, US - East1 (N. Virginia) - AWS - Artifactory, Security - Runtime, US - East1 (N. Virginia) - AWS - Security - Runtime, Security - JAS, US - East1 (N. Virginia) - AWS - Security - JAS, Security - Xray, US - East1 (N. Virginia) - AWS - Security - Xray, US - East1 (N. Virginia) - AWS - Web UI, Web UI
- [Vendor status page: https://stspg.io/2cck3szls8lc](https://stspg.io/2cck3szls8lc)
- [Company: JFrog](https://rewindex.com/company/jfrog.md)

## Part of an outage event

- [AWS us-east-1 outage, Oct 9, 2026: 17 vendors, 18 incidents](https://rewindex.com/events/2026-10-09-aws-us-east-1)
- This incident names AWS / us-east-1 (location or integration). (hop 1, posted +18 min vs the first vendor naming AWS)
- Evidence: “…JFrog Cloud Platform outage affecting subset of customers in AWS US East region This incident has been resolved. A fix has been implemented and we are monitoring the results. This incident has been re…”

```mermaid
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Convex, Temporal Cloud, JFrog, PlanetScale +1"]:::blames
  root --> h1
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Chargebee"]:::blames
  root --> later
  me["JFrog (this incident)<br/>posted +18 min"]:::me
  h1 --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **investigating** 2026-10-09 22:50 UTC: We are currently investigating an issue impacting JFrog Platform Our team is actively working to identify the root cause and implement a resolution. We will provide an update in 30 minutes. Thank you for your patience.
- **monitoring** 2026-10-09 23:05 UTC: A fix has been implemented and we are monitoring the results.
- **resolved** 2026-10-09 23:20 UTC: This incident has been resolved.


---
Canonical: https://rewindex.com/company/jfrog/incidents/ly2v5wwdvy3z · Markdown: https://rewindex.com/company/jfrog/incidents/ly2v5wwdvy3z.md · JSON: https://rewindex.com/api/v1/companies/jfrog/incidents/ly2v5wwdvy3z · Generated 2026-10-20T01:31:05.611Z