Skip to content

Outage tracker / Figma

Is Figma down?

Short linkrlup.io/down/figma

I'm having a problem

Downchecked 22 minutes ago

Our probes cannot reach Figma from any of the 4 regions we check.

Functional endpoints verified

We have an outage open for Figma, 2d 11h so far.

Last outage: 59 min on Aug 28, 2026 (API, from Europe, US-East, Asia-Pacific and US-West).

our independent probeslive · checked Sep 3, 2026, 1:06 AM UTC
US-East459 msDown
US-West211 msDown
Europe200 msDown
Asia-Pacific1016 msDown
their status pagetheir claim, not our reading

Figma reports: All systems operational (“All Systems Operational”)

from Figma's own status page, checked Sep 3, 2026, 12:26 AM UTC
Our probes are seeing errors from Figma right now. Figma's own status page currently reports All Systems Operational. We are not able to explain the difference. It's possible the issue is limited to the specific request path we check, or that their status page has not updated yet.

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

US-East
605msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 490ms2026-08-21 UTC: p95 534ms2026-08-22 UTC: p95 476ms2026-08-23 UTC: p95 444ms2026-08-24 UTC: p95 715ms2026-08-25 UTC: p95 640ms2026-08-26 UTC: p95 988ms2026-08-27 UTC: p95 435ms2026-08-28 UTC: p95 618ms2026-08-29 UTC: p95 734ms2026-08-30 UTC: p95 578ms2026-08-31 UTC: p95 605ms
Aug 5Aug 19Sep 3
US-West
592msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 334ms2026-08-21 UTC: p95 490ms2026-08-22 UTC: p95 425ms2026-08-23 UTC: p95 503ms2026-08-24 UTC: p95 416ms2026-08-25 UTC: p95 439ms2026-08-26 UTC: p95 420ms2026-08-27 UTC: p95 678ms2026-08-28 UTC: p95 521ms2026-08-29 UTC: p95 652ms2026-08-30 UTC: p95 556ms2026-08-31 UTC: p95 592ms
Aug 5Aug 19Sep 3
Europe
401msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 444ms2026-08-21 UTC: p95 436ms2026-08-22 UTC: p95 583ms2026-08-23 UTC: p95 497ms2026-08-24 UTC: p95 666ms2026-08-25 UTC: p95 609ms2026-08-26 UTC: p95 466ms2026-08-27 UTC: p95 542ms2026-08-28 UTC: p95 454ms2026-08-29 UTC: p95 466ms2026-08-30 UTC: p95 503ms2026-08-31 UTC: p95 401ms
Aug 5Aug 19Sep 3
Asia-Pacific
771msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 980ms2026-08-21 UTC: p95 972ms2026-08-22 UTC: p95 972ms2026-08-23 UTC: p95 764ms2026-08-24 UTC: p95 841ms2026-08-25 UTC: p95 731ms2026-08-26 UTC: p95 692ms2026-08-27 UTC: p95 820ms2026-08-28 UTC: p95 962ms2026-08-29 UTC: p95 789ms2026-08-30 UTC: p95 698ms2026-08-31 UTC: p95 771ms
Aug 5Aug 19Sep 3

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 api 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.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: DownUS-West: DownEurope: DownAsia-Pacific: DownUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

Open incident

Aug 31, 2026, 2:15 PM UTCOngoing
multiple regions
open for 2d 11h so farUS-East: failing from Aug 31, 2026, 2:28 PM UTC, still failingUS-West: failing from Aug 31, 2026, 2:36 PM UTC, still failingEurope: failing from Aug 31, 2026, 2:15 PM UTC, still failingAsia-Pacific: failing from Aug 31, 2026, 3:31 PM UTC, still failing

What we measured, and what people reported

Our US-East, US-West, Europe and Asia-Pacific probes cannot reach Figma, without a matching rise in user reports.

  • US-East
    Downlatency: 459msstatus code: 401checked: Sep 3, 2026, 1:04 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes cannot reach Figma. We do not have enough reports from US-East to say whether people there are seeing it too.
  • US-West
    Downlatency: 211msstatus code: 401checked: Sep 3, 2026, 1:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes cannot reach Figma. We do not have enough reports from US-West to say whether people there are seeing it too.
  • Europe
    Downlatency: 200msstatus code: 401checked: Sep 3, 2026, 1:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes cannot reach Figma. We do not have enough reports from Europe to say whether people there are seeing it too.
  • Asia-Pacific
    Downlatency: 1016msstatus code: 401checked: Sep 3, 2026, 1:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes cannot reach Figma. We do not have enough reports from Asia-Pacific to say whether people there are seeing it too.
  • US-Central
    Not monitored from this regionFigma is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionFigma is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionFigma is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionFigma is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionFigma is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionFigma is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

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

Outage, 59mmeasured by our probes · Europe and US-East and Asia-Pacific and US-West2026-08-28
Figma MCP Disruption, 4h 11mdeclared on their status page2026-08-26
Service Disruption, 3h 21mdeclared on their status page2026-07-27
Figma Make disruption - Gemini 3.1 Pro, 12h 54mdeclared on their status page2026-06-18
Figma Make and Agent Service Disruption, 1mdeclared on their status page2026-06-16
Figma Make Service Disruption, 9h 8mdeclared on their status page2026-04-20
Figma Make Service Disruption, 21hdeclared on their status page2026-04-09
Figma Make Publishing Disruption, 8h 11mdeclared on their status page2026-03-12

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 servers

Tell me when this goes down

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.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Figma uptime measured by RealUptimeLive, from this page's own readings.
[![Figma uptime measured by RealUptime](https://realuptime.io/outages/figma/badge.svg?days=30)](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 60h 12m of downtime for Figma over the 337h 29m since we started watching it on 2026-08-20, which is 82.1577% uptime by our reading. A 99.9% target allows 20 minutes over that period.

That is 59h 52m 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.

What we check

primaryfunctional: live API
https://api.figma.com/v1/me
secondary
https://status.figma.com/
RealUptime is not affiliated with Figma; the name identifies what we measured, and nothing here speaks for Figma's own team. We send a single web request to Figma from 4 regions on our own schedule and time the response. We do not see inside Figma's systems, do not use an account or real transaction, and are not the same signal Figma's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Figma is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Figma operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.

Related services

Adobe Creative CloudAirtableAsanaBigCommerceBing