JFrog: JFrog Cloud Platform outage affecting subset of customers in AWS US East region
AWS us-east-1 outage, Oct 9, 2026 · 17 vendors, 18 incidents
JFrog’s incident names AWS / us-east-1 (location or integration). (hop 1, posted +18 min vs the first vendor naming AWS)
“…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…”
Swipe sideways to see the whole diagram.
Mermaid source
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 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: DistributionUS - East1 (N. Virginia) - AWS - DistributionUS - East1 (N. Virginia) - AWS - WebhookWebhookSecurity - CurationUS - East1 (N. Virginia) - AWS - Security - CurationPipelinesUS - East1 (N. Virginia) - AWS - PipelinesSecurity - CatalogUS - East1 (N. Virginia) - AWS - Security - CatalogArtifactoryUS - East1 (N. Virginia) - AWS - ArtifactorySecurity - RuntimeUS - East1 (N. Virginia) - AWS - Security - RuntimeSecurity - JASUS - East1 (N. Virginia) - AWS - Security - JASSecurity - XrayUS - East1 (N. Virginia) - AWS - Security - XrayUS - East1 (N. Virginia) - AWS - Web UIWeb UI
Timeline of updates
- investigating
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
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:22 UTC
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
62b21b9e838df7f1…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).