Figma reported "Temporary Disruption with Sites" on its status page at 2026-10-30 10:38 UTC. 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.

Figma did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-30 10:38 UTC. This page shows the end time when Figma marks it resolved.

How do I get alerts for Figma?

Subscribe to the Figma live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Figma. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

FigmaIncident · 2026-10-30 10:38 UTC

Temporary Disruption with Sites

NoticeOfficial update

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.

State

Monitoring

Started

2 d ago

2026-10-30 10:38 UTC

Ongoing for

2 days

Worst impact

Notice

Timeline

1 update

Oct 30Oct 31Oct 31Nov 1Nov 1

NoticeUpdate postedDates in UTC

Monitoring

2 days 100%

Updates

Times in UTC

As posted by Figma

Monitoring2026-11-01 17:18 UTC

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

Figma in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 28 min

This incident

38× the median

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

2 days

median 1 h 28 min

90 days agoToday

Other Figma incidents

All incidents

Figma·Figma agent and Figma Make increased errors rates.

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.

Resolvedresolved 19 d 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