Figma outage history

Figma users across regions reported outages in core editing and exporting workflows. The disruption included missing export buttons, failure to copy or export assets, and permission or sharing problems that blocked collaboration for many files. The impact appeared global, with users in North America, Europe, and other regions experiencing degraded editing, copying, or exporting for extended periods. Impact began around 7:05 PM UTC and persisted at least through 7:29 PM UTC according to StatusGator data.

A brief degradation affected Figma due to issues in the AWS Infrastructure component. Users may have experienced slower performance or intermittent access while the problem was active. The incident began at 11:47 AM UTC and was resolved by 1:07 PM UTC, lasting roughly an hour. On the status page, AWS Infrastructure was shown as degraded before returning to normal, with services back to their usual state by the final update.

From 6:14 PM UTC to 7:14 PM UTC, Figma users experienced an outage that prevented access to the editor and designs due to connection errors. Users reported not being able to open files or use the editor, with messages like 'An error occurred while opening the editor.' The outage disrupted design work for many users during this period.

StatusGator detected the issue at Feb 18, 2026 6:14 PM UTC, ahead of any official acknowledgment. There were no official updates published on Figma's status page during the incident. A large volume of user reports arrived in the early minutes of the incident, underscoring the breadth of impact before the incident was resolved.

A publishing disruption affected Figma Sites that use code layers, causing some users to be unable to publish. The incident began on Feb 17, 2026 2:17 PM UTC and was resolved by Feb 18, 2026 3:17 PM UTC. The issue led to a period of degraded publishing workflows before normal functionality returned.

The provider issued two status updates during the incident, outlining the investigation and the subsequent recovery.

Figma reported a publishing disruption affecting the Makes publishing workflow and Sites that use code components. Users attempting to publish new Makes or update code-based Sites may have experienced errors or delays, disrupting publish-to-live workflows.

The incident began at 7:07 PM UTC and was resolved by 12:37 AM UTC, lasting roughly 6 hours and 30 minutes. The service was marked with a warning during the event. The status page recorded 2 updates describing the investigation and the resolution. The disruption appeared limited to publishing functionality for Makes and code-enabled Sites rather than a full platform outage.

An outage affected Figma, with users unable to access the editor or open files. The incident began at 10:25 AM UTC and was resolved by 11:01 AM UTC, lasting about 36 minutes. Reports covered multiple regions, including India and Malta, impacting design collaboration and work on active projects.

StatusGator detected the issue at Jan 9, 2026 10:25 AM UTC from user reports ahead of any official acknowledgment. Figma did not publish status updates during the incident on their status page, and service recovery followed the 11:01 UTC resolution. A wave of user reports mid-incident suggested broad, though not universal, impact across users.

Figma experienced a multi-hour outage impacting access to its web and mobile apps. Users reported being unable to load the app, sign in, or access files, with errors ranging from loading failures to timeouts. The incident began at 7:09 AM UTC and lasted until 11:41 AM UTC, a duration of about 4 hours and 32 minutes. StatusGator detected the issue prior to any official acknowledgement, with an Early Warning Signal starting at Dec 12, 2025 7:09 AM UTC. Figma did not publish official updates on their status page during the incident, leaving users without formal communication until resolution.

Figma Make previews stopped rendering for a subset of users, hindering the ability to preview or attach Make project designs. Reports came from users across multiple regions including Vietnam, Türkiye, the United Kingdom, and Japan. The outage began at Nov 18, 2025 2:03 PM UTC and was resolved by Nov 18, 2025 2:20 PM UTC, lasting about 17 minutes. StatusGator detected the issue at Nov 18, 2025 2:03 PM UTC as an Early Warning Signal ahead of any official acknowledgment. There were no official status updates posted by Figma during the incident.

Figma experienced a service disruption that degraded or prevented use of its real-time collaboration server and API/web app for many users. The outage began around Oct 20, 2025 7:47 PM UTC and was linked to dependencies on AWS and related infrastructure. StatusGator detected the issue at Oct 20, 2025 7:47 PM UTC, about 5 hours 50 minutes before the first official acknowledgment at Oct 21, 2025 12:37 AM UTC. The provider issued initial updates noting degraded services, with a follow-up at Oct 21, 2025 12:42 AM UTC as mitigation progressed.

An outage briefly affected Figma users, with issues loading reported in India (including Noida and Jalandhar). The incident began at 12:20 PM UTC and was resolved by 12:25 PM UTC, lasting about 5 minutes. User reports started around 12:15 PM UTC, and StatusGator recorded an Early Warning Signal at Aug 21, 2025 12:20 PM UTC based on those observations, while Figma did not post any status updates during the event. The disruption appears localized to India and did not result in a prolonged impact.