Is Figma Down?
- Figma's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 236 ms
Right now
The verdict is the worse of these two. How we decide
Figma's status page
status.figma.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Admin, Billing & AI credits | Operational |
| Community & Forum | Operational |
| Dev Mode | Operational |
| Email & Notifications | Operational |
| File Browser & Search | Operational |
| Figma agent | Operational |
| Figma Design | Operational |
| FigJam | Operational |
| Figma Make | Operational |
| Figma Motion | Operational |
| Figma Slides | Operational |
| Figma Weave | Operational |
5 more, all operational · show all 17
| Component | Status |
|---|---|
| Admin, Billing & AI credits | Operational |
| Community & Forum | Operational |
| Dev Mode | Operational |
| Email & Notifications | Operational |
| File Browser & Search | Operational |
| Figma agent | Operational |
| Figma Design | Operational |
| FigJam | Operational |
| Figma Make | Operational |
| Figma Motion | Operational |
| Figma Slides | Operational |
| Figma Weave | Operational |
| MCP | Operational |
| Plugins & Widgets | Operational |
| Real-time collaboration server | Operational |
| REST API | Operational |
| Sign-in & Account Access | Operational |
FlareWarden checks
figma.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 236 ms
- Checked
By region
- Amsterdam reachable, 91 ms
- Chicago reachable, 627 ms
- San Jose reachable, 64 ms
- Singapore reachable, 284 ms
- Stockholm reachable, 106 ms
- Sydney reachable, 235 ms
- Tokyo reachable, 345 ms
- Toronto reachable, 142 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 49 ms | 3 ms | 5 ms | 66 ms |
| Chicago | 33 ms | 1 ms | 30 ms | 304 ms |
| San Jose | 15 ms | 2 ms | 4 ms | 30 ms |
| Singapore | 247 ms | 1 ms | 3 ms | 262 ms |
| Stockholm | 64 ms | 1 ms | 3 ms | 74 ms |
| Sydney | 204 ms | 1 ms | 3 ms | 214 ms |
| Tokyo | 303 ms | 2 ms | 7 ms | 320 ms |
| Toronto | 28 ms | 8 ms | 10 ms | 78 ms |
History
Incidents Figma reported
Since Oct 22, 15 days · from status.figma.com
- Incidents
- 1
- Major or critical
- 0
- Median to resolve
- 2d 10h
- lasted 2d 10h
Temporary Disruption with Sites
Unrated ·
Figma website availability
Measured by FlareWarden · figma.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 240ms
Last 30 days
91-day clean streakMeasured by FlareWarden's own checks of figma.com from multiple regions every 6 hours. Figma's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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 up to 17 cities across three regions to find out where it breaks.
Related services
Figma outage FAQ
Will I lose my work if Figma goes down?
Does the Figma desktop app work offline?
Can I still hand off designs to engineers during an outage?
Is FigJam affected by the same outages?
How we measure this
- We request Figma's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Figma itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Figma goes down
We check Figma every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring