Is Figma down?
Partially downchecked 5 minutes ago
Part of Figma is not answering our probes: its API from Europe, South America, US-East, UK, Asia-Pacific, US-Central, Southeast Asia, US-West, Australia and Canada. Its web surface, the surface we treat as the service's own, answered from every region we check.
As of Oct 5, 2026, 8:11 PM UTC, Figma answered RealUptime's probes in all 10 regions that returned a reading. Our US-East, US-West, Europe, Asia-Pacific, US-Central, Canada, UK, Southeast Asia, Australia and South America probes reached some of its surfaces and not others.
Last outage: 30d 7h on Aug 31, 2026 (web surface and API, from Europe, South America, US-East, UK, Asia-Pacific, US-Central, Southeast Asia, US-West, Australia and Canada).
Figma reports: All systems operational (“All Systems Operational”)
Figma's own component breakdown, as they publish it
- Admin, Billing & AI creditsOperational
- Community & ForumOperational
- Dev ModeOperational
- Email & NotificationsOperational
- File Browser & SearchOperational
- Figma agentOperational
- Figma DesignOperational
- FigJamOperational
- Figma MakeOperational
- Figma MotionOperational
- Figma SlidesOperational
- Figma WeaveOperational
- MCPOperational
- Plugins & WidgetsOperational
- Real-time collaboration serverOperational
- REST APIOperational
- Sign-in & Account AccessOperational
These are Figma's components, named and scored by Figma. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Figma's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Figma response time, by region
Is it Figma, or is it you?
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Figma -- it cannot diagnose Figma's own systems.
What we measured, function by function
Figma answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
- APIUS-East: DownUS-West: DownEurope: DownAsia-Pacific: DownUS-Central: DownCanada: DownUK: DownSoutheast Asia: DownAustralia: DownSouth America: Down
Get an email when we see Figma go down, and when it is back
Get told when we measure this
We will tell you when our probes stop reaching Figma, and again when they can reach it again. That is our own measurement from ten regions, not Figma's status page. No account, no card.
What we measured, and what people reported
- North AmericaPartially downUS-East, US-West, US-Central, Canada
- US-EastPartially downlatency: 526msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Figma normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestPartially downlatency: 1737msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Figma normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralPartially downlatency: 498msstatus code: 200checked: Oct 5, 2026, 8:05 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Figma normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaPartially downlatency: 357msstatus code: 200checked: Oct 5, 2026, 7:57 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Figma normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaPartially downlatency: 945msstatus code: 200checked: Oct 5, 2026, 8:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Figma normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropePartially downEurope, UK
- EuropePartially downlatency: 290msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Figma normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKPartially downlatency: 637msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Figma normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificPartially downAsia-Pacific, Southeast Asia, Australia
- Asia-PacificPartially downlatency: 738msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Figma normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaPartially downlatency: 1319msstatus code: 200checked: Oct 5, 2026, 7:57 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Figma normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaPartially downlatency: 927msstatus code: 200checked: Oct 5, 2026, 7:59 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Figma normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Figma, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Figma yet, which is not evidence that nothing is wrong.
Recent outages
measured entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Figma since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Figma covering any window you pick, with our measurements and Figma's own claim at the time, side by side.
Full availability history for Figma: 90-day availability by region, month-by-month uptime, and every incident on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/figma)<a href="https://realuptime.io/outages/figma"><img src="https://realuptime.io/outages/figma/badge.svg?days=30" alt="Figma uptime measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What Figma's SLA implies, from our measurement
Below your target
We measured 601h 50m of downtime for Figma over the last 30 days, which is 16.4100% uptime by our reading. A 99.9% target allows 43 minutes over that period.
That is 601h 7m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.
This is computed from our own probe measurements, not from Figma's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.