Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Figma Outage History

Every past Figma outage tracked by IsDown, with detection times, duration, and resolution details.

There were 140 Figma outages since September 2016. The 18 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 20, 2026

April 2026: Figma Make Service Disruption

Detected Apr 20, 2026 6:42 AM UTC · Resolved Apr 20, 2026 3:50 PM UTC · Duration about 9 hours

Figma experienced a service disruption affecting the Figma Make feature, with users encountering increased error messages for approximately 9.2 hours. The engineering team implemented a fix to resolve the error rate issues. The incident was successfully resolved after monitoring confirmed the fix was effective.

Minor April 9, 2026

April 2026: Figma Make Service Disruption

Detected Apr 9, 2026 7:00 PM UTC · Resolved Apr 10, 2026 4:02 PM UTC · Duration about 21 hours

Figma experienced a service disruption affecting users' ability to load Figma Make files and published Sites, with the issue particularly impacting users on certain VPN providers. The incident lasted 21 hours before being fully resolved, with Figma monitoring the service to ensure complete recovery.

Minor March 12, 2026

March 2026: Figma Make Publishing Disruption

Detected Mar 12, 2026 2:00 PM UTC · Resolved Mar 12, 2026 10:12 PM UTC · Duration about 8 hours

Figma experienced an 8.2-hour service disruption that prevented some users from previewing and publishing Figma Make files from 12:45 to 4:50 PM UTC. The issue was identified within approximately 45 minutes of investigation beginning, and a fix was successfully implemented and monitored until full resolution.

Minor March 6, 2026

March 2026: Variant Properties Disruption

Detected Mar 6, 2026 9:40 PM UTC · Resolved Mar 7, 2026 6:10 PM UTC · Duration about 21 hours

Figma experienced a bug affecting library publishes that caused incorrect component updates, resulting in errors about conflicting properties and values in variants for users consuming those libraries. The issue impacted design workflows for approximately 7.5 hours while the publishing bug was active, though the total incident duration was 20.5 hours. The problem was resolved by fixing the underlying library publish issue, with users needing to re-publish affected components and re-update consuming files to clear remaining errors.