Skip to main content
Figma logo

Is Figma Down?

No — Figma is up

Reachable from all 8 checked regions

Average response time: 60ms

Last checked · checks run every 6 hours

Official status page: https://status.figma.com

Figma uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
94ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means we have no measurement for that window.

30-day history

2-day clean streak
Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: 100.00% uptime, 16 checks
Jul 28: 100.00% uptime, 43 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn
18ms
DNS 0ms TCP 0ms TLS 3ms TTFB 7ms
bom
167ms
DNS 1ms TCP 1ms TLS 5ms TTFB 27ms
cdg
38ms
DNS 0ms TCP 0ms TLS 3ms TTFB 9ms
dfw
112ms
DNS 0ms TCP 7ms TLS 9ms TTFB 34ms
ewr
33ms
DNS 0ms TCP 1ms TLS 4ms TTFB 9ms
fra
24ms
DNS 1ms TCP 1ms TLS 4ms TTFB 12ms
gru
72ms
DNS 0ms TCP 6ms TLS 9ms TTFB 30ms
iad
17ms
DNS 0ms TCP 0ms TLS 3ms TTFB 10ms

What Figma does

Figma is a browser-based design tool for interface design and prototyping, with real-time multiplayer editing. Design files live in the service rather than on a designer's machine, and engineers usually read specifications and export assets straight from the file, so an outage blocks both design work and handoff at once.

What an outage looks like

During a Figma outage files fail to open, the canvas shows a connection error, and multiplayer cursors disappear while edits stop syncing. Comments may not post and asset export can fail. The desktop app wraps the same service rather than holding a local copy, so it fails alongside the browser instead of offering a fallback.

What to do about it

Check status.figma.com for current incidents. Version history is kept server-side, so work saved before the incident is preserved and does not need recreating. If a file was open when the outage began, avoid closing the tab: unsynced changes can sometimes still be recovered once the connection returns.

Is it down for everyone, or just you?

If this page says Figma is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Notion
Notion
Webflow
Webflow
GitHub
GitHub
Slack
Slack

Figma outage FAQ

Will I lose my work if Figma goes down?
Work already synced is kept in version history on Figma's side and comes back when service returns. The risk is edits made in the minutes before the connection dropped, which may not have synced. Leaving the tab open gives those the best chance of recovering, because closing it discards whatever the client was still holding.
Does the Figma desktop app work offline?
Not meaningfully. The desktop app is a wrapper around the same service rather than a local editor, so it fails when the service does. Files you have not already opened will not load at all, and editing is unavailable regardless. There is no offline mode to fall back on during an incident.
Can I still hand off designs to engineers during an outage?
Not from Figma itself, since inspect and export both need the service. If a handoff is time-critical, screenshots already shared in chat or a ticket remain usable, and any assets exported before the incident are unaffected. Plan to re-export once service returns rather than working from stale copies.
Is FigJam affected by the same outages?
FigJam runs on the same platform and is reported on the same status page, so a platform-level incident usually affects both. Component-level incidents can hit one and not the other, which is why status.figma.com is worth reading rather than assuming: it names which parts of the service are degraded.

How we measure this

  • We request Figma's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Figma publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Figma goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required