Is Figma down right now?

No. Our checks are finding no problems with Figma right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Figma continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, can't log in, can't connect, slow or laggy, files won't sync, export or download failing and API errors. Those are the options the report button offers for Figma, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Figma specifically, the file service, the live multiplayer layer, shared libraries and exports are separate. One large file can fail to open while the rest of your workspace is fine, and multiplayer is a websocket a proxy or VPN can break without touching anything else. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Figma, open a small file in a private window on another network. Small files opening while one large file does not points at that file. The desktop app failing while the browser works points at the app or its cache. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Figma's side. Specifically: keep the tab open rather than reloading repeatedly. Figma holds unsaved changes in the session and reconnects on its own, and reloading during a multiplayer problem is what usually loses the last few edits. Version history recovers earlier states. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Figma publishes a machine-readable status feed, so our first check reads it directly and reports what Figma itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.figma.com, and it is linked further up this page. That is Figma's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Figma or figma.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Figma's own support, not us.