Developer Tools
Codecov SLA credit guide
What Codecov pays when it misses its uptime commitment — its published tariff (5%, 10%, 25% or 50% of a quarter's fees), the quarter-end filing deadline and how to file. The unit is the calendar quarter, so no amount is computed here from a single month.
What SLA credit does Codecov pay when it misses?
Codecov (Harness Support Terms & SLA — Codecov Enterprise SaaS, quarterly) carries a 99.5% quarterly uptime commitment, and Codecov does pay a service credit for missing it. Its tariff is published and it is assessed on the CALENDAR QUARTER: 5%, 10%, 25% or 50% of that quarter's fees, depending how far the Quarterly Uptime Percentage fell. Harness will, in its sole discretion, either apply this Service Credit as a credit to your next invoice or pay it to you within forty-five (45) days following the end of the quarter in which it is due. The percentage applies only to the fees applicable to that calendar quarter for the affected Harness Platform module (Codecov), not to any other module, and the Service Credit is the sole and exclusive remedy for missing the Target Up Time. You must be current with payment of all fees under all applicable Order Forms to receive it. Ontracko measures calendar months, and three of them aggregate into that one quarterly figure, so a single bad month establishes no breach on its own: this page quotes no percentage against one month, no dollar amount and no calculator, because a figure priced off a month against a quarterly tariff can be out by a factor of three. File within 15 days of the end of the affected calendar quarter. Ontracko does that arithmetic for you once Codecov is connected: it scores all three calendar months, sums their downtime over the quarter's own minutes to get the Quarterly Uptime Percentage, reads the band off Codecov's published table and drafts the claim with the figure in it — and while a month of the quarter is still unscored it drafts protectively, stating no figure at all. Monitoring, incident timing and the dated evidence a claim is built on are free either way.
Uptime commitment
99.5%
Filing window
15 days
counted from the end of the affected calendar quarter
Services with SLA data
1
Codecov’s credit is assessed on the calendar quarter
Codecov publishes its tariff and applies it to the Quarterly Uptime Percentage — the availability of the whole quarter — and calculates the credit against the fees for that quarter. Three calendar months aggregate into that single figure, so one bad month establishes no breach on its own. This is the published table:
| Quarterly Uptime Percentage | Credit (% of that quarter's fees) |
|---|---|
| 98% – under 99.5% | 5% |
| 94% to 98% | 10% |
| 79% to 94% | 25% |
| below 79% | 50% |
Transcribed from Codecov’s own SLA (primary source ↗). The claim is due within 15 days of the end of the affected calendar quarter — read that anchor carefully, because a reader who counts the window from the incident date instead will believe a claim that is still live has already expired. Harness will, in its sole discretion, either apply this Service Credit as a credit to your next invoice or pay it to you within forty-five (45) days following the end of the quarter in which it is due. The percentage applies only to the fees applicable to that calendar quarter for the affected Harness Platform module (Codecov), not to any other module, and the Service Credit is the sole and exclusive remedy for missing the Target Up Time. You must be current with payment of all fees under all applicable Order Forms to receive it.
What this page does not do is put a number on it. It holds no spend figure for you and no scored months, so applying the table above to anything here would be a guess with a percentage sign on it — which is why there is no calculator on this page. Ontracko does that arithmetic for you once Codecov is connected: it scores all three calendar months, sums their downtime over the quarter's own minutes to get the Quarterly Uptime Percentage, reads the band off Codecov's published table and drafts the claim with the figure in it — and while a month of the quarter is still unscored it drafts protectively, stating no figure at all.
Credit tiers by service
Codecov (Harness Support Terms & SLA — Codecov Enterprise SaaS, quarterly)’s credit tariff is published, and it is assessed on the calendar quarter: 5%, 10%, 25% or 50% of that quarter's fees, depending how far the Quarterly Uptime Percentage fell — the table is above. Ontracko measures calendar months and three of them aggregate into that one quarterly figure, so a single month indexes no band here and this page computes no amount from one. A VERIFIED PAYER WHOSE TARIFF IS QUARTERLY, SO NO AMOUNT IS EVER PRICED OFF A SINGLE MONTH — the three months of the quarter are aggregated into one Quarterly Uptime Percentage first, and until all three are scored no figure is stated at all. THE DOCUMENT IS HARNESS'S: Harness acquired Codecov from Sentry (announced 2026-06-02, https://www.harness.io/press-and-news/harness-acquires-codecov); the about.codecov.io footer reads "© 2026 Harness Inc." and its "Terms of Service" link goes to the Harness Subscription Terms (https://www.harness.io/legal/subscription-terms — the old about.codecov.io/terms-of-service/ returns 404), whose §1.4 says "Harness will provide support for the applicable Module at service levels as described in the applicable Order Form and Support Terms and SLA, available at https://www.harness.io/legal/support-policy-sla". That Support Terms & SLA ("Version August 14, 2025") is Harness's platform-wide policy applied per module and does not name Codecov individually — the chain is footer ToS → Subscription Terms §1.4 → Support Terms & SLA, and the Codecov pricing page (https://about.codecov.io/pricing/) offers "an Enterprise-only SLA". SCOPE IS NARROW: Codecov Enterprise, SaaS only ("if Customer has licensed an on-premise version of the Harness Platform, Sections 3 and 4 of this policy shall not be applicable"), production instance only, and the Subscription Terms §5 says "NO WARRANTIES, INDEMNITIES, SLAS, OR SUPPORT APPLY TO TRIALS AND BETAS". THE FIGURE: Target Up Time 99.5% "in a given calendar quarter" on standard support (99.8% on premier); Availability "is calculated on a quarterly, per-minute, per Harness Platform module basis", where Downtime is the minutes the module "is completely inoperable or inaccessible". THE STANDARD TARIFF, as a percentage of the affected module's fees applicable to that calendar quarter: "Greater than 98%, less than 99.5%" → 5%; "Greater than 94%, less than or equal to 98%" → 10%; "Greater than or equal to 79%, less than or equal 94%" → 25%; "Less than 79%" → 50% (premier: >99.0% <99.8% → 5%, >95.0% ≤99.0% → 10%, ≥80% ≤95% → 25%, <80.0% → 50%). Three calendar months average into that one figure, so a single bad month establishes nothing on its own, and the profile therefore carries NO MONTHLY credit tiers. THE DEADLINE IS 15 DAYS AFTER THE END OF THE QUARTER: "Customer must submit a support ticket to Harness and provide any reasonably requested information or documentation supporting Customer’s claim for a Service Credit, within 15 days after the end of the calendar quarter in which Customer believes the Service Credit was earned." "Harness’s monitoring and logging infrastructure is the source of truth" for Availability. CREDIT MECHANICS: Harness "will, in its sole discretion, either (i) apply the Service Credit as a credit to Customer’s next invoice, or (ii) will pay Customer the Service Credit within forty five (45) days following the end of the quarter"; it "is Customer’s sole and exclusive remedy"; and §11 requires the Customer to be current with all fees to receive any Service Credit. Exclusions: Downtime caused by the Customer or its network, equipment or software, by the Customer's vendors, third-party connections or utilities, or by factors outside Harness's reasonable control (force majeure, global service provider outages, Internet problems beyond Harness's network), plus Scheduled Maintenance, modules not purchased and separate production instances. FOUR DECOYS, NOT THIS SLA: (1) the Sentry Terms of Service — Codecov's former owner, which disclaims uptime — must not be transcribed here; (2) §9 "Response Time" (2 business hours to 2 business days on standard) is a support-response commitment, not availability; (3) the $100,000 Continuous Delivery worked example is an illustration on a different module — and its "within thirty (30) days of the end of June" payout wording is not the operative 45-day rule; (4) the premier 99.8% table applies only to premier-support subscribers. The figure applies only under a Codecov Enterprise Order Form, and a negotiated Order Form may differ. Sources: https://www.harness.io/legal/support-policy-sla + https://www.harness.io/legal/subscription-terms + https://about.codecov.io/pricing/ + https://www.harness.io/press-and-news/harness-acquires-codecov, read first-hand 2026-10-09.
How to file a Codecov SLA credit claim
Portal: Harness Support (support ticket — Codecov is a Harness Platform module) ↗
- ⚠️ THIS SLA IS QUARTERLY: the tariff is applied to the module's Availability over the CALENDAR QUARTER and calculated against the fees applicable to that QUARTER, and three calendar months aggregate into that one figure — so a single bad month establishes no breach on its own, and no figure taken from one month means anything here. Ontracko computes the quarterly figure for you from the three scored months and prices the claim against the published bands; while any month of the quarter is still unscored it states no amount at all and files protectively, so check which quarter this claim covers, and whether it is complete, before quoting anything from it.
- ⚠️ THE DOCUMENT IS HARNESS'S, NOT CODECOV'S OR SENTRY'S. Harness acquired Codecov from Sentry; the about.codecov.io Terms of Service link now goes to the Harness Subscription Terms, whose §1.4 incorporates the Harness Support Terms & SLA (https://www.harness.io/legal/support-policy-sla, "Version August 14, 2025"). Do not cite the Sentry Terms of Service — they are Codecov's former owner's and carry no availability credit.
- Check the scope first — it is narrow: Codecov ENTERPRISE only (the pricing page offers "an Enterprise-only SLA"), the SaaS version only (on-premise / self-hosted installations are excluded), and only the production instance that hosts your licensed module. Trials and betas get nothing: "NO WARRANTIES, INDEMNITIES, SLAS, OR SUPPORT APPLY TO TRIALS AND BETAS".
- THE FULL STANDARD-SUPPORT TARIFF, as a percentage of the fees applicable to the affected QUARTER for the affected module: quarterly Availability greater than 98% and less than 99.5% → 5%; greater than 94% and less than or equal to 98% → 10%; greater than or equal to 79% and less than or equal to 94% → 25%; less than 79% → 50%. Mind the boundaries — exactly 98% pays 10% and exactly 94% pays 25%. If you hold PREMIER support the Target Up Time is 99.8% and the bands are >99.0% <99.8% → 5%, >95.0% ≤99.0% → 10%, ≥80% ≤95% → 25%, <80.0% → 50%; Ontracko prices the claim on the standard table, so re-band it yourself if you hold premier.
- ⏰ FIFTEEN DAYS AFTER THE END OF THE CALENDAR QUARTER — "within 15 days after the end of the calendar quarter in which Customer believes the Service Credit was earned". The window runs from quarter-end, not from the incident, and it is short: put the date in the calendar the moment the quarter closes.
- 🎫 FILE BY SUPPORT TICKET through Harness's ticketing system (https://www.harness.io/support). On standard support only your up to two (2) authorized support contacts may submit tickets, so file from one of those accounts. Name the calendar quarter in the subject, paste the claim text from section 8, and identify the affected module (Codecov) and its production instance.
- Be ready to supply "any reasonably requested information or documentation supporting Customer’s claim" — and expect Harness to price it off its own figures: "Harness’s monitoring and logging infrastructure is the source of truth". Our incident minutes are your corroborating evidence.
- Strip out the exclusions before totalling: Downtime caused by you or your network, equipment or software; by your vendors, third-party connections or utilities; by factors outside Harness's reasonable control (force majeure, global service provider outages, Internet problems beyond Harness's network); and Scheduled Maintenance.
- The credit is Harness's choice of form: applied to your next invoice, or paid to you within forty-five (45) days after the end of the quarter. It is the sole and exclusive remedy, and you must be current on all fees under your Order Forms to receive it.
Evidence you’ll need
- •Affected Harness Platform module (Codecov) and the production instance that hosts it
- •Calendar quarter claimed
- •Incident timestamps and duration
- •Any information or documentation Harness reasonably requests in support of the claim
Common exclusions
- •Downtime caused by Customer, Customer's network, equipment or software
- •Customer's vendors, third-party connections or utilities
- •Factors outside Harness's reasonable control, including force majeure, global service provider outages and Internet problems beyond Harness's network
- •Scheduled Maintenance
- •Harness Platform modules not purchased by Customer
- •Production instances separate from the one hosting Customer's licensed module
- •Codecov plans other than Enterprise
- •Trials and betas
- •On-premise / self-hosted installations
- •Premier support figures (99.8%) apply only to premier-support subscribers
Frequently asked
What is Codecov's SLA uptime commitment?
Codecov (Harness Support Terms & SLA — Codecov Enterprise SaaS, quarterly) carries a 99.5% quarterly uptime commitment.
Does Codecov pay an SLA service credit?
Yes, and its tariff is published. Codecov applies it to the Quarterly Uptime Percentage — the availability of the whole quarter — and credits 5%, 10%, 25% or 50% of that quarter's fees, the band depending on how far the quarterly figure fell. Harness will, in its sole discretion, either apply this Service Credit as a credit to your next invoice or pay it to you within forty-five (45) days following the end of the quarter in which it is due. The percentage applies only to the fees applicable to that calendar quarter for the affected Harness Platform module (Codecov), not to any other module, and the Service Credit is the sole and exclusive remedy for missing the Target Up Time. You must be current with payment of all fees under all applicable Order Forms to receive it. Because it is assessed on the CALENDAR QUARTER and not on a single month, this page quotes no percentage against one month and no dollar amount: three calendar months aggregate into that one figure, one bad month establishes no breach on its own, and a credit priced off a month against a quarterly table can be out by a factor of three. The claim is due within 15 days of the end of the affected calendar quarter. Ontracko does that arithmetic for you once Codecov is connected: it scores all three calendar months, sums their downtime over the quarter's own minutes to get the Quarterly Uptime Percentage, reads the band off Codecov's published table and drafts the claim with the figure in it — and while a month of the quarter is still unscored it drafts protectively, stating no figure at all.
What is the deadline to file a Codecov SLA credit claim?
Claims are generally due within 15 days of the end of the affected calendar quarter (verify the exact clause in Codecov's SLA before filing).
Does Ontracko file Codecov SLA credit claims for me?
Ontracko monitors Codecov 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 Codecov and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.