Loading status…
Figma status · Collaboration · checked (1m ago)
No — Figma is not down. All Figma systems are reported operational.
According to Figma's official status page, Figma was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Figma's feed reported no outage in 100.00% of our checks.
Everything above is read from Figma's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Figma in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Figma is a browser-based design tool for interface design and prototyping, with FigJam for whiteboarding and Dev Mode for handing designs to engineers. Its defining feature is that editing is multiplayer and realtime, which means it depends on a live connection in a way most design tools do not.
Figma's status page separates the editor from multiplayer, file rendering and thumbnails, plugins, the API and the community site. Multiplayer is the component to watch: it is the realtime layer that syncs edits between people in the same file, and it can fail while files still open and load perfectly well — which presents as your collaborators' cursors freezing rather than as an outage.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Figma's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Figma was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Figma's status endpoint.
Figma has published 18 incidents in the last 12 months, newest first. Only what Figma posted itself — not every problem users hit.
resolved · Aug 26, 12:08 PM (24d ago)
resolved · Jul 27, 07:29 PM (54d ago)
resolved · Jun 18, 11:46 PM (93d ago)
resolved · Jun 16, 05:58 PM (95d ago)
resolved · Apr 20, 06:42 AM (152d ago)
resolved · Apr 9, 07:00 PM (163d ago)
resolved · Mar 12, 02:00 PM (191d ago)
resolved · Mar 6, 09:40 PM (197d ago)
resolved · Feb 17, 02:16 PM (214d ago)
resolved · Feb 5, 07:05 PM (226d ago)
resolved · Jan 29, 07:39 PM (233d ago)
resolved · Jan 27, 08:01 PM (235d ago)
resolved · Jan 23, 01:05 AM (240d ago)
resolved · Jan 7, 06:19 PM (255d ago)
resolved · Dec 15, 05:00 PM (278d ago)
resolved · Nov 18, 02:01 PM (305d ago)
resolved · Oct 20, 07:55 PM (334d ago)
resolved · Oct 1, 09:43 PM (353d ago)
Figma is demanding on the browser, and a file that will not open is often local: try the desktop app, or a hard refresh to clear a stale service worker. Large files hitting memory limits crash the tab rather than returning an error. If you can open a file but cannot edit it, check whether you have view-only permission on that project. Unsaved work is held locally and syncs when the connection returns, so a multiplayer drop is usually not data loss.
