Edge & Security
bunny.net SLA credit guide
What bunny.net's own document actually says about uptime: a 99.995% 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 bunny.net would live.
What SLA credit does bunny.net pay when it misses?
bunny.net does not commit to an availability percentage, and its binding agreement pays no SLA service credit. Its governing document states a 99.995% monthly uptime target — a level it says it aims at, not one it guarantees — so there is no promised figure to fall below and the binding contract is not breached when a period falls short of it. The figure is bunny.net's own — it is transcribed from bunny.net's own document and this page does not suppress it — but bunny.net frames it as a level it aims at rather than one it guarantees, so there is no committed percentage to hold bunny.net to. If bunny.net has promised you a binding availability level, it lives in your own Order Form or negotiated agreement rather than on any public page. bunny.net advertises an outage-credit table (denominated in service hours) on its marketing SLA page, which its binding Terms of Service neither incorporates nor honors and which publishes no claim process; a customer may be able to request a credit from bunny.net support, but the governing agreement guarantees none. So Ontracko quotes no figure, tier or claim deadline and drafts no claim against it — the binding contract guarantees none and the marketing page sets out no process — but the honest step for a bad month is to ask bunny.net support about that advertised credit rather than to treat the matter as settled. Ontracko still monitors bunny.net for free — the dated outage record is the evidence behind any such request, and your leverage at renewal. One more thing about the deadline, because bunny.net 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 bunny.net claim, that date is our own monitoring reminder rather than anything bunny.net set — we will never let it expire a claim, and you should never quote it to bunny.net as their window.
Uptime target — not a commitment
99.995%
Filing window
No published window
Services with SLA data
1
Credit tiers by service
No filable service credit exists for Bunny.net under its binding agreement — not a tier table gap, a genuine zero in the contract. bunny.net advertises an outage-credit table (denominated in service hours) on its marketing SLA page, which its binding Terms of Service neither incorporates nor honors and which publishes no claim process; a customer may be able to request a credit from bunny.net support, but the governing agreement guarantees none. So Ontracko quotes no figure, tier or claim deadline and drafts no claim against it — the binding contract guarantees none and the marketing page sets out no process — but the honest step for a bad month is to ask Bunny.net support about that advertised credit rather than to treat the matter as settled. THE BINDING CONTRACT PAYS NO SERVICE CREDIT, AND THE CREDIT TABLE THAT CIRCULATES IS ON A SEPARATE MARKETING PAGE THE CONTRACT DOES NOT HONOR. bunny.net has TWO contradicting availability surfaces, both read first-hand in full on 3 October 2026. (1) THE BINDING TERMS OF SERVICE (bunny.net/tos/), which opens "This is a legally binding contract between bunny.net and you" and states "All customers using our service are subject to the terms and conditions described in this document." Its entire "Service level agreement" section reads: "bunny.net will use all possible efforts to keep your service running 24 hours a day, 7 days a week, as long as you abide by our Terms of Service. We aim for at least a 99.995% monthly uptime for our content delivery service; however, sometimes, for a number of reasons, it may be unavailable to you. You recognize and acknowledge that occasional unavailability of the services will occur. We make no warranty or assurance that the service will run uninterrupted. We do not guarantee to provide support outside of normal business hours unless specifically stated by us." So the governing contract: a 99.995% monthly TARGET (verb "aim for", standard "all possible efforts"), an explicit no-warranty, and NO credit table, claim process, window, measurement definition or remedy of any kind. The ToS incorporates by reference only the Acceptable Use Policy and the privacy & data policy; it does NOT mention or incorporate the /sla/ page. (2) THE MARKETING SLA PAGE (bunny.net/sla/), headed "99.99% Uptime Guarantee", which states under "Outage Credits": "In the event of monthly availability falling below our guarantees, your account will be eligible for SLA credits based on your monthly usage." Its table is denominated in service HOURS (Monthly Availability | Outage Time | Credit Amount): 99.98% / 10-59 minutes / 12 hours; 99.85% / 1-2 hours / 24 hours; 99.70% / 2-4 hours / 48 hours; 99.50% / 4-7 hours / 120 hours; 99.00% / 7+ hours / 240 hours. It states no claim process, no filing window, no exclusions and no definition of how availability is measured. THE TWO SURFACES CONTRADICT ON ALL THREE LOAD-BEARING FACTS: the percentage (ToS 99.995% vs page 99.99%), the force (ToS "aim for" on "all possible efforts" and an express no-warranty — a target — vs the page's "Guarantee"), and the existence of a remedy (ToS none vs the page's outage-credit table). There is a documented gap even inside the marketing table: the 99.99% guarantee is about 4.32 minutes of downtime in a 30-day month, but the first credit row begins at 10 minutes of outage, so a month with 4.32-10 minutes of downtime is below the guarantee yet below the first credit threshold. THE DECISION (backlog item 47, option a): the BINDING ToS governs claim-drafting, so Ontracko ships bunny as a 99.995% monthly TARGET with NO contractual service credit and drafts no claim. The marketing table is RECORDED here (not suppressed), but it is NOT drafted against and NO filable remedy is computed from it: because bunny.net does advertise outage credits, a customer may be able to request a credit from bunny.net support even though the governing agreement guarantees none. If a binding availability commitment or remedy exists for a particular account it would live in that account's own bunny.net agreement, which is unpublished and not verifiable from here.
Is there a bunny.net SLA credit to file?
Not under bunny.net's binding agreement, which pays no per-incident service credit. bunny.net advertises an outage-credit table (denominated in service hours) on its marketing SLA page, which its binding Terms of Service neither incorporates nor honors and which publishes no claim process; a customer may be able to request a credit from bunny.net support, but the governing agreement guarantees none. So Ontracko quotes no figure, tier or claim deadline and drafts no claim against it — the binding contract guarantees none and the marketing page sets out no process — but the honest step for a bad month is to ask bunny.net support about that advertised credit rather than to treat the matter as settled. THE BINDING CONTRACT PAYS NO SERVICE CREDIT, AND THE CREDIT TABLE THAT CIRCULATES IS ON A SEPARATE MARKETING PAGE THE CONTRACT DOES NOT HONOR. bunny.net has TWO contradicting availability surfaces, both read first-hand in full on 3 October 2026. (1) THE BINDING TERMS OF SERVICE (bunny.net/tos/), which opens "This is a legally binding contract between bunny.net and you" and states "All customers using our service are subject to the terms and conditions described in this document." Its entire "Service level agreement" section reads: "bunny.net will use all possible efforts to keep your service running 24 hours a day, 7 days a week, as long as you abide by our Terms of Service. We aim for at least a 99.995% monthly uptime for our content delivery service; however, sometimes, for a number of reasons, it may be unavailable to you. You recognize and acknowledge that occasional unavailability of the services will occur. We make no warranty or assurance that the service will run uninterrupted. We do not guarantee to provide support outside of normal business hours unless specifically stated by us." So the governing contract: a 99.995% monthly TARGET (verb "aim for", standard "all possible efforts"), an explicit no-warranty, and NO credit table, claim process, window, measurement definition or remedy of any kind. The ToS incorporates by reference only the Acceptable Use Policy and the privacy & data policy; it does NOT mention or incorporate the /sla/ page. (2) THE MARKETING SLA PAGE (bunny.net/sla/), headed "99.99% Uptime Guarantee", which states under "Outage Credits": "In the event of monthly availability falling below our guarantees, your account will be eligible for SLA credits based on your monthly usage." Its table is denominated in service HOURS (Monthly Availability | Outage Time | Credit Amount): 99.98% / 10-59 minutes / 12 hours; 99.85% / 1-2 hours / 24 hours; 99.70% / 2-4 hours / 48 hours; 99.50% / 4-7 hours / 120 hours; 99.00% / 7+ hours / 240 hours. It states no claim process, no filing window, no exclusions and no definition of how availability is measured. THE TWO SURFACES CONTRADICT ON ALL THREE LOAD-BEARING FACTS: the percentage (ToS 99.995% vs page 99.99%), the force (ToS "aim for" on "all possible efforts" and an express no-warranty — a target — vs the page's "Guarantee"), and the existence of a remedy (ToS none vs the page's outage-credit table). There is a documented gap even inside the marketing table: the 99.99% guarantee is about 4.32 minutes of downtime in a 30-day month, but the first credit row begins at 10 minutes of outage, so a month with 4.32-10 minutes of downtime is below the guarantee yet below the first credit threshold. THE DECISION (backlog item 47, option a): the BINDING ToS governs claim-drafting, so Ontracko ships bunny as a 99.995% monthly TARGET with NO contractual service credit and drafts no claim. The marketing table is RECORDED here (not suppressed), but it is NOT drafted against and NO filable remedy is computed from it: because bunny.net does advertise outage credits, a customer may be able to request a credit from bunny.net support even though the governing agreement guarantees none. If a binding availability commitment or remedy exists for a particular account it would live in that account's own bunny.net agreement, which is unpublished and not verifiable from here. Ontracko still tracks bunny.net’s uptime record for free, which is real leverage in a renewal conversation even without a claimable credit.
Frequently asked
What is bunny.net's SLA uptime commitment?
bunny.net does not publish a commitment — it publishes a TARGET, and the difference is the whole answer. Bunny.net states a 99.995% monthly uptime target: a level bunny.net says it aims at, not one it guarantees, so nothing is contractually breached by a period that falls short of it. The figure is bunny.net's own — it is transcribed from bunny.net's own document and this page does not suppress it — but bunny.net frames it as a level it aims at rather than one it guarantees, so there is no committed percentage to hold bunny.net to. If bunny.net has promised you a binding availability level, it lives in your own Order Form or negotiated agreement rather than on any public page.
Does bunny.net 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. bunny.net's own document states a 99.995% monthly uptime target rather than committing to a level, and its binding agreement provides no service credit, so nothing is contractually breached when a period falls short. bunny.net advertises an outage-credit table (denominated in service hours) on its marketing SLA page, which its binding Terms of Service neither incorporates nor honors and which publishes no claim process; a customer may be able to request a credit from bunny.net support, but the governing agreement guarantees none. So Ontracko quotes no figure, tier or claim deadline and drafts no claim against it — the binding contract guarantees none and the marketing page sets out no process — but the honest step for a bad month is to ask bunny.net support about that advertised credit rather than to treat the matter as settled. THE BINDING CONTRACT PAYS NO SERVICE CREDIT, AND THE CREDIT TABLE THAT CIRCULATES IS ON A SEPARATE MARKETING PAGE THE CONTRACT DOES NOT HONOR. bunny.net has TWO contradicting availability surfaces, both read first-hand in full on 3 October 2026. (1) THE BINDING TERMS OF SERVICE (bunny.net/tos/), which opens "This is a legally binding contract between bunny.net and you" and states "All customers using our service are subject to the terms and conditions described in this document." Its entire "Service level agreement" section reads: "bunny.net will use all possible efforts to keep your service running 24 hours a day, 7 days a week, as long as you abide by our Terms of Service. We aim for at least a 99.995% monthly uptime for our content delivery service; however, sometimes, for a number of reasons, it may be unavailable to you. You recognize and acknowledge that occasional unavailability of the services will occur. We make no warranty or assurance that the service will run uninterrupted. We do not guarantee to provide support outside of normal business hours unless specifically stated by us." So the governing contract: a 99.995% monthly TARGET (verb "aim for", standard "all possible efforts"), an explicit no-warranty, and NO credit table, claim process, window, measurement definition or remedy of any kind. The ToS incorporates by reference only the Acceptable Use Policy and the privacy & data policy; it does NOT mention or incorporate the /sla/ page. (2) THE MARKETING SLA PAGE (bunny.net/sla/), headed "99.99% Uptime Guarantee", which states under "Outage Credits": "In the event of monthly availability falling below our guarantees, your account will be eligible for SLA credits based on your monthly usage." Its table is denominated in service HOURS (Monthly Availability | Outage Time | Credit Amount): 99.98% / 10-59 minutes / 12 hours; 99.85% / 1-2 hours / 24 hours; 99.70% / 2-4 hours / 48 hours; 99.50% / 4-7 hours / 120 hours; 99.00% / 7+ hours / 240 hours. It states no claim process, no filing window, no exclusions and no definition of how availability is measured. THE TWO SURFACES CONTRADICT ON ALL THREE LOAD-BEARING FACTS: the percentage (ToS 99.995% vs page 99.99%), the force (ToS "aim for" on "all possible efforts" and an express no-warranty — a target — vs the page's "Guarantee"), and the existence of a remedy (ToS none vs the page's outage-credit table). There is a documented gap even inside the marketing table: the 99.99% guarantee is about 4.32 minutes of downtime in a 30-day month, but the first credit row begins at 10 minutes of outage, so a month with 4.32-10 minutes of downtime is below the guarantee yet below the first credit threshold. THE DECISION (backlog item 47, option a): the BINDING ToS governs claim-drafting, so Ontracko ships bunny as a 99.995% monthly TARGET with NO contractual service credit and drafts no claim. The marketing table is RECORDED here (not suppressed), but it is NOT drafted against and NO filable remedy is computed from it: because bunny.net does advertise outage credits, a customer may be able to request a credit from bunny.net support even though the governing agreement guarantees none. If a binding availability commitment or remedy exists for a particular account it would live in that account's own bunny.net agreement, which is unpublished and not verifiable from here.
Does Ontracko file bunny.net SLA credit claims for me?
No — bunny.net's standard agreement has no filable service credit, so Ontracko does not draft claims for it. Ontracko still monitors bunny.net for free and tracks the uptime record, which is useful leverage at renewal.
Let Ontracko file it for you
Connect bunny.net and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.