Space for ads
Checked every 5 minutes · How we measure this
As of 18:30 EDT on 23 Oct 2026, figma.com responded to our check in 2,242 ms, with 99.65% availability over the last 24 hours.
Checked every 5 minutes · last checked 7 minutes ago
The line is response time measured from our probe to figma.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by Figma on its own status page. Verify on their status page.
The admin console, plan and seat management, billing, and AI credit allocation.
Browsing and publishing on Figma Community, and access to the Figma Community Forum.
Inspecting designs for implementation, measurements, generated code, and Code Connect.
Delivery of email and in-product notifications; invites, comment mentions, and digests.
Browsing, searching, and organizing your files and folders, including the home and recents views.
Prompting the Figma agent on the canvas in Figma Design, FigJam, and Slides.
Designing, editing, and prototyping in design files; including comments, libraries, and Draw.
Creating and collaborating on FigJam whiteboard files.
Prompting, previewing, and publishing in Figma Make, and the availability of already-published Make apps.
Animating on the canvas; the timeline, keyframes, and motion exports.
Building, editing, and presenting Figma Slides decks.
AI workflows for generating and editing imagery, video, and audio.
The Figma MCP server, which supplies design context to IDEs and coding agents.
Installing and running plugins and widgets, and the APIs they depend on.
Multiplayer; working in the same file as other people at the same time, with everyone's cursors and edits appearing live.
The Figma REST API, including webhooks, OAuth apps, SCIM provisioning, and activity logs.
Signing up and signing in to Figma, including SSO and SAML, staying signed in, and account recovery.
0 problem reports
Figma agent and Figma Make increased errors rates.
A fix has been implemented and we are monitoring the results.
Confirmed on the vendor status page
Figma outage
DownBits detected an outage on Figma between 27 Sep 2026, 06:40 – 06:55 IST, lasting ongoing. Detected across 3 consecutive automated checks of figma.com.
Detected by DownBits probe
Service disruption
Figma should now be operational. We are continuing to monitor.
Confirmed on the vendor status page
Figma is responding normally. Our last automated check of figma.com completed 7 minutes ago and succeeded in 2,242 ms. Over the past 24 hours the service answered 99.65% of our checks.
Measured from our automated checks, Figma has been available 99.65% over 24 hours, 99.90% over 7 days, 99.90% over 30 days. We recorded 3 incidents in the last 30 days.
Figma has averaged 1,572 ms across our successful checks in the past 24 hours, which is slower than ideal and may feel sluggish on a weak connection. Response time is measured from our probe to figma.com and does not include rendering time in your browser.
The most recent incident DownBits recorded for Figma began on 27 September 2026 at 06:40 IST and lasted 15 min. It was logged as outage. Detected by DownBits probe.
Our probe is reaching figma.com normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://figma.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than Figma. On Windows run ping figma.com and nslookup figma.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load figma.com in a private or incognito window. If it works there, clear cookies and site data for figma.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
