Figma: General degraded performance
AWS outage, Nov 12, 2019 · 11 vendors, 12 incidents
Figma’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +58 min vs the first vendor naming AWS)
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["Figma (this incident)<br/>posted +58 min"]:::me
root -.->|"same window"| 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
We’ve identified the root cause of the degraded performance and Figma should now be fully operational again for all users. If you continue to have problems connecting to Figma, email support@figma.com.
From Figma’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.figma.com (opens in new tab).