Is Figma down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, www.figma.com is responding normally to HostTracker's monitoring network, and has been up for 21d 4h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, www.figma.com is responding normally to HostTracker's monitoring network, and has been up for 21d 4h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

It's very likely a real-time connectivity issue rather than a full outage. Figma's live collaboration - cursors, simultaneous edits, comments appearing instantly - runs over its own multiplayer connection layered on top of the file itself, so that specific layer can fail while the file continues to open and display normally. This produces exactly the symptom of a file that looks static and unresponsive to others' changes even though nothing is actually broken about the file or the underlying service.

This usually points at the file's own size and complexity rather than a service problem. A file with a very large number of layers, components, or high-resolution images can take noticeably longer to load and render regardless of Figma's platform health, since that load is proportional to how much the file itself contains. If every other file opens quickly and only one specific file struggles, that's a performance limit on that file, not evidence of an outage.

That points specifically at an SSO incident rather than a Figma-wide outage. Organizations using single sign-on authenticate through a separate path from a plain email/password login, so a problem in that SSO integration can block an entire organization's sign-in while individual accounts using a direct login continue to work normally. Checking whether the issue is scoped to SSO specifically narrows the cause considerably.