Hosting & Edge
Webflow SLA credit guide
What Webflow's published SLA says, why this page quotes no uptime percentage for it — the committed figure is set in your own Order Form — and how to file against the terms that are.
What SLA credit are you owed when Webflow is down?
Webflow publishes an SLA — it just does not publish the percentage in it. Webflow's own document defines the committed uptime as whatever your Order Form (or Service Order) says, and sets the credit schedule the same way, so this page states no figure for Webflow and runs no calculator on one. That is NOT the same as Webflow publishing nothing or owing nothing: the commitment binds and the remedy is real — the two numbers are simply on your paper rather than on a public page. Read the committed uptime and the credit schedule off your own Order Form and apply them to the incident record below. Ontracko monitors Webflow for free, times every incident and assembles the dated evidence a claim is built on; that half is identical whatever your Order Form turns out to say.
Uptime target — not a commitment
Set in your Order Form
Filing window
7 days
counted from incident onset
Services with SLA data
1
Webflow’s committed uptime is in your Order Form, not on this page
Webflow publishes an SLA, but not the percentage in it: its own document defines the committed uptime as the figure set out in the applicable Order Form or Service Order, and sets the credit schedule the same way. So this page states no uptime percentage for Webflow and shows no calculator — a figure we cannot read out of Webflow’s paperwork is a figure we won’t assert, and any percentage attributed to Webflow elsewhere came from marketing copy rather than its terms.
This is not a vendor with nothing to file. The commitment binds and the remedy is real — both numbers are simply on your paper. Open your Webflow Order Form, read the committed uptime and the credit schedule off it, and apply them to the incident record below; everything else a claim needs, including the deadline and the filing route, is on this page. Ontracko drafts exactly that, and states no amount it cannot source.
Credit tiers by service
Webflow (SLA Terms and Conditions — Uptime Level set in the Order Form)’s committed uptime and its credit schedule are both set in your Order Form / Service Order, so there is no published tier table for us to show and this page transcribes none — read both off that document. The credit itself is real; it is the size of it that is private. THIS IS A CORRECTION: WEBFLOW DOES PUBLISH AN SLA, and an earlier batch recorded that it did not. The page at webflow.com/legal/sla is real (its 404 control returns "Error 404 | Webflow"; this returns "SLA | Webflow") and states "Last Modified: August 1, 2026 / Effective Date: September 1, 2026", but the page body is only a pointer — THE SUBSTANCE IS THE LINKED PDF, "WEBFLOW SERVICE LEVEL AGREEMENT TERMS AND CONDITIONS", footed "CONFIDENTIAL / Last Updated 09.01.2026", incorporated into Webflow's Master Subscription Agreement. THE TARIFF: on a Qualifying Downtime, Webflow "will issue Customer a credit equal to 2% of the Monthly Fees" (§2.4), where §1.2 defines Monthly Fees as the Fees prorated for the month the downtime occurs in and §1.3 defines a Qualifying Downtime as downtime in excess of thirty (30) consecutive minutes that causes Total Monthly Uptime to fall below the applicable Uptime Level. CREDITS ARE CAPPED AT 25% OF THE MONTHLY FEES PER CALENDAR MONTH, may not be redeemed for cash, may only be applied to the ensuing Renewal Term, and are the sole and exclusive remedy — so an outage-heavy month stops paying at a quarter of that month's fees however many 2% accruals it earned. ⚠️ THE TRAP, AND IT IS THE MOST EXPENSIVE CLAUSE IN THIS DOCUMENT: Qualifying Downtime "begins to accrue WHEN CUSTOMER NOTIFIES WEBFLOW AND WEBFLOW CONFIRMS THE OUTAGE, and continues until the Platform's availability is restored." The clock does not start when the outage starts — it starts when you report it and Webflow agrees. Every minute before the report is unpaid, so a customer who notices late has already lost that downtime whatever our monitoring recorded, and the correct action on a live incident is to open the ticket immediately rather than to wait and reconstruct it afterwards. THE FILING WINDOW COMPOUNDS IT: the written request is due within SEVEN (7) CALENDAR DAYS OF THE INITIAL QUALIFYING DOWNTIME — counted from onset, not from resolution and not from month-end — and failure to submit in time forfeits the credit outright. DO NOT COMPARE THAT SEVEN AGAINST OTHER VENDORS' DAY COUNTS: confluent, influxdata, launchdarkly and recurly all publish FIVE, and the first two of those run from MONTH-END, which makes their real windows far longer than this one. The anchor is what makes Webflow's window tight, not the number. ⚠️ THE UPTIME LEVEL ITSELF IS NOT PUBLISHED: §2.1 obliges Webflow only to use "commercially reasonable efforts to ensure that Total Monthly Uptime meets the Uptime Level thresholds specified on the applicable Order Form between the parties", so Ontracko cannot tell from the outside whether any given outage was a Qualifying Downtime at all — the 30-consecutive-minute floor is public, the threshold it has to breach is on the customer's own Order Form. Read it there before valuing anything, and treat our minutes as the evidence for a claim whose trigger only the customer can confirm. Uptime is published by Webflow at https://status.webflow.com/uptime; support tickets go to https://support.webflow.com/get-support, whose response-time commitments are a SEPARATE obligation and set no filing deadline.
How to file a Webflow SLA credit claim
- Open a billing/support case with the vendor from an account with billing authority.
- Paste the claim text from section 8 and attach the incident evidence from section 3.
- Ask explicitly for an SLA service credit under the availability commitment of your agreement.
Common exclusions
- •Scheduled Maintenance (at least five (5) days' advance notice via https://status.webflow.com)
- •(i) Customer-requested maintenance
- •(ii) Outages of third-party applications, utilities or integrations used by Customer (e.g. plug-ins or APIs)
- •(iii) Components or systems not within Webflow's reasonable control (e.g. Customer's proxies or DNS resolvers)
- •(iv) Denial of service or similar attacks
- •(v) Force Majeure Events
- •(vi) Any action taken by Webflow as required under Applicable Law or to ensure the stability and integrity of the Platform
Frequently asked
What is Webflow's SLA uptime commitment?
Webflow does not publish one. Its SLA defines the committed uptime as the percentage set out in the applicable Order Form or Service Order, so the figure is contractual and binding but private to each customer — there is nothing public to quote, and any percentage attributed to Webflow elsewhere came from marketing copy rather than from its terms. Read the committed uptime off your own Order Form; that document is the only primary source for it.
Does Webflow pay an SLA service credit?
Whatever Webflow owes you is set by the same document as the commitment — your Order Form or Service Order — rather than by a published tariff. That makes it different from a vendor with nothing to file: a remedy exists, Ontracko simply cannot read its size from anything Webflow publishes, so this page states no percentage and no amount instead of inventing one. Read the credit schedule off your Order Form and apply it to the incident record.
What is the deadline to file a Webflow SLA credit claim?
Claims are generally due within 7 days of incident onset (verify the exact clause in Webflow's SLA before filing).
Does Ontracko file Webflow SLA credit claims for me?
Ontracko monitors Webflow for free, detects and times every incident, and assembles the whole claim package except the two numbers Webflow keeps in your Order Form — the committed uptime and the credit schedule. Bring those from your own document and the claim is complete; we state no amount we cannot source. You file it; Ontracko charges 8% only on credits that are actually recovered.
Let Ontracko file it for you
Connect Webflow and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.