← Back to the carnage
FIGMA
🟡 Figma locked users out of their own files for a bit—turns out the read-only fate was unintentional. They found the problem and users can now resume their design arguments. No permissions were actually nuked, just temporarily forgotten. (Auto-resolved: no updates in 24h)
// The official story
Service Disruption
// Status page says
Jul 27 , 19:29 UTC Monitoring - Some users were unable take expected actions within files, including editing the file. No file permissions were modified or incorrectly assigned. We have now addressed the root cause and are monitoring for any additional issues.
🔗 Official status page (for the PR-approved version)
https://status.figma.com/incidents/8cwfrc0gv32wFigma's Greatest Hits
🟢 FIGMA
Jun 16, 2026
🟡 Figma's Make and Agent features had an existential crisis when talking to Claude—turns out the AI forgot its training. Engineers deployed the digital equivalent of smelling salts and declared victory. They're watching for relapse. (Auto-resolved: no updates in 24h)
🟢 FIGMA
Jan 27, 2026
🟡 Figma's AI tools went dark, leaving designers to do the unthinkable: design without robot assistance. The company is 'investigating,' which is corporate for 'our AI is having an existential crisis.'. (Auto-resolved: no updates in 24h)
🟢 FIGMA
Jan 19, 2026
⚪ Figma's Sites and Make feature went dark when Cloudflare decided to take an unscheduled nap—turns out your design tool's reliability depends on someone else's infrastructure. They've now applied the digital equivalent of duct tape and claim everything's breathing normally again, though we're all holding our breath waiting for round two. (Auto-resolved: no updates in 24h)
🟢 FIGMA
Jan 19, 2026
⚪ Figma Make spent 11 hours building files that refused to exist. Turns out the 'Make' was taking its name too literally—it was making nothing but errors. Crisis averted, but your patience was the real casualty here. (Auto-resolved: no updates in 24h)