Observability
Logz.io SLA credit guide
What Logz.io's own document actually says about uptime: a 99.8% target it aims at rather than a level it commits to, what that does and does not mean when a month goes badly, and where a real availability commitment for Logz.io would live.
What SLA credit are you owed when Logz.io is down?
Logz.io does not commit to an availability percentage, and pays no SLA service credit either. Its own document states a 99.8% monthly uptime target — a level it says it aims at, not one it guarantees — so there is no promised figure to fall below, nothing is breached when a period falls short of it, and there is nothing to file. The figure is Logz.io's own — it is transcribed from Logz.io's own document and this page does not suppress it — but Logz.io frames it as a level it aims at rather than one it guarantees, so there is no committed percentage to hold Logz.io to. If Logz.io has promised you a binding availability level, it lives in your own Order Form or negotiated agreement rather than on any public page. Where agreements in this class offer any remedy at all it is a termination or refund right after repeated consecutive misses rather than a per-incident credit, and some offer none even then, so read the exclusions below. Ontracko still monitors Logz.io for free — the dated outage record is what a renewal conversation runs on — but does not draft credit claims for it, so we won't tell you otherwise. One more thing about the deadline, because Logz.io 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 Logz.io claim, that date is our own monitoring reminder rather than anything Logz.io set — we will never let it expire a claim, and you should never quote it to Logz.io as their window.
Uptime target — not a commitment
99.8%
Filing window
Nothing to file
Services with SLA data
1
Credit tiers by service
No filable service credit exists for Logz.io (Target Uptime Availability — no credit) under the standard agreement — not a tier table gap, a genuine zero. THE COMMITTED FIGURE WAS WRONG AND HAS BEEN CORRECTED: Logz.io commits to an uptime of 99.8% per month, not the 99.9% this catalog previously published. THERE IS ALSO NO CREDIT TO CLAIM: the entire SLA is four short paragraphs — an uptime target plus two exclusion paragraphs — with no credit table, no remedy clause, no termination right and no claim process anywhere in it. Any recovery is a commercial negotiation or a breach argument under the master agreement, not an SLA credit claim, so do not draft one. IT IS DRAFTED AS A TARGET RATHER THAN A GUARANTEE: the heading reads Target Uptime Availability, the obligation is commercially reasonable efforts, and the document states the downtime metric is targeted at 0.2% per month. TWO FURTHER QUALIFIERS GUT THE MEASUREMENT: uptime is as measured by Logz.io with no customer audit right, and the Uptime definition excludes any scheduled AND UNSCHEDULED maintenance time — excluding unscheduled maintenance from the denominator is unusually broad and lets almost any remediation window be carved out. NO EFFECTIVE DATE OR VERSION IS STATED ANYWHERE on the page, which is itself a claim risk: we cannot prove which version governed a given outage. Offered only to paying customers; no plan tier or minimum commitment is stated.
Is there a Logz.io SLA credit to file?
No — there is nothing to file. Logz.io’s standard agreement doesn’t pay a per-incident service credit, so filing a claim would go nowhere. THE COMMITTED FIGURE WAS WRONG AND HAS BEEN CORRECTED: Logz.io commits to an uptime of 99.8% per month, not the 99.9% this catalog previously published. THERE IS ALSO NO CREDIT TO CLAIM: the entire SLA is four short paragraphs — an uptime target plus two exclusion paragraphs — with no credit table, no remedy clause, no termination right and no claim process anywhere in it. Any recovery is a commercial negotiation or a breach argument under the master agreement, not an SLA credit claim, so do not draft one. IT IS DRAFTED AS A TARGET RATHER THAN A GUARANTEE: the heading reads Target Uptime Availability, the obligation is commercially reasonable efforts, and the document states the downtime metric is targeted at 0.2% per month. TWO FURTHER QUALIFIERS GUT THE MEASUREMENT: uptime is as measured by Logz.io with no customer audit right, and the Uptime definition excludes any scheduled AND UNSCHEDULED maintenance time — excluding unscheduled maintenance from the denominator is unusually broad and lets almost any remediation window be carved out. NO EFFECTIVE DATE OR VERSION IS STATED ANYWHERE on the page, which is itself a claim risk: we cannot prove which version governed a given outage. Offered only to paying customers; no plan tier or minimum commitment is stated. Ontracko still tracks Logz.io’s uptime record for free, which is real leverage in a renewal conversation even without a claimable credit.
Common exclusions
- •Scheduled maintenance (at least 8 hours' notice, weekends where practicable)
- •Emergency maintenance, for which NO notice is given at all
- •Force majeure
- •Telecom, ISP and third-party hosting failures
- •Hardware, software or power outside Logz.io's control
- •Denial-of-service attacks
- •Third-party acts or omissions
Frequently asked
What is Logz.io's SLA uptime commitment?
Logz.io does not publish a commitment — it publishes a TARGET, and the difference is the whole answer. Logz.io (Target Uptime Availability — no credit) states a 99.8% monthly uptime target: a level Logz.io says it aims at, not one it guarantees, so nothing is contractually breached by a period that falls short of it. The figure is Logz.io's own — it is transcribed from Logz.io's own document and this page does not suppress it — but Logz.io frames it as a level it aims at rather than one it guarantees, so there is no committed percentage to hold Logz.io to. If Logz.io has promised you a binding availability level, it lives in your own Order Form or negotiated agreement rather than on any public page.
Does Logz.io pay an SLA service credit?
No — and there is no commitment behind it either, though for a different reason from a vendor that publishes nothing at all. Logz.io's own document states a 99.8% monthly uptime target rather than committing to a level, and provides no service credit, so nothing is contractually breached when a period falls short, and there is nothing to file. If Logz.io has promised you a binding availability level, it lives in your own Order Form or negotiated agreement — that document, not a public page, is where it would be. THE COMMITTED FIGURE WAS WRONG AND HAS BEEN CORRECTED: Logz.io commits to an uptime of 99.8% per month, not the 99.9% this catalog previously published. THERE IS ALSO NO CREDIT TO CLAIM: the entire SLA is four short paragraphs — an uptime target plus two exclusion paragraphs — with no credit table, no remedy clause, no termination right and no claim process anywhere in it. Any recovery is a commercial negotiation or a breach argument under the master agreement, not an SLA credit claim, so do not draft one. IT IS DRAFTED AS A TARGET RATHER THAN A GUARANTEE: the heading reads Target Uptime Availability, the obligation is commercially reasonable efforts, and the document states the downtime metric is targeted at 0.2% per month. TWO FURTHER QUALIFIERS GUT THE MEASUREMENT: uptime is as measured by Logz.io with no customer audit right, and the Uptime definition excludes any scheduled AND UNSCHEDULED maintenance time — excluding unscheduled maintenance from the denominator is unusually broad and lets almost any remediation window be carved out. NO EFFECTIVE DATE OR VERSION IS STATED ANYWHERE on the page, which is itself a claim risk: we cannot prove which version governed a given outage. Offered only to paying customers; no plan tier or minimum commitment is stated.
Does Ontracko file Logz.io SLA credit claims for me?
No — Logz.io's standard agreement has no filable service credit, so Ontracko does not draft claims for it. Ontracko still monitors Logz.io for free and tracks the uptime record, which is useful leverage at renewal.
Let Ontracko file it for you
Connect Logz.io and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.