outages.live
Live

Figma

Figma is operational

Checked 59 s ago Operational

Temporary Disruption with Sites

Figma Sites do not work. Figma reports that a fix is in place and that Sites should work again. Figma continues to monitor the problem.

Noticeupdated 2 d ago

History

90 days agoToday

Incidents in 90 days

4

Days with an incident

6

Median duration

1 h 28 min

Longest incident

4 h 11 min

Components

17
Admin, Billing & AI credits Operational
90 days ago1 day with an incidentToday
Community & Forum Operational
90 days ago1 day with an incidentToday
Dev Mode Operational
90 days ago1 day with an incidentToday
Email & Notifications Operational
90 days ago1 day with an incidentToday
File Browser & Search Operational
90 days ago1 day with an incidentToday
Figma agent Operational
90 days ago2 days with an incidentToday
Figma Design Operational
90 days ago1 day with an incidentToday
FigJam Operational
90 days ago1 day with an incidentToday
Figma Make Operational
90 days ago2 days with an incidentToday
Figma Motion Operational
90 days ago1 day with an incidentToday
Figma Slides Operational
90 days ago1 day with an incidentToday
Figma Weave Operational
90 days ago1 day with an incidentToday
MCP Operational
90 days ago2 days with an incidentToday
Plugins & Widgets Operational
90 days ago1 day with an incidentToday
Real-time collaboration server Operational
90 days ago1 day with an incidentToday
REST API Operational
90 days ago1 day with an incidentToday
Sign-in & Account Access Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 13, 2026

Duration27 min10:25 to 10:52Figma agent and Figma Make increased errors rates.Degraded

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.

Sep 27, 2026

Duration1 h 28 min01:04 to 02:32Service disruptionMajor outage

This incident has been resolved.

Aug 26, 2026

Duration4 h 11 min12:08 to 16:19Figma MCP DisruptionPartial outage

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.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane