Design
Figma SLA credit guide
What Figma's own agreement actually says about availability: no uptime percentage, no credit schedule and no claim process, so there is nothing to file for a bad month — plus where a service level for Figma would live if you have one, and the outage record Ontracko keeps regardless.
What SLA credit are you owed when Figma is down?
Figma publishes NO availability SLA at all — no uptime percentage, no credit schedule and no claim process — so there is nothing to file for a bad month, and any "Figma uptime guarantee" figure circulating elsewhere did not come from Figma's own terms. If you have a service level with Figma, it lives in your own Order Form or negotiated agreement — that document, not a public page, is where the commitment and any remedy actually are. Ontracko monitors Figma for free either way and keeps the dated outage record, which is what a renewal conversation runs on. One more thing about the deadline, because Figma not stating one is not the same as there being none: file promptly anyway. A contract can carry a limitation period nobody printed, evidence ages badly, and the status-page record a claim is built on is easiest to defend while it is fresh. If Ontracko shows a date against a Figma claim, that date is our own monitoring reminder rather than anything Figma set — we will never let it expire a claim, and you should never quote it to Figma as their window.
Uptime commitment
None published
Filing window
Nothing to file
Services with SLA data
1
Credit tiers by service
No filable service credit exists for Figma (Software Services Agreement — no availability SLA published) under the standard agreement — not a tier table gap, a genuine zero. A DEFINITIVE NEGATIVE FROM AN ENUMERATED LEGAL INDEX PLUS A FULL READ OF THE ENTERPRISE AGREEMENT — not a failed search, which is the distinction that makes this profile worth having. figma.com/legal/ enumerates every document Figma publishes and lists NO Service Level Agreement: Software Services Agreement (Org/Enterprise), Terms of Service (Starter/Professional), Data Processing Addendum, Figma AI Terms, Community and Developer Terms, Creator Agreement, Figma Developer Terms, Figma Live Events, Acceptable Use Policy, Modern UK Slavery Act Statement, Transparency in Coverage, Code of Conduct, Community Code of Conduct, Digital Regulation Help Centre, Privacy & Trust Center, Copyright & IP Policy, Trademark Guidelines. Both figma.com/legal/sla/ and figma.com/sla/ HARD 404. THE ENTERPRISE AGREEMENT WAS READ IN FULL: the Software Services Agreement at figma.com/ssa/ — the Organization and Enterprise plan agreement, 49,599 bytes of rendered text — contains ZERO occurrences of "uptime", "service level agreement" or "service credit". ITS ONLY AVAILABILITY LANGUAGE IS A DESIGN STANDARD, NOT A MEASURED COMMITMENT: Figma undertakes "practices for redundancy, robustness, and scalability designed to maintain the availability of the Figma Platform", and separately security measures "designed to ensure the security, availability, integrity, and confidentiality of Customer Content". Neither states a percentage, neither defines a measurement period, and neither pays anything for a shortfall — "designed to maintain" is not a level and cannot be breached in a way a credit answers. THE 99.9 STORED IN slaCommitment ABOVE IS ONTRACKO'S GENERIC MONITORING DEFAULT, carried over so scoring still runs; it is NOT a Figma commitment and must never be presented as one. It is also the exact figure this catalog used to advertise for Figma on /vendor-directory ("99.9% SLA (org plans)") while /sla/figma simultaneously said the terms had not been transcribed — the contradiction that motivated the unverified-vendor guard in scripts/check-math.ts. If a customer believes an availability commitment applies, the only place one could live is their own Order Form or negotiated Enterprise agreement — unpublished, and not verifiable from here.
Is there a Figma SLA credit to file?
No — there is nothing to file. Figma’s standard agreement doesn’t pay a per-incident service credit, so filing a claim would go nowhere. A DEFINITIVE NEGATIVE FROM AN ENUMERATED LEGAL INDEX PLUS A FULL READ OF THE ENTERPRISE AGREEMENT — not a failed search, which is the distinction that makes this profile worth having. figma.com/legal/ enumerates every document Figma publishes and lists NO Service Level Agreement: Software Services Agreement (Org/Enterprise), Terms of Service (Starter/Professional), Data Processing Addendum, Figma AI Terms, Community and Developer Terms, Creator Agreement, Figma Developer Terms, Figma Live Events, Acceptable Use Policy, Modern UK Slavery Act Statement, Transparency in Coverage, Code of Conduct, Community Code of Conduct, Digital Regulation Help Centre, Privacy & Trust Center, Copyright & IP Policy, Trademark Guidelines. Both figma.com/legal/sla/ and figma.com/sla/ HARD 404. THE ENTERPRISE AGREEMENT WAS READ IN FULL: the Software Services Agreement at figma.com/ssa/ — the Organization and Enterprise plan agreement, 49,599 bytes of rendered text — contains ZERO occurrences of "uptime", "service level agreement" or "service credit". ITS ONLY AVAILABILITY LANGUAGE IS A DESIGN STANDARD, NOT A MEASURED COMMITMENT: Figma undertakes "practices for redundancy, robustness, and scalability designed to maintain the availability of the Figma Platform", and separately security measures "designed to ensure the security, availability, integrity, and confidentiality of Customer Content". Neither states a percentage, neither defines a measurement period, and neither pays anything for a shortfall — "designed to maintain" is not a level and cannot be breached in a way a credit answers. THE 99.9 STORED IN slaCommitment ABOVE IS ONTRACKO'S GENERIC MONITORING DEFAULT, carried over so scoring still runs; it is NOT a Figma commitment and must never be presented as one. It is also the exact figure this catalog used to advertise for Figma on /vendor-directory ("99.9% SLA (org plans)") while /sla/figma simultaneously said the terms had not been transcribed — the contradiction that motivated the unverified-vendor guard in scripts/check-math.ts. If a customer believes an availability commitment applies, the only place one could live is their own Order Form or negotiated Enterprise agreement — unpublished, and not verifiable from here. Ontracko still tracks Figma’s uptime record for free, which is real leverage in a renewal conversation even without a claimable credit.
Frequently asked
What is Figma's SLA uptime commitment?
Figma does not publish one. Its own agreement states no uptime percentage anywhere, so there is no commitment to quote — any figure attributed to Figma elsewhere did not come from Figma's terms. If you hold a negotiated Order Form, any availability commitment you have lives there.
Does Figma pay an SLA service credit?
No — and there is no commitment behind it either. Figma's published agreement states no uptime percentage and provides no service credit, so there is no figure to miss and nothing to file for a bad month. If you have a service level with Figma, it lives in your own Order Form or negotiated agreement — that document, not a public page, is where any commitment and any remedy would be. A DEFINITIVE NEGATIVE FROM AN ENUMERATED LEGAL INDEX PLUS A FULL READ OF THE ENTERPRISE AGREEMENT — not a failed search, which is the distinction that makes this profile worth having. figma.com/legal/ enumerates every document Figma publishes and lists NO Service Level Agreement: Software Services Agreement (Org/Enterprise), Terms of Service (Starter/Professional), Data Processing Addendum, Figma AI Terms, Community and Developer Terms, Creator Agreement, Figma Developer Terms, Figma Live Events, Acceptable Use Policy, Modern UK Slavery Act Statement, Transparency in Coverage, Code of Conduct, Community Code of Conduct, Digital Regulation Help Centre, Privacy & Trust Center, Copyright & IP Policy, Trademark Guidelines. Both figma.com/legal/sla/ and figma.com/sla/ HARD 404. THE ENTERPRISE AGREEMENT WAS READ IN FULL: the Software Services Agreement at figma.com/ssa/ — the Organization and Enterprise plan agreement, 49,599 bytes of rendered text — contains ZERO occurrences of "uptime", "service level agreement" or "service credit". ITS ONLY AVAILABILITY LANGUAGE IS A DESIGN STANDARD, NOT A MEASURED COMMITMENT: Figma undertakes "practices for redundancy, robustness, and scalability designed to maintain the availability of the Figma Platform", and separately security measures "designed to ensure the security, availability, integrity, and confidentiality of Customer Content". Neither states a percentage, neither defines a measurement period, and neither pays anything for a shortfall — "designed to maintain" is not a level and cannot be breached in a way a credit answers. THE 99.9 STORED IN slaCommitment ABOVE IS ONTRACKO'S GENERIC MONITORING DEFAULT, carried over so scoring still runs; it is NOT a Figma commitment and must never be presented as one. It is also the exact figure this catalog used to advertise for Figma on /vendor-directory ("99.9% SLA (org plans)") while /sla/figma simultaneously said the terms had not been transcribed — the contradiction that motivated the unverified-vendor guard in scripts/check-math.ts. If a customer believes an availability commitment applies, the only place one could live is their own Order Form or negotiated Enterprise agreement — unpublished, and not verifiable from here.
Does Ontracko file Figma SLA credit claims for me?
No — Figma's standard agreement has no filable service credit, so Ontracko does not draft claims for it. Ontracko still monitors Figma for free and tracks the uptime record, which is useful leverage at renewal.
Let Ontracko file it for you
Connect Figma and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.