Figma Status service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Live Domain Check
Run a live reachability check for status.figma.com. Compare the regional responses with the problem you see in Figma Status.
Find Figma Status help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
A status.figma.com response tests the status page itself; inspect its incident details to assess an editor or API problem.
The checker above requests status.figma.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Figma Status action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Figma Help provides bug-report and log-collection guidance; choose the actual editor/API issue.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
Figma Help provides bug-report and log-collection guidance; choose the actual editor/API issue.
Open Figma Status help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Status-page URL, affected product, file/API error and UTC observation time.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Figma Status.
These are troubleshooting comparisons, not claims that Figma Status is currently experiencing a particular incident.
Match the affected component and incident time to your file or API error.
If the dashboard is unreachable, compare the actual editor/API and Figma Help before treating missing status information as an outage.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Figma Status seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open status.figma.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Figma Status issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Figma Status support.
Run the status.figma.com check and compare its original timestamps and responses with your actual error. A status.figma.com response tests the status page itself; inspect its incident details to assess an editor or API problem.
Use the official help/reporting resource linked above. Figma Help provides bug-report and log-collection guidance; choose the actual editor/API issue.
Match the affected component and incident time to your file or API error. If the dashboard is unreachable, compare the actual editor/API and Figma Help before treating missing status information as an outage.
Status-page URL, affected product, file/API error and UTC observation time.