All services / Productivity & collaboration
Figma
Saved on this device only; Korantix does not store it and sends no notifications.
- Current assessment
- Operational (provider)
- Confidence
- Medium confidence
- Scope
- Provider-wide
- Last verified
- Oct 25, 01:36 AM UTC
- Sources
- 1 source: Official
Official incident history
- Resolved
Figma agent and Figma Make increased errors rates.
Started: · Duration: 27 minProvider updates (4)
- Investigating “We're investigating increased errors for Figma Make and Figma agent.”
- Identified “The issue has been identified and a fix is being implemented.”
- Monitoring “A fix has been implemented and we are monitoring the results.”
- Resolved “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 have fully recovered. We are continuing to work with the provider to prevent this from happening again. We apologize for th…”
- Started: · Duration: 88 minResolved
Provider updates (3)
- Investigating “We are currently investigating an issue where Figma Services are degraded or unavailable because of failures with AWS and other dependencies.”
- Monitoring “Figma should now be operational. We are continuing to monitor.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 251 minResolved
Provider updates (3)
- Investigating “We're investigating an issue that prevents Codex/ChatGPT users from seeing some MCP tools, such as use_figma.”
- Monitoring “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.”
- Resolved “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.”
- Started: · Duration: 201 minResolved
Provider updates (2)
- Monitoring “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.”
- Resolved “This incident has been resolved.”
- Resolved
Figma Make disruption - Gemini 3.1 Pro
Started: · Duration: 774 minProvider updates (3)
- Investigating “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.”
- Monitoring “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.”
- Resolved “This incident has been resolved.”
- Resolved
Figma Make and Agent Service Disruption
Started: · Duration: 103 minProvider updates (2)
- Monitoring “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.”
- Resolved “We've identified an issue leading to errors while prompting Figma Make and and Agent using Anthropic models. This has been resolved.”
- Started: · Duration: 548 minResolved
Provider updates (3)
- Investigating “We are investigating an increase in Figma Make error messages”
- Monitoring “[Mitigated] A fix has been implemented and we're monitoring the results.”
- Resolved “This incident has been resolved at 9:39 am UTC”
- Started: · Duration: 1260 minResolved
Provider updates (3)
- Investigating “We are investigating an issue some users are experiencing while loading Figma Make files or published Sites.”
- Monitoring “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.”
- Resolved “This incident has been resolved.”
- Resolved
Figma Make Publishing Disruption
Started: · Duration: 491 minProvider updates (4)
- Investigating “We are investigating an issue loading previews and publishing Figma Make files.”
- Identified “We have identified the issue that is preventing some users from previewing and publishing Figma Make files. We are now working to fix it.”
- Monitoring “A fix has been implemented and we're monitoring the results.”
- Resolved “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.”
- Started: · Duration: 1229 minResolved
Provider updates (3)
- Investigating “We are currently investigating an issue causing some users to see errors about conflicting properties and values in their variants.”
- Monitoring “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.”
- Resolved “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 see this error, please re-publish the affected components (by making a small change) and re-update the consuming files …”
- Resolved
Figma Sites Publishing Disruption
Started: · Duration: 344 minProvider updates (4)
- Investigating “We are investigating an issue some users are experiencing when publishing Figma Sites with code layers.”
- Identified “We have identified the cause of the issue with Sites publishing and are working on a fix.”
- Monitoring “A fix has been implemented and we're monitoring the results.”
- Resolved “This issue has been resolved as of February 17 at 18:59 UTC.”
- Resolved
Figma Make Publishing Disruption
Started: · Duration: 330 minProvider updates (4)
- Investigating “We are investigating an issue some users are experiencing when publishing Figma Makes or Sites with code components.”
- Identified “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.”
- Monitoring “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.”
- Resolved “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.”
- Resolved
Figma Make Publishing Disruption
Started: · Duration: 4699 minProvider updates (4)
- Investigating “We are investigating an issue some users are experiencing when publishing Figma Makes or Sites with code components.”
- Identified “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: https://github.com/esm-dev/esm.sh/issues/1294#issue-3866491297. We are actively working to mitigate the issue.”
- Monitoring “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.”
- Resolved “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.”
- Started: · Duration: 220 minResolved
Provider updates (3)
- Investigating “We are investigating an issue affecting availability of some AI features in Figma.”
- Monitoring “We’ve mitigated the issue impacting AI feature availability and are continuing to monitor.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 1003 minResolved
Provider updates (5)
- Investigating “We are investigating an issue some users are experiencing while prompting in Figma Make.”
- Monitoring “We have addressed the issue and prompting in Figma Make should now be operational. We are continuing to monitor.”
- Investigating “We are investigating an issue some users are experiencing while prompting in Figma Make.”
- Monitoring “We have addressed the issue and prompting in Figma Make should now be operational. We are continuing to monitor.”
- Resolved “From 12AM to 5PM UTC, some users experienced issues while prompting in Figma Make. This has been resolved.”
- Resolved
Figma Make publishing disruption
Started: · Duration: 126 minProvider updates (2)
- Investigating “We are investigating an issue some users are experiencing when attempting to publish Figma Make files.”
- Resolved “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.”
- Started: · Duration: 30 minResolved
Provider updates (2)
- Investigating “We are currently investigating an issue where Figma Make is experiencing intermittent service disruptions starting at 06:30 UTC.”
- Resolved “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.”
- Resolved
Service Disruption with Sites and Make
Started: · Duration: 243 minProvider updates (4)
- Investigating “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.”
- Identified “The issue has been identified and a fix is being implemented.”
- Monitoring “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 recovery.”
- Resolved “This incident has been resolved.”
- Started: · Duration: 658 minResolved
Provider updates (4)
- Investigating “We are currently investigating an issue where Figma Services are degraded or unavailable because of failures with AWS and other dependencies.”
- Identified “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.”
- Monitoring “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.”
- Resolved “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, so we are marking the incident resolved. We will continue to monitor closely through the night.”
- Started: · Duration: 370 minResolved
Provider updates (3)
- Investigating “We are investigating an issue some users are experiencing while prompting in Figma Make.”
- Monitoring “A fix has been implemented and prompting in Figma Make should now be operational. We are continuing to monitor.”
- Resolved “From 19:00 to 21:51 UTC, some users experienced issues while prompting in Figma Make. This has been resolved.”
What the provider published about this service, with the provider's own updates (wording quoted as published).
Evidence
- Official
- Figma Status ↗ ·
All Systems Operational· Oct 25, 01:36 AM UTC
Why this assessment
- Provider reports no active incident.
Rule set assess-1. The same evidence always gives the same result.
Evidence and freshness
Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.
| Source | Last observed | Age | Used in assessment |
|---|---|---|---|
| Official | 3 min ago | Yes — recent |
Technical details
Affected components (provider)
The provider lists no degraded components.