JFrog: Degraded performance for AWS EUC1 region
AWS outage, Nov 12, 2019 · 11 vendors, 12 incidents
JFrog’s incident blames AWS as the cause. (hop 1, posted +48 min vs the first vendor naming AWS)
“…Degraded performance for AWS EUC1 region This incident caused by Amazon Web Services outage in EU-West-1 region (Frankfurt) has been resolved.…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>5 vendors, 4 blamed AWS<br/>Opsgenie, Elastic Cloud, Wise, JFrog +1"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Confluent"]:::blames
root --> h4
later["Later<br/>1 vendor<br/>JFrog"]:::names
root --> later
me["JFrog (this incident)<br/>posted +48 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.
Timeline of updates
- resolved
This incident caused by Amazon Web Services outage in EU-West-1 region (Frankfurt) has been resolved.
From JFrog’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.jfrog.io (opens in new tab).