Databases
InfluxDB Cloud SLA credit guide
What InfluxDB Cloud owes you when it misses its uptime commitment — the credit tiers, the filing deadline, how to file, and a calculator to estimate your credit.
What SLA credit are you owed when InfluxDB Cloud is down?
When InfluxDB Cloud 2.0 falls below its 99.9% monthly uptime commitment, you're owed an SLA service credit worth 10%–50% of the affected service's monthly spend — larger the further uptime fell — claimable within 5 days of the end of the affected billing month. It's a credit toward a future invoice, not a cash refund.
Uptime commitment
99.9%
Filing window
5 days
counted from the end of the affected billing month
Services with SLA data
1
Credit calculator
Note: InfluxDB Cloud defines availability as a request success rate — the share of requests returning an error, averaged over short intervals — not as wall-clock uptime. Only InfluxDB Cloud can compute the official Monthly Uptime Percentage, from its own request logs. Use this as an estimate of what a qualifying shortfall would be worth, and ask InfluxDB Cloud to compute the contractual figure when you file.
SLA target is 99.9% — enter what you actually observed.
Enter your monthly spend above to see the dollar credit for a 10% tier.
Estimate only, from the vendor’s published tiers — the final credit is set by the vendor against your actual invoice and their SLA definitions.
Credit tiers by service
| Measured uptime | Credit |
|---|---|
| 99% – under 99.9% | 10% of spend |
| 95% – under 99% | 25% of spend |
| below 95% | 50% of spend |
Measured how? InfluxDB Cloud 2.0 is measured as a request success rate — errors as a share of total requests, averaged over short intervals — not as wall-clock uptime. Availability for this service is the vendor’s Monthly Uptime Percentage under that definition, which only InfluxDB Cloud can compute from its request logs. A status-page outage is evidence that a qualifying event happened; it is not the contractual figure.
FIVE CALENDAR DAYS, NOT BUSINESS DAYS, AFTER MONTH-END — the shortest window we track and practically unclaimable by hand, which is precisely the case for automated monitoring. Tiers are 10% between 99.0% and 99.9%, 25% between 95% and 98.99%, and 50% below 95%, aggregate credits capped at 50% of that month's usage-based fees. MEASUREMENT IS AN ERROR RATE AND OUR NUMBER IS THE WRONG METRIC: Unavailable means all continuous Requests to the Service in a one-minute interval fail with a 5xx. The minute only counts when ALL requests in it fail, so a partial outage, a regional degradation, or 4xx and timeout failures produce ZERO Unavailable Minutes. Ask InfluxData to compute the Monthly Availability Percentage under its own definition and offer our minutes as an indicator only. THE CLAIM ADDRESS COULD NOT BE READ: the document specifies email, but the address is obfuscated in the page HTML and must be confirmed with the vendor before a claim is drafted — do not guess it. InfluxData determines availability from its own system logs and reserves sole discretion to deny. Effective February 1, 2021. NOTE THERE ARE TWO DOCUMENTS: InfluxDB Cloud 3.0 Dedicated (effective September 1, 2023) carries the same tiers but allows TEN BUSINESS days after month-end, requires a minimum annual commitment as the fee denominator, applies only to production use, and adds a termination right if availability falls below 98.00% in any three of six consecutive months. This profile models Cloud 2.0, which is what the catalog entry maps to.
How to file a InfluxDB Cloud SLA credit claim
Portal: InfluxData (claim by email) ↗
- ⚠️ FIVE CALENDAR DAYS AFTER MONTH-END — not business days, and the shortest window we track anywhere. Diary it the moment a breach month closes; this is effectively unclaimable without automated monitoring.
- ⚠️ CONFIRM THE CLAIM EMAIL ADDRESS WITH INFLUXDATA FIRST: the SLA says to claim by email but the address is obfuscated in the page HTML and could not be read. Do not guess it — ask support, then send.
- ⚠️ OUR UPTIME FIGURE IS THE WRONG METRIC HERE: InfluxData counts a minute as Unavailable only when ALL continuous requests in that one-minute interval fail with a 5xx. A partial outage, a regional degradation, or 4xx and timeout failures produce zero Unavailable Minutes.
- So ask InfluxData to compute the Monthly Availability Percentage under its own definition and apply the tier that follows, offering our minutes as an indicator rather than as the claimed figure.
- State the dates and times the Service was Unavailable and include related logs documenting it — the SLA requires the logs, not a narrative.
- Tiers are 10% between 99.0% and 99.9%, 25% between 95% and 98.99%, and 50% below 95%, with aggregate credits capped at 50% of that month's fees.
- Note that InfluxData determines availability from its own system logs and reserves sole discretion to deny — and pays nothing while any payment is past due or you are in material breach.
- ⚠️ CHECK WHICH PRODUCT YOU ARE ON. This is InfluxDB Cloud 2.0. Cloud 3.0 Dedicated is a separate document with the same tiers but TEN BUSINESS days after month-end, a minimum-annual-commitment fee denominator, production-use-only scope, and a termination right if availability falls below 98.00% in any three of six consecutive months.
Evidence you’ll need
- •The dates and times the Service was Unavailable
- •Related logs documenting the Unavailability
Common exclusions
- •Scheduled and emergency maintenance
- •Customer breach of the agreement
- •Non-compliance with the Documentation
- •Unauthorized modification
- •Failure of third-party equipment
- •Force majeure
- •Any period where payments are past due or the customer is in material breach
Frequently asked
What is InfluxDB Cloud's SLA uptime commitment?
InfluxDB Cloud 2.0 carries a 99.9% monthly uptime commitment.
How much credit can I claim if InfluxDB Cloud misses its SLA?
Credits are tiered by measured uptime, from 10% up to 50% of the monthly service spend for the affected service, depending on how far below 99.9% availability fell.
What is the deadline to file a InfluxDB Cloud SLA credit claim?
Claims are generally due within 5 days of the end of the affected billing month (verify the exact clause in InfluxDB Cloud's SLA before filing).
Does Ontracko file InfluxDB Cloud SLA credit claims for me?
Ontracko monitors InfluxDB Cloud 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 InfluxDB Cloud and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.