Figma: SLA evidence report
Figma: SLA evidence report
- Measured downtime
- 600h 11m
- Across 1 outage in this window.
- Window
- 2026-09-05 to 2026-10-05
- UTC, 30 days.
Aug 31, 2026, 2:15 PM UTC to Sep 30, 2026, 10:07 PM UTC
Multiple regions: Europe, South America, US-East, UK, Asia-Pacific, US-Central, Southeast Asia, US-West, Australia, Canada
600h 11mmeasured in this window
This outage started before the report window shown above; only the part inside the window counts toward the total.
Figma's claim at the time: Said operational the whole time we measured this outage (46.7m of this outage has no recorded claim either way)
What we probed
Methodology
Every outage above is a period our probes measured Figma as down from enough of the regions we check it from to count as a real outage, not a single unreliable reading (see how we tell the difference). Measured downtime is the wall-clock time inside the window an outage's regions were failing; regions failing together still count as one outage, not one per region.
Figma's claim at the time comes from their own public status feed, polled on our own schedule, and is shown separately from what we measured. We never change our own reading based on what a vendor claims, and their claim never becomes our reading.
This is one external observation from RealUptime's own regions, not Figma's own SLA measurement, which is usually defined against their own instrumentation and may cover a different scope than what we probe. The credit estimate above is a starting point for a conversation with Figma, not a legal determination, and RealUptime is not counsel.