outages.live
Live
FigmaIncident · 2026-08-26 12:08 UTC

Figma MCP Disruption

ResolvedOfficial update

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.

The latest update from Figma.

State

Resolved

Started

68 d ago

2026-08-26 12:08 UTC

Lasted

4 h 11 min

until 2026-08-26 16:19 UTC

Worst impact

Partial outage

Timeline

4 updates
12:0813:1114:1415:1616:19
Partial outageUpdate postedTimes in UTC

Investigating

2 h 5 min 50%

Monitoring

2 h 6 min 50%

Updates

Times in UTC

As posted by Figma

Resolved2026-08-26 16:19 UTC

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.

Monitoring2026-08-26 15:14 UTC

Recovery is still progressing 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.

Monitoring2026-08-26 14:13 UTC

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.

Investigating2026-08-26 12:08 UTC

We're investigating an issue that prevents Codex/ChatGPT users from seeing some MCP tools, such as use_figma.

Affected components

1
MCP

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