Where does this status come from?

From Figma's own status page API at https://status.figma.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Figma's words.

How can my agent or app check Figma status?

Fetch https://upbutler.com/status/figma/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"figma"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Figma's?

Add "figma" to the dependencies of your UpButler workspace. When one of your monitors fails while Figma has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Figma down?

Right now

No. Figma is operational.

No incidents reported.

Read from status.figma.com 72 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/figma/status.agent.json

MCP: upstream_status {"service":"figma"}

The editor, Dev Mode and the REST API used by design-to-code agents.

What Figma reports

Operational

Taken as is from Figma's own status page API. Incident titles and component names below are theirs.

Open status.figma.com

UpButler's independent probe

There is no keyless endpoint of Figma that says anything useful, so UpButler does not probe it. To check your own Figma account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Figma components

17 operational

Admin, Billing & AI creditsOperational
Community & ForumOperational
Dev ModeOperational
Email & NotificationsOperational
File Browser & SearchOperational
Figma agentOperational
Figma DesignOperational
FigJamOperational
Figma MakeOperational
Figma MotionOperational
Figma SlidesOperational
Figma WeaveOperational
MCPOperational
Plugins & WidgetsOperational
Real-time collaboration serverOperational
REST APIOperational
Sign-in & Account AccessOperational

Figma incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Figma.

Started (UTC)	Incident	Impact	Lasted
2026-09-27 01:04	Service disruption	critical	1 h 28 min

Tell your outage from Figma's

Declare that your project depends on Figma. When one of your monitors fails while Figma has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - figma

Ask before you retry

curl -s https://upbutler.com/status/figma/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "figma",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Figma down right now?: No. As of 2026-10-10 05:11 UTC, Figma is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Figma's own status page API at https://status.figma.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Figma's words.
How can my agent or app check Figma status?: Fetch https://upbutler.com/status/figma/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"figma"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Figma's?: Add "figma" to the dependencies of your UpButler workspace. When one of your monitors fails while Figma has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in code, packages and workflows

UpButler is not affiliated with Figma. Status and incident text belong to Figma and are read from their public status source; the probe result is UpButler's own measurement.