🗺️

Collaboration

Miro SLA credit guide

What Miro owes you when it misses its uptime commitment — the credit tiers, the filing deadline, how to file, and why its credit has no dollar figure attached.

What SLA credit are you owed when Miro is down?

When Miro (Service Level Agreement under the Master Cloud Agreement) falls below its 99.5% monthly uptime commitment, you're owed an SLA service credit of 5%–30% — larger the further uptime fell — claimable within 30 days of the end of the affected billing month. Read what that percentage applies to: Miro calculates it against the monthly portion of the annual fees due for the affected Service in that month — an annual fee pro-rated, which is not the month's invoice even though the table's own header reads "Service Credit (% of monthly fees)", not against your invoice, so it has no dollar value we can compute for you and we quote none. Quote the tier and ask Miro to apply it to that base.

What is an SLA credit? · SLA glossary

Uptime commitment

99.5%

Filing window

30 days

counted from the end of the affected billing month

Services with SLA data

1

Miro’s credit is a percentage of something other than your bill

The tier percentages below are real and they are Miro’s own. What they are a percentage of is not the spend Ontracko records — Miro applies them to the monthly portion of the annual fees due for the affected Service in that month — an annual fee pro-rated, which is not the month's invoice even though the table's own header reads "Service Credit (% of monthly fees)". That is a figure Ontracko does not hold, so there is no dollar amount to calculate here and we don’t show a calculator: applying 30% to the wrong base produces a number that is either an overclaim or an underclaim, and both get argued back at you instead of paid.

File it anyway. The shortfall, the evidence and the filing deadline — within 30 days of the end of the affected billing month — are unchanged — what changes is the ask: quote the tier, name the base Miro’s own document sets, and ask Miro to compute the amount against it. Ontracko drafts exactly that.

Credit tiers by service

Miro (Service Level Agreement under the Master Cloud Agreement)99.5% target · 30 days from month-end
Measured uptimeCredit
99% – under 99.5%5%
98.5% – under 99%10%
98% – under 98.5%15%
97.5% – under 98%20%
below 97.5%30%

A percentage of what? Miro (Service Level Agreement under the Master Cloud Agreement)’s credit is a percentage of the monthly portion of the annual fees due for the affected Service in that month — an annual fee pro-rated, which is not the month's invoice even though the table's own header reads "Service Credit (% of monthly fees)" — not of your invoice. The Credit column above is that percentage, and it converts to no dollar figure we can compute for you, because that base is not a figure Ontracko holds — quote the tier and ask Miro to apply it to the base its own SLA sets.

A VERIFIED PAYER WITH A FIVE-BAND TABLE AND NO DATE ON ITS OWN DOCUMENT. Source: the Miro Service Level Agreement PDF at miro.com/legal/documents/Miro-Service-Level-Agreement.pdf, linked from the Master Cloud Agreement at miro.com/legal/master-cloud-agreement/. ⚠️ THE DOCUMENT STATES NO EFFECTIVE OR LAST-UPDATED DATE ANYWHERE. That is a finding, not a gap in the transcription: there is no version to cite, so ask Miro which version is operative before filing. WHO IS ACTUALLY COVERED: the SLA "is issued under and forms part of the Master Cloud Agreement or other Miro agreement which references this policy", and it names NO plan tier — so it binds customers contracted under the Master Cloud Agreement, which is not the same statement as "Enterprise only" and must not be written as one. A separate read of Miro's self-serve Terms of Service found zero occurrences of "SLA", "Availability Standard" or "Service Credit", which indicates a self-serve Free, Starter or Business subscriber has no availability commitment at all; that negative is a secondary read rather than a verbatim transcription, and is recorded as such. THE STANDARD: ""Availability Standard" means uptime availability of the Service at a level of at least 99.5% availability measured on a monthly basis, excluding scheduled maintenance time." ⚠️ THE SENTENCE A VENDOR REP WILL QUOTE BACK IS THE EFFORTS QUALIFIER: §1 says Miro "will use commercially reasonable efforts to provide the Service to Customer at the Availability Standard set forth below". The credit does not turn on the effort — it triggers "If Miro fails to meet the Availability Standard in a particular month", which is the measured number — so the remedy is indexed on the figure, and the efforts language does not soften it away. WHAT COUNTS AS DOWN: "The Service will be deemed unavailable if Customer is unable to access the Service ("Disruption")." That is a WHOLE-SERVICE ACCESS test: one broken feature, however important, is not a Disruption. THE PUBLISHED TABLE, exactly as printed: 99.5% or greater — No Credit; 99.00% to 99.5% — 5%; 98.5% to 99.00% — 10%; 98.00% to 98.5% — 15%; 97.5% to 98.00% — 20%; less than 97.5% — 30%. ⚠️ THE BANDS AS PRINTED SHARE THEIR ENDPOINTS and Miro does not say which side a boundary falls on. Ontracko indexes a figure on the band it falls inside and resolves each shared endpoint into the higher, cheaper band — so a month at exactly 99.00% is read as 5% and a month at exactly 99.5% as no credit, which is the one boundary Miro did settle ("99.5% or greater — No Credit"). That convention is OURS, not Miro's; if a month lands exactly on a printed boundary, say so and let Miro apply its own reading. ⚠️ THE CREDIT BASE IS AN ANNUAL FEE PRO-RATED AND THE DOCUMENT DISAGREES WITH ITSELF ABOUT IT: the body entitles the customer to "a credit based on the monthly portion of the annual fees due for the affected Service in such month", while the table's own header reads "Service Credit (% of monthly fees)". The body governs, so the percentage applies to the pro-rated annual fee and it is not your monthly fee as invoiced — which is the figure a customer will otherwise compute against. Ontracko states no dollar amount for Miro for that reason. ⏰ THIRTY DAYS FROM THE END OF THE MONTH: the credit is payable only if "Customer makes a request for service credits within 30 days after the end of such month". ⚠️ THE SLA PRESCRIBES NO CHANNEL FOR THAT REQUEST — no email address, no portal, no subject line, no identifier. Miro's separate Support Policy PDF names the general incident channel, "the support ticketing portal at https://miro.com/contact/support/", and in practice that is where a claim has to go; note what that is, though — the GENERAL SUPPORT channel, not a credit channel the SLA sets out — so say plainly in the ticket that it is a request for service credits under the SLA, and keep the dated proof that it was sent inside the window. ⚠️ ELIGIBILITY BAR: "Miro will apply each Service Credit to Customer's next invoice, provided that Customer's account is fully paid up, without any outstanding payment issues or disputes. Customer will not receive any refunds for any unused Service Credits." An open billing dispute forfeits the credit — settle the invoice before filing. EXCLUDED (§1.a, verbatim): "(i) general internet problems or outages caused by power supply carriers; (ii) malfunction of equipment, systems software, network connections or other infrastructure not owned or operated by Miro; (iii) force majeure events or other factors outside the reasonable control of Miro or (iv) scheduled service or maintenance or reasonable emergency maintenance." THE SLA STATES NO EVIDENCE REQUIREMENT of any kind, so this profile transcribes none. EXCLUSIVE REMEDY: "Service Credits constitute liquidated damages and are not a penalty. Service Credits are Customer's sole and exclusive remedy, and Miro's sole and exclusive liability, for Miro's failure to meet the Availability Standard."

How to file a Miro SLA credit claim

Portal: Miro Support — the support ticketing portal ↗

  1. ⚠️ THE SLA NAMES NO CHANNEL FOR THE CREDIT REQUEST — no email address, no portal, no subject line, no identifier. It says only that the customer must make "a request for service credits within 30 days after the end of such month". Miro's separate Support Policy names the general incident channel — "the support ticketing portal at https://miro.com/contact/support/" — and in practice that is where the request has to go. Understand what that is: the GENERAL SUPPORT channel, not a credit channel the SLA prescribes. So say in the ticket, in words, that this is a request for service credits under the SLA's Availability Standard, and keep dated proof that it was submitted inside the window.
  2. ⏰ THIRTY DAYS AFTER THE END OF THE MONTH the Availability Standard was missed in — the window runs from month-end, not from the incident. Put the date in the calendar the moment the month closes.
  3. CHECK THE SCOPE FIRST, AND DO NOT CALL IT "ENTERPRISE ONLY": the SLA "is issued under and forms part of the Master Cloud Agreement or other Miro agreement which references this policy", and it names no plan tier at all. It binds customers contracted under the Master Cloud Agreement. Miro's self-serve Terms of Service contain no SLA, no Availability Standard and no Service Credit, so a Free, Starter or Business subscriber on self-serve paper has no availability commitment to claim under — confirm which paper the customer is on before filing.
  4. THE FULL TABLE, as printed: 99.5% or greater → No Credit; 99.00% to 99.5% → 5%; 98.5% to 99.00% → 10%; 98.00% to 98.5% → 15%; 97.5% to 98.00% → 20%; less than 97.5% → 30%. ⚠️ THE BANDS SHARE THEIR ENDPOINTS AND MIRO DOES NOT SAY WHICH SIDE A BOUNDARY FALLS ON. Ontracko resolves each shared endpoint into the higher, cheaper band — a month at exactly 99.00% reads as 5% — which agrees with the one boundary Miro did settle ("99.5% or greater — No Credit"). That convention is ours. If the month lands exactly on a printed boundary, say so in the ticket and let Miro apply its own reading rather than arguing a band you cannot source.
  5. ⚠️ THE PERCENTAGE IS NOT APPLIED TO YOUR MONTHLY INVOICE, AND THE DOCUMENT DISAGREES WITH ITSELF ABOUT THIS. The body entitles the customer to "a credit based on the monthly portion of the annual fees due for the affected Service in such month"; the table's own header reads "Service Credit (% of monthly fees)". The body governs — take the annual fee for the affected Service, divide it by twelve, and apply the band to that. Ontracko quotes no dollar figure for Miro because the annual fee is not a quantity it holds.
  6. ⚠️ IT IS A WHOLE-SERVICE TEST: "The Service will be deemed unavailable if Customer is unable to access the Service ("Disruption")." One broken feature — however important — is not a Disruption. Build the claim on windows where the Service as a whole was unreachable.
  7. ⚠️ ELIGIBILITY BAR THAT FORFEITS THE CREDIT OUTRIGHT: "Miro will apply each Service Credit to Customer's next invoice, provided that Customer's account is fully paid up, without any outstanding payment issues or disputes." An open billing dispute costs the credit, and there are no refunds for unused Service Credits. Settle the invoice before filing.
  8. Expect the "commercially reasonable efforts" sentence back, and know the answer: §1 does say Miro "will use commercially reasonable efforts to provide the Service to Customer at the Availability Standard", but the credit clause triggers "If Miro fails to meet the Availability Standard in a particular month" — on the measured number, not on the endeavour. The efforts language does not turn a table with five bands into a target.
  9. Strip out the exclusions before totalling (§1.a): general internet problems or outages caused by power supply carriers; malfunction of equipment, systems software, network connections or other infrastructure not owned or operated by Miro; force majeure and other factors outside Miro's reasonable control; and scheduled service or maintenance or reasonable emergency maintenance. Scheduled maintenance is also excluded from the Availability Standard itself.
  10. THE SLA ASKS FOR NO EVIDENCE AT ALL — no account identifier, no logs, no incident reference. That is a gap in the document rather than a licence to send nothing: include the account and affected Service, the Disruption dates, times and durations, and the Miro incident references from status.miro.com, and label them as supporting material rather than as items the SLA requires.
  11. ⚠️ SOURCE NOTE: the Miro Service Level Agreement PDF (miro.com/legal/documents/Miro-Service-Level-Agreement.pdf, linked from the Master Cloud Agreement) STATES NO EFFECTIVE OR LAST-UPDATED DATE ANYWHERE. There is no version to cite, so ask Miro to confirm which version is operative for this customer before filing. Service Credits are the sole and exclusive remedy for a missed Availability Standard, and Miro states they are liquidated damages rather than a penalty.

Common exclusions

  • •General internet problems or outages caused by power supply carriers
  • •Malfunction of equipment, systems software, network connections or other infrastructure not owned or operated by Miro
  • •Force majeure events or other factors outside the reasonable control of Miro
  • •Scheduled service or maintenance, or reasonable emergency maintenance

Frequently asked

What is Miro's SLA uptime commitment?

Miro (Service Level Agreement under the Master Cloud Agreement) carries a 99.5% monthly uptime commitment.

How much credit can I claim if Miro misses its SLA?

Credits are tiered by measured uptime, from 5% up to 30%, depending on how far below 99.5% availability fell. Note what the percentage applies to: Miro calculates it against the monthly portion of the annual fees due for the affected Service in that month — an annual fee pro-rated, which is not the month's invoice even though the table's own header reads "Service Credit (% of monthly fees)", not against your invoice — so this page states no dollar amount and shows no calculator. Quote the tier and ask Miro to apply it to that base.

What is the deadline to file a Miro SLA credit claim?

Claims are generally due within 30 days of the end of the affected billing month (verify the exact clause in Miro's SLA before filing).

Does Ontracko file Miro SLA credit claims for me?

Ontracko monitors Miro for free, detects SLA breaches automatically, and assembles the complete claim package (evidence + credit math + claim text). You file it; Ontracko charges 8% only on credits that are actually recovered.

Let Ontracko file it for you

Connect Miro and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.

Other vendor SLA guides