Is Figma down right now?
Live status for www.figma.com isn't set up in this environment yet - check any URL manually instead.
Checking www.figma.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
About Figma outages
Written by the HostTracker monitoring team · updated from live probe data.
Figma is a real-time collaborative design tool, and that real-time layer is exactly where its most distinctive failures show up: a live multiplayer or websocket connection issue can leave a file open and viewable while cursors stop moving and edits stop syncing between collaborators, which reads as a broken file rather than a connectivity problem. Large, complex files also behave differently from a full outage - a file that's slow or fails to fully load because of its own size and complexity is a performance limit, not the same thing as Figma being unreachable, and it's worth telling the two apart before assuming a platform-wide incident.
Common causes of Figma downtime
Multiplayer or websocket connection failures that stop live collaboration - cursors, edits, comments - from syncing between people in the same file while the file itself still opens
Very large or complex files failing to fully load or rendering slowly due to their own size, a performance limit rather than a platform-wide outage
Font and asset CDN incidents that leave text or images missing or broken inside a file while the editor itself is otherwise fully functional
SSO login incidents that block sign-in for organizations using single sign-on while Figma's core service stays healthy for everyone else
Divergence between the desktop app and the browser version, where an update or a local issue breaks one client while the other keeps working normally
Not sure whether it's Figma or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests www.figma.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Figma being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
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.
Run the live check at the top of this page - it tests www.figma.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Figma is reachable for everyone or only failing for you.
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.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.