outages.live
Live
FigmaIncident · 2026-10-13 10:25 UTC

Figma agent and Figma Make increased errors rates.

ResolvedOfficial update

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 the disruption.

The latest update from Figma.

State

Resolved

Started

19 d ago

2026-10-13 10:25 UTC

Lasted

27 min

until 2026-10-13 10:52 UTC

Worst impact

Degraded

Timeline

5 updates
10:2510:3210:3910:4510:52
DegradedUpdate postedTimes in UTC

Investigating

4 min 17%

Identified

3 min 10%

Monitoring

20 min 73%

Updates

Times in UTC

As posted by Figma

Resolved2026-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 have fully recovered. We are continuing to work with the provider to prevent this from happening again. We apologize for the disruption.

Monitoring2026-10-13 10:32 UTC

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

Identified2026-10-13 10:30 UTC

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

Investigating2026-10-13 10:26 UTC

We are continuing to investigate this issue.

Investigating2026-10-13 10:25 UTC

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

Affected components

2
Figma agentFigma Make

Figma in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

6

Median duration

2 h 49 min

This incident

84% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 days
median 2 h 49 min
90 days agoToday

Other Figma incidents

All incidents

Figma·Temporary Disruption with Sites

Figma Sites did not work. The incident is resolved. Figma reports that the fix was implemented and the incident was resolved as of October 31 at 2:00 AM UTC.

Resolvedresolved 1 h ago

Figma·Service disruption

This incident has been resolved.

Resolvedresolved 36 d ago

Figma·Figma MCP Disruption

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.

Resolvedresolved 67 d ago

Follow Figma

Your coding agent knows when Figma is down, and tells you when a failure is theirs, not yours. You can also get Figma incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "figma" and tell me if Figma has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=figma
Slack
/feed subscribe https://outages.cc/feed.xml?providers=figma

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane