AI
OpenAI SLA credit guide
What OpenAI's own agreement actually says about availability: no uptime percentage, no credit schedule and no claim process, so there is nothing to file for a bad month — plus where a service level for OpenAI would live if you have one, and the outage record Ontracko keeps regardless.
What SLA credit are you owed when OpenAI is down?
OpenAI publishes NO availability SLA at all — no uptime percentage, no credit schedule and no claim process — so there is nothing to file for a bad month, and any "OpenAI uptime guarantee" figure circulating elsewhere did not come from OpenAI's own terms. If you have a service level with OpenAI, it lives in your own Order Form or negotiated agreement — that document, not a public page, is where the commitment and any remedy actually are. Ontracko monitors OpenAI for free either way and keeps the dated outage record, which is what a renewal conversation runs on. One more thing about the deadline, because OpenAI 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 OpenAI claim, that date is our own monitoring reminder rather than anything OpenAI set — we will never let it expire a claim, and you should never quote it to OpenAI as their window.
Uptime commitment
None published
Filing window
Nothing to file
Services with SLA data
1
Credit tiers by service
No filable service credit exists for OpenAI (Services Agreement / Service Terms — no availability SLA published) under the standard agreement — not a tier table gap, a genuine zero. NO AVAILABILITY SLA IS PUBLISHED. Both documents that constitute OpenAI's agreement were read: the Service Terms (updated September 10, 2026) and the OpenAI Services Agreement. Neither contains the phrase "Service Level Agreement", an availability percentage, an uptime definition or an outage credit; both were scanned for service level, uptime, availability, uninterrupted and "as is". ⚠️ THE SECTION HEADED "SERVICE CREDITS" IS NOT AN OUTAGE REMEDY, AND NAMING THAT IS THE WHOLE POINT OF THIS ENTRY. §6.5 of the Services Agreement reads: "Customer may need to prepay for Services by purchasing Service Credits. Service Credits are subject to the Service Credit Terms." Those are PREPAID PURCHASE credits — money a customer buys in order to spend it on the API — not compensation for downtime. Anyone searching OpenAI's terms for "service credit" lands on that heading and concludes an SLA remedy exists. It does not. WHAT OPENAI WARRANTS IS CONFORMITY, NOT AVAILABILITY: §12.1 provides that "OpenAI warrants that, during the Term, when used in accordance with this Agreement, the Services will conform in all material respects with the Documentation", and §12.2 disclaims everything else — "SUBJECT TO SECTION 12.1, THE SERVICES ARE PROVIDED "AS IS."" An outage is not on the face of it a failure to conform with the Documentation, so a status-page record is not by itself evidence for that warranty. BETA SERVICES ARE DISCLAIMED SEPARATELY AND ADDITIONALLY: OpenAI "makes no representations or warranties for Beta Services, including any warranty that Beta Services will be generally available, uninterrupted or error-free" (Service Terms §2). A THIRD DISTINCT THING, AND NOT A CLAIM ROUTE: the Services Agreement provides a channel for disputing an INVOICE, addressed to OpenAI's accounts-receivable team and running on its own short timetable from the invoice date. That is a BILLING dispute mechanism. It is not an SLA claim channel, it bars nothing about availability, and an outage claim must not be filed against it. IF A CUSTOMER HOLDS AN AVAILABILITY COMMITMENT FOR OPENAI, THE ONLY PLACE IT CAN LIVE IS THEIR OWN SIGNED ORDER FORM OR NEGOTIATED AGREEMENT — unpublished, and not verifiable from here. Read that agreement before asserting any figure. Primary sources read 20 September 2026.
Is there a OpenAI SLA credit to file?
No — there is nothing to file. OpenAI’s standard agreement doesn’t pay a per-incident service credit, so filing a claim would go nowhere. NO AVAILABILITY SLA IS PUBLISHED. Both documents that constitute OpenAI's agreement were read: the Service Terms (updated September 10, 2026) and the OpenAI Services Agreement. Neither contains the phrase "Service Level Agreement", an availability percentage, an uptime definition or an outage credit; both were scanned for service level, uptime, availability, uninterrupted and "as is". ⚠️ THE SECTION HEADED "SERVICE CREDITS" IS NOT AN OUTAGE REMEDY, AND NAMING THAT IS THE WHOLE POINT OF THIS ENTRY. §6.5 of the Services Agreement reads: "Customer may need to prepay for Services by purchasing Service Credits. Service Credits are subject to the Service Credit Terms." Those are PREPAID PURCHASE credits — money a customer buys in order to spend it on the API — not compensation for downtime. Anyone searching OpenAI's terms for "service credit" lands on that heading and concludes an SLA remedy exists. It does not. WHAT OPENAI WARRANTS IS CONFORMITY, NOT AVAILABILITY: §12.1 provides that "OpenAI warrants that, during the Term, when used in accordance with this Agreement, the Services will conform in all material respects with the Documentation", and §12.2 disclaims everything else — "SUBJECT TO SECTION 12.1, THE SERVICES ARE PROVIDED "AS IS."" An outage is not on the face of it a failure to conform with the Documentation, so a status-page record is not by itself evidence for that warranty. BETA SERVICES ARE DISCLAIMED SEPARATELY AND ADDITIONALLY: OpenAI "makes no representations or warranties for Beta Services, including any warranty that Beta Services will be generally available, uninterrupted or error-free" (Service Terms §2). A THIRD DISTINCT THING, AND NOT A CLAIM ROUTE: the Services Agreement provides a channel for disputing an INVOICE, addressed to OpenAI's accounts-receivable team and running on its own short timetable from the invoice date. That is a BILLING dispute mechanism. It is not an SLA claim channel, it bars nothing about availability, and an outage claim must not be filed against it. IF A CUSTOMER HOLDS AN AVAILABILITY COMMITMENT FOR OPENAI, THE ONLY PLACE IT CAN LIVE IS THEIR OWN SIGNED ORDER FORM OR NEGOTIATED AGREEMENT — unpublished, and not verifiable from here. Read that agreement before asserting any figure. Primary sources read 20 September 2026. Ontracko still tracks OpenAI’s uptime record for free, which is real leverage in a renewal conversation even without a claimable credit.
Frequently asked
What is OpenAI's SLA uptime commitment?
OpenAI does not publish one. Its own agreement states no uptime percentage anywhere, so there is no commitment to quote — any figure attributed to OpenAI elsewhere did not come from OpenAI's terms. If you hold a negotiated Order Form, any availability commitment you have lives there.
Does OpenAI pay an SLA service credit?
No — and there is no commitment behind it either. OpenAI's published agreement states no uptime percentage and provides no service credit, so there is no figure to miss and nothing to file for a bad month. If you have a service level with OpenAI, it lives in your own Order Form or negotiated agreement — that document, not a public page, is where any commitment and any remedy would be. NO AVAILABILITY SLA IS PUBLISHED. Both documents that constitute OpenAI's agreement were read: the Service Terms (updated September 10, 2026) and the OpenAI Services Agreement. Neither contains the phrase "Service Level Agreement", an availability percentage, an uptime definition or an outage credit; both were scanned for service level, uptime, availability, uninterrupted and "as is". ⚠️ THE SECTION HEADED "SERVICE CREDITS" IS NOT AN OUTAGE REMEDY, AND NAMING THAT IS THE WHOLE POINT OF THIS ENTRY. §6.5 of the Services Agreement reads: "Customer may need to prepay for Services by purchasing Service Credits. Service Credits are subject to the Service Credit Terms." Those are PREPAID PURCHASE credits — money a customer buys in order to spend it on the API — not compensation for downtime. Anyone searching OpenAI's terms for "service credit" lands on that heading and concludes an SLA remedy exists. It does not. WHAT OPENAI WARRANTS IS CONFORMITY, NOT AVAILABILITY: §12.1 provides that "OpenAI warrants that, during the Term, when used in accordance with this Agreement, the Services will conform in all material respects with the Documentation", and §12.2 disclaims everything else — "SUBJECT TO SECTION 12.1, THE SERVICES ARE PROVIDED "AS IS."" An outage is not on the face of it a failure to conform with the Documentation, so a status-page record is not by itself evidence for that warranty. BETA SERVICES ARE DISCLAIMED SEPARATELY AND ADDITIONALLY: OpenAI "makes no representations or warranties for Beta Services, including any warranty that Beta Services will be generally available, uninterrupted or error-free" (Service Terms §2). A THIRD DISTINCT THING, AND NOT A CLAIM ROUTE: the Services Agreement provides a channel for disputing an INVOICE, addressed to OpenAI's accounts-receivable team and running on its own short timetable from the invoice date. That is a BILLING dispute mechanism. It is not an SLA claim channel, it bars nothing about availability, and an outage claim must not be filed against it. IF A CUSTOMER HOLDS AN AVAILABILITY COMMITMENT FOR OPENAI, THE ONLY PLACE IT CAN LIVE IS THEIR OWN SIGNED ORDER FORM OR NEGOTIATED AGREEMENT — unpublished, and not verifiable from here. Read that agreement before asserting any figure. Primary sources read 20 September 2026.
Does Ontracko file OpenAI SLA credit claims for me?
No — OpenAI's standard agreement has no filable service credit, so Ontracko does not draft claims for it. Ontracko still monitors OpenAI for free and tracks the uptime record, which is useful leverage at renewal.
Let Ontracko file it for you
Connect OpenAI and Ontracko monitors the SLA, catches every breach, and drafts the claim with the evidence attached. Free — 8% only on recovered credits.