outages.live
Live
FigmaIncident · 2026-09-27 01:04 UTC

Service disruption

ResolvedOfficial update

This incident has been resolved.

The latest update from Figma.

State

Resolved

Started

36 d ago

2026-09-27 01:04 UTC

Lasted

1 h 28 min

until 2026-09-27 02:32 UTC

Worst impact

Major outage

Timeline

3 updates
01:0401:2601:4802:1002:32
Major outageUpdate postedTimes in UTC

Investigating

15 min 17%

Monitoring

1 h 14 min 83%

Updates

Times in UTC

As posted by Figma

Resolved2026-09-27 02:32 UTC

This incident has been resolved.

Monitoring2026-09-27 01:18 UTC

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

Investigating2026-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.

Affected components

17
Admin, Billing & AI creditsCommunity & ForumDev ModeEmail & NotificationsFile Browser & SearchFigma agentFigma DesignFigJam

Figma in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

6

Median duration

1 h 28 min

This incident

About 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·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

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·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