Figma Status
Official status page for Figma services.
Live Domain Check
Check if Figma is down right now (figma.com). Run a live multi-region check to see whether Figma is offline for everyone or just you.
Get official Figma outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Figma incidents can impact file loading, collaboration sync, commenting, or publishing independently. A quick status + endpoint check helps teams decide whether to pause release/design handoff workflows.
For Figma, incident signals are often feature-specific: Files list loads but opening specific files fails. Multiplayer cursors freeze or lag heavily. If this matches what you see on figma.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Figma publishes an official status page with incident details and uptime history.
Official status page for Figma services.
Official troubleshooting and support content.
Official developer references for API and plugin workflows.
Monitor real-time social updates and official posts related to Figma outages.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when figma.com seems down. Use this checklist to confirm whether Figma is down for everyone or only for you.
Run figma.com in WebsiteDown.org first, then open figma.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Figma service status page and compare timestamps with your failed checks.
Test related hosts such as status.figma.com, help.figma.com. If they work while figma.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for figma.com, then share those details with Figma support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Figma seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open figma.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on figma.com. Avoid repeated password or security resets until you confirm this is not a broader Figma issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Figma support.
Run the automatic multi-region check on this page for figma.com. If most regions fail at the same time, Figma is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether Figma is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full Figma outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for figma.com:
This order helps you avoid unnecessary account resets when the Figma issue is provider-side.