Figma

Affected: Figma agent, Figma Make

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-13 10:25 UTC

   We're investigating increased errors for Figma Make and Figma agent.

2. investigating 2026-10-13 10:26 UTC

   We are continuing to investigate this issue.

3. identified 2026-10-13 10:30 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-10-13 10:32 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-10-13 10:52 UTC

   The issue is now resolved fully. Some users saw elevated error rates in Figma's AI features, including AI chat and Figma Make. Affected requests may have failed or needed a retry. We identified an issue with one of our providers and moved traffic to an alternate. Error rates...

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: Admin, Billing & AI credits, Community & Forum, Dev Mode, Email & Notifications, File Browser & Search, Figma agent, Figma Design, FigJam, Figma Make, Figma Motion, Figma Slides, Figma Weave, MCP, Plugins & Widgets, Real-time collaboration server, REST API, Sign-in & Account Access

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-09-27 01:04 UTC

   We are currently investigating an issue where Figma Services are degraded or unavailable because of failures with AWS and other dependencies.

2. monitoring 2026-09-27 01:18 UTC

   Figma should now be operational. We are continuing to monitor.

3. resolved 2026-09-27 02:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: MCP

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 12:08 UTC

   We're investigating an issue that prevents Codex/ChatGPT users from seeing some MCP tools, such as use_figma.

2. monitoring 2026-08-26 14:13 UTC

   We’re beginning to see recovery for the issue preventing some Codex and ChatGPT users from seeing MCP tools, such as use_figma. We’ll continue monitoring the recovery and provide another update within the next hour, or sooner if we have additional information.

3. monitoring 2026-08-26 15:14 UTC

   Recovery is still progressing for the issue preventing some Codex and ChatGPT users from seeing MCP tools, such as use_figma. We’ll continue monitoring the recovery and provide another update within the next hour, or sooner if we have additional information.

4. resolved 2026-08-26 16:19 UTC

   The issue preventing some Codex and ChatGPT users from seeing MCP tools, such as use_figma, has been resolved. The impact began at 10:14 UTC, with recovery beginning at 14:03 UTC.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-27 19:29 UTC

   Some users were unable take expected actions within files, including editing the file, between 18:42 UTC and 19:25 UTC. No file permissions were modified or incorrectly assigned. We have now addressed the root cause and are monitoring for any additional issues.

2. resolved 2026-07-27 22:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-18 23:46 UTC

   We are investigating an issue some users are experiencing when using Gemini 3.1 Pro in the Figma Make model picker. As a workaround, users can switch to the default model.

2. monitoring 2026-06-19 01:03 UTC

   The issue affecting some users when using Gemini 3.1 Pro in the Figma Make model picker has been resolved. We are continuing to monitor.

3. resolved 2026-06-19 12:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. monitoring 2026-06-16 17:58 UTC

   We've identified an issue leading to errors while prompting Figma Make and and Agent using Anthropic models. A fix has been implemented and this should now be operational. We are continuing to monitor.

2. resolved 2026-06-16 19:41 UTC

   We've identified an issue leading to errors while prompting Figma Make and and Agent using Anthropic models. This has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-20 06:42 UTC

   We are investigating an increase in Figma Make error messages

2. monitoring 2026-04-20 07:08 UTC

   [Mitigated] A fix has been implemented and we're monitoring the results.

3. resolved 2026-04-20 15:50 UTC

   This incident has been resolved at 9:39 am UTC

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-09 19:00 UTC

   We are investigating an issue some users are experiencing while loading Figma Make files or published Sites.

2. monitoring 2026-04-09 22:33 UTC

   Some users on certain VPN providers may have experienced difficulty loading Figma Make files and published Sites. The issue has been resolved. We are monitoring to confirm full recovery.

3. resolved 2026-04-10 16:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 14:00 UTC

   We are investigating an issue loading previews and publishing Figma Make files.

2. identified 2026-03-12 14:43 UTC

   We have identified the issue that is preventing some users from previewing and publishing Figma Make files. We are now working to fix it.

3. monitoring 2026-03-12 15:19 UTC

   A fix has been implemented and we're monitoring the results.

4. resolved 2026-03-12 22:11 UTC

   From 12:45 to 4:50 PM UTC today, we experienced an issue that prevented some users from previewing and publishing Figma Make files. We have updated this from Monitoring to Resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-06 21:40 UTC

   We are currently investigating an issue causing some users to see errors about conflicting properties and values in their variants.

2. monitoring 2026-03-07 02:32 UTC

   We have identified an issue causing errors about conflicting properties in variants. A fix has been implemented and remaining errors can be cleared by republishing the affected components and accepting updates. We are continuing to monitor.

3. resolved 2026-03-07 18:08 UTC

   From 5:50PM 3/6 UTC to 1:15AM 3/7 UTC, there was a bug that would cause library publishes to be incorrect. Files pulling in those updates would experience errors related to conflicting properties in variants. The issue with library publishes has been resolved. If you continue to...

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-17 14:16 UTC

   We are investigating an issue some users are experiencing when publishing Figma Sites with code layers.

2. identified 2026-02-17 15:03 UTC

   We have identified the cause of the issue with Sites publishing and are working on a fix.

3. monitoring 2026-02-17 18:59 UTC

   A fix has been implemented and we're monitoring the results.

4. resolved 2026-02-17 20:00 UTC

   This issue has been resolved as of February 17 at 18:59 UTC.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-05 19:05 UTC

   We are investigating an issue some users are experiencing when publishing Figma Makes or Sites with code components.

2. identified 2026-02-05 21:12 UTC

   We’ve identified the issue affecting some users when publishing Figma Makes or Sites that include code components. We’re actively tracking the issue with our upstream provider, esm.sh.

3. monitoring 2026-02-06 00:02 UTC

   A fix has been implemented for publishing Figma Makes or Sites with code components. This should now be operational. We are continuing to monitor to ensure full recovery.

4. resolved 2026-02-06 00:34 UTC

   From 7:05 PM UTC on Feb 5 to 12:00 AM UTC on Feb 6, some users experienced issues when prompting in Figma Make or Sites with code components. This issue has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-29 19:39 UTC

   We are investigating an issue some users are experiencing when publishing Figma Makes or Sites with code components.

2. identified 2026-01-29 20:16 UTC

   We have identified the issue impacting some users when publishing Figma Makes created before December 16, 2025 or Sites with code components. This is due to an intermittent issue with the service used for accessing code package dependencies used in Figma Make and Figma Sites:...

3. monitoring 2026-01-31 20:37 UTC

   A fix has been implemented for publishing Figma Makes or Sites with code components. This should now be operational. We are continuing to monitor to ensure full recovery.

4. resolved 2026-02-02 01:57 UTC

   From 9:58 PM UTC on Jan 27 to 2:00 AM UTC on Feb 1, some users experienced issues when prompting in Figma Make or Sites with code components. This issue has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-27 20:01 UTC

   We are investigating an issue affecting availability of some AI features in Figma.

2. monitoring 2026-01-27 20:26 UTC

   We’ve mitigated the issue impacting AI feature availability and are continuing to monitor.

3. resolved 2026-01-27 23:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-23 01:05 UTC

   We are investigating an issue some users are experiencing while prompting in Figma Make.

2. monitoring 2026-01-23 02:17 UTC

   We have addressed the issue and prompting in Figma Make should now be operational. We are continuing to monitor.

3. investigating 2026-01-23 10:02 UTC

   We are investigating an issue some users are experiencing while prompting in Figma Make.

4. monitoring 2026-01-23 10:29 UTC

   We have addressed the issue and prompting in Figma Make should now be operational. We are continuing to monitor.

5. resolved 2026-01-23 17:48 UTC

   From 12AM to 5PM UTC, some users experienced issues while prompting in Figma Make. This has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-07 18:19 UTC

   We are investigating an issue some users are experiencing when attempting to publish Figma Make files.

2. resolved 2026-01-07 20:24 UTC

   From 5:30 PM to 6:30 PM UTC, some users were experiencing issues when publishing Figma Make files or publishing Sites. This has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-15 17:00 UTC

   We are currently investigating an issue where Figma Make is experiencing intermittent service disruptions starting at 06:30 UTC.

2. investigating 2025-12-15 17:20 UTC

   A fix has been implemented in Figma Make and should now be operational. We are continuing to monitor to ensure full recovery.

3. resolved 2025-12-15 17:30 UTC

   From 06:30 UTC to 17:20 UTC, Figma Make was experiencing intermittent errors building Make files. A fix has been implemented in Figma Make and this incident is now resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 14:01 UTC

   We are investigating a service disruption when publishing and previewing Figma Sites and Make files, and accessing published Sites and Makes due to a Cloudflare outage.

2. investigating 2025-11-18 14:38 UTC

   We are continuing to investigate this issue.

3. investigating 2025-11-18 14:56 UTC

   We are continuing to investigate this issue.

4. identified 2025-11-18 16:09 UTC

   The issue has been identified and a fix is being implemented.

5. monitoring 2025-11-18 16:40 UTC

   We have implemented mitigations for the earlier disruption caused by the Cloudflare outage. Publishing and previewing Figma Sites and Make files, as well as accessing published Sites and Makes, should now be working as expected. We are continuing to monitor to ensure full...

6. resolved 2025-11-18 18:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: Real-time collaboration server, REST API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 19:55 UTC

   We are currently investigating an issue where Figma Services are degraded or unavailable because of failures with AWS and other dependencies.

2. identified 2025-10-20 21:24 UTC

   We are currently working to mitigate issues where Figma Services are degraded or unavailable because of failures with AWS and other dependencies. We will update in the next hour.

3. identified 2025-10-20 22:53 UTC

   We are currently working to mitigate issues where Figma Services are degraded or unavailable because of failures with AWS and other dependencies. We have recovered some Figma systems and are working to recover the rest. We will update when we see significant recovery or in...

4. identified 2025-10-21 00:35 UTC

   We are currently working to mitigate issues where Figma Services are degraded or unavailable because of previous impact from AWS and other dependencies. Although we have restored some systems we have not fully recovered. We will update when we see further significant recovery or...

5. identified 2025-10-21 00:41 UTC

   We are currently working to mitigate issues where Figma Services are degraded or unavailable because of previous impact from AWS and other dependencies. Although we have restored some systems we have not fully recovered. We will update when we see further significant recovery or...

6. monitoring 2025-10-21 02:30 UTC

   We have made significant progress, but error rates are still elevated for some users as we work to apply our mitigations to all impacted servers. We will post another update in an hour or sooner if we recover fully before then.

7. monitoring 2025-10-21 04:10 UTC

   We continue to make significant progress recovering our systems. Error rates are still elevated for some users as we continue to apply our mitigations to all impacted servers. We will post another update in an hour or sooner if we recover fully before then.

8. resolved 2025-10-21 06:53 UTC

   From 19:38 UTC to 4:10 UTC, Figma was degraded or unavailable due to failures in AWS and other dependencies. We've completed all mitigations and have been monitoring the situation for a few hours now without issues. We haven't seen any abnormal issues since our 4:10 UTC update,...

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-01 21:43 UTC

   We are investigating an issue some users are experiencing while prompting in Figma Make.

2. monitoring 2025-10-01 22:05 UTC

   A fix has been implemented and prompting in Figma Make should now be operational. We are continuing to monitor.

3. resolved 2025-10-02 03:53 UTC

   From 19:00 to 21:51 UTC, some users experienced issues while prompting in Figma Make. This has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-06 03:16 UTC

   We've identified an issue impacting interacting with prototypes and Mirror on iOS. A solution is being deployed.

2. resolved 2025-09-06 04:40 UTC

   A fix has been implemented and prototypes and Mirror on iOS should now be operational. We are continuing to monitor.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-13 16:52 UTC

   We are investigating an issue some users are experiencing when attempting to access the Figma Community Forum.

2. resolved 2025-06-13 22:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-12 18:57 UTC

   We’re investigating reports that previously published Sites and Makes are inaccessible and new publish attempts are failing.

2. monitoring 2025-06-12 19:44 UTC

   We are monitoring recovery as access to previously published Makes and Sites become available.

3. resolved 2025-06-12 23:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-05 20:56 UTC

   We are investigating an issue some users are experiencing when attempting to publish Figma Make files.

2. resolved 2025-06-05 23:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-16 12:46 UTC

   We are investigating an issue where some users are unable to load the file browser or comments.

2. monitoring 2025-04-16 13:00 UTC

   A fix has been implemented and we are monitoring results. Please refresh your tabs.

3. resolved 2025-04-16 13:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-11 17:53 UTC

   We are investigating an issue where some users may observe errors upon attempting to access Figma.

2. monitoring 2025-04-11 19:11 UTC

   A fix has been implemented and Figma should now be operational. We are continuing to monitor.

3. resolved 2025-04-12 00:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: Real-time collaboration server

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-07 16:47 UTC

   We are investigating an issue users are experiencing when loading comments in some files.

2. monitoring 2025-04-07 17:25 UTC

   We have resolved the issue causing some users to be unable to load their comments, and are monitoring.

3. monitoring 2025-04-08 05:50 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-04-08 05:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-14 01:30 UTC

   We are investigating an issue where some Figma users on Chromebooks are unable to open files.

2. monitoring 2025-02-15 00:59 UTC

   A fix has been implemented and shipped to all users. We are continuing to monitor.

3. resolved 2025-02-25 16:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-22 17:59 UTC

   We are currently experiencing issues affecting email delivery. We are actively investigating and working to resolve the issue as quickly as possible

2. identified 2025-01-22 19:12 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-01-22 20:47 UTC

   The issue has been resolved and we are monitoring the results.

4. resolved 2025-01-22 21:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-01-22 06:30 UTC

   From 2:30 AM - 6:30 AM UTC some users experienced slow performance loading the Figma file browser view as well as features like comments. We have since resolved the underlying issue and are monitoring closely.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-08 21:38 UTC

   We are seeing some intermittent error rates that could cause file access errors and errors loading the recent files page. We are actively investigating.

2. monitoring 2025-01-08 22:56 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-01-08 23:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-12-03 17:49 UTC

   We are currently investigating an issue with loading Figma

2. monitoring 2024-12-03 18:19 UTC

   A fix has been implemented and Figma should now be operational. We are continuing to monitor.

3. resolved 2024-12-03 19:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-28 00:34 UTC

   We are investigating an issue where some customers are unable to load files through the file browser.

2. monitoring 2024-11-28 01:43 UTC

   The issue has been identified and fixed.

3. resolved 2024-11-28 03:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-08 17:17 UTC

   We're investigating an availability issue navigating and viewing files

2. monitoring 2024-10-08 17:20 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-10-08 17:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-30 16:37 UTC

   We are seeing some intermittent error rates that could cause file access errors and errors loading the recent files page. We are continuing to investigate.

2. monitoring 2024-09-30 16:49 UTC

   We have resolved the issue and are monitoring for further issues

3. resolved 2024-09-30 19:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-09-26 17:42 UTC

   There was degradation in search results ranking, but we’ve identified the problem and are in the process of getting the fix out

2. monitoring 2024-09-26 18:23 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-09-26 18:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: Real-time collaboration server

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2024-09-10 07:57 UTC

   We've received reports of issues related to file access permissions. We believe the issue should be fixed and are monitoring the make sure the issue is resolved.

2. investigating 2024-09-10 08:12 UTC

   We are still seeing some intermittent error rates that could cause file access permission errors and are continuing to investigate.

3. monitoring 2024-09-10 10:17 UTC

   We've implemented a fix and are monitoring results.

4. resolved 2024-09-10 11:24 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: Real-time collaboration server

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-09 22:06 UTC

   We’re investigating an issue with images not loading in files.

2. monitoring 2024-09-09 22:48 UTC

   Our engineering teams deployed a fix and we are monitoring results.

3. resolved 2024-09-09 23:25 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: Real-time collaboration server

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-09 12:02 UTC

   We are currently investigating an issue related to the opening of a small set of files. We expect it to be resolved shortly.

2. monitoring 2024-09-09 12:28 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-09-09 13:30 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: Real-time collaboration server, REST API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2024-07-22 13:58 UTC

   Figma had a 10 minute partial availability issue on Monday July 22nd between 13:38 and 13:48 UTC. We have identified and addressed the root cause and we are actively monitoring.

2. monitoring 2024-07-22 14:02 UTC

   We are continuing to monitor for any further issues.

3. resolved 2024-07-22 14:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2024-06-10 23:17 UTC

   We experienced a brief disruption that affected opening of files and home page loading due to a configuration change. The issue has been resolved and we're monitoring the results.

2. resolved 2024-06-11 00:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-05-10 19:27 UTC

   Figma observed delays with notifications from 11:00am PT to 11:45am PT. This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-04-15 23:31 UTC

   Figma experienced some delays in emails sending from Apr 9th to April 15th. The issue was mitigated on Apr 15th.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-02-28 01:33 UTC

   Figma users experienced intermittent connectivity issues for 12 minutes. We have since resolved the underlying issue and are monitoring closely.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: REST API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. monitoring 2024-02-14 15:59 UTC

   OpenAI is experiencing an issue that is preventing some users from utilizing FigJam’s AI features. We are monitoring their service’s status and will update here when the disruption is cleared.

2. resolved 2024-02-14 21:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2023-12-10 04:18 UTC

   We experienced a brief disruption due to an underlying AWS issue. The issue has been resolved and we're monitoring the results.

2. resolved 2023-12-10 04:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2023-11-21 00:11 UTC

   Figma observed increased errors between 3:36pm PT and 3:39pm PT. The incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: REST API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-11-15 20:55 UTC

   We are currently investigating an issue where some users are unable to load Figma

2. monitoring 2023-11-15 21:02 UTC

   A fix has been implemented and we're monitoring the results

3. resolved 2023-11-15 22:33 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Figma's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2023-11-15 01:30 UTC

   Figma experienced an issue between 1:32am - 1:49am GMT that caused certain key operations to fail. The issue has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.

Affected: REST API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. monitoring 2023-11-08 22:43 UTC

   OpenAI is experiencing an issue that is preventing some users from utilizing FigJam’s AI features. We are monitoring their service’s status and will update here when the disruption is cleared.

2. resolved 2023-11-10 06:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Figma's status page.