Skip to main content
Chrome icon

New! Check service status instantly with our Chrome extension

Add to Chrome External link icon
Firefox icon

New! Check service status instantly with our Firefox extension

Add to Firefox External link icon
magnifying glass icon
magnifying glass icon
  • Can't find service? Request service
    Sign up
    Figma icon
    Figma icon

    Figma outage history

    Collaborative interface design tool for building meaningful products.

    There were 15 Figma outages since January 2025 which are summarized below, including incident details, duration, and resolution information.

    Not working for you?

    minor icon Minor

    : Figma Site publishing degraded due to third-party dependency

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (12 hours and 40 minutes)

    The Figma Site publishing feature experienced a temporary disruption caused by an issue with a third-party dependency. Impact began at and persisted until , with site publishing likely failing or performing slowly for affected users during that window.

    Figma communicated the incident on the status page with a 'Temporary Disruption with Sites' message, noting the degradation was related to the external dependency. The issue was resolved by and site publishing returned to normal.

    minor icon Minor

    : Figma agent and Figma Make experience increased error rates

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (10 minutes)

    Users attempting to run automation with Figma Make and operate the Figma agent encountered elevated error rates starting at . The incident affected the Figma agent and Figma Make components, leading to degraded automation workflows for a period of time. The issue was identified and a fix was being implemented by as engineers worked to stabilize operations.

    The services returned to normal by as the fix took effect.

    major icon Major

    : Figma disruption hits sign-in and collaboration

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (15 minutes)

    A service disruption began at with degraded or unavailable Figma services tied to failures with AWS and other dependencies. Users faced sign-in issues, limited file access, and degraded collaboration across core apps, including Sign-in & Account Access, REST API, Real-time collaboration server, File Browser & Search, Email & Notifications, and design suites like Figma Design and FigJam, with plugins and widgets also affected. By , the affected components came back online and service was returning to normal as the root issues were resolved.

    minor icon Minor

    : Figma outage disrupts MCP tools for Codex/ChatGPT users

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (4 hours and 10 minutes)

    An outage began at affecting Figma's MCP subsystem, which prevented Codex and ChatGPT users from seeing MCP tools such as use_figma. The issue represented a partial outage for access to these features, with the MCP component flagged as degraded. Over the next few hours, Figma provided updates about recovery efforts; by recovery was starting and monitoring continued, and by progress remained in progress. The MCP tool visibility was restored later, and the MCP component returned to up status by . The disruption lasted a little over four hours.

    major icon Major

    : Figma editing and export features down worldwide

    Detected by StatusGator:
    Officially acknowledged: No
    Outage ended: (24 minutes)

    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 and persisted at least through according to StatusGator data.

    minor icon Minor

    : Figma AWS infrastructure briefly degraded, then restored

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 hour and 20 minutes)

    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 and was resolved by , 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.

    major icon Major

    : Figma outage disrupts editor access and designs

    Detected by StatusGator:
    Officially acknowledged: No
    Outage ended: (1 hour and 1 minute)

    From to , 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 , 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.

    minor icon Minor

    : Figma Sites publishing disruption lasting about 25 hours

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (1 day and 1 hour)

    A publishing disruption affected Figma Sites that use code layers, causing some users to be unable to publish. The incident began on and was resolved by . 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.

    minor icon Minor

    : Figma publishing disruption affects Makes and code-enabled sites

    Detected by StatusGator:
    Officially acknowledged:
    Outage ended: (5 hours and 30 minutes)

    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 and was resolved by , 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.

    minor icon Minor

    : Figma outage disrupts file access for users worldwide

    Detected by StatusGator:
    Officially acknowledged: No
    Outage ended: (36 minutes)

    An outage affected Figma, with users unable to access the editor or open files. The incident began at and was resolved by , 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 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 icon

    Looking for more Figma outage stats?

    Get real-time insights and historical data on Figma outages.

    Figma outage stats