Service Level Agreement
We commit to 99.5% monthly uptime. This agreement sets out how we measure it and the service credits you can claim if we miss it.
1. Scope
1.1 This SLA applies to the embed, Render API and Inventory API on any plan with a monthly subscription fee: Lens, Hobby and every size of Pro, unless an account's written agreement says otherwise. On Lens it applies to the Render API, which is the only part of Lens it covers. Whether the Inspekt Lens extension works on a third-party website is outside it (Terms 3.6). So are Pro Studio and the cinematic render queue, on every plan.
1.2 Under this SLA, Enterprise is best effort, with no uptime commitment and no credits. Its uptime terms belong in its written agreement. An account with no plan (Terms 5.7) is not served and is outside this SLA. A free trial (Terms 5.8) has no fee and earns no credits.
2. Uptime commitment
2.1 We commit to 99.5% monthly uptime, calculated as:
Monthly Uptime % =
(total minutes in the calendar month - downtime minutes)
/ total minutes in the calendar month
x 100
measured per calendar month in UTC. The allowance is 0.5% of the month: 3 hours 36 minutes in a 30-day month, and about 3 hours 43 minutes in a 31-day month.
2.2 Downtime means minutes in which most well-formed requests to the embed, Render API or Inventory API return a server error (HTTP 5xx) or fail to answer within 30 seconds, measured under section 3, excluding anything covered by section 4.
3. Measurement
3.1 Our own monitoring is the authoritative source for downtime minutes. We run synthetic checks against the public surfaces every 5 minutes.
3.2 If you make a credit claim under section 7, we will give you the monitoring data we hold for that month on reasonable request.
4. Exclusions
The following do not count as downtime:
4.1 Scheduled maintenance, announced at least 48 hours ahead by email to your account contact, capped at 4 hours in a calendar month, and performed outside 09:00 to 21:00 US Mountain Time where that is reasonably practicable.
4.2 Your own or an end user's equipment, software, network or connectivity, or any third-party service you depend on other than ours.
4.3 Your breach of the agreement, misuse of your key, or traffic well beyond your plan or any reasonable expectation of it.
4.4 Force majeure: acts of God, war, terrorism, civil unrest, government action, internet backbone or DNS root failures, a widespread cloud or ISP outage outside our control, pandemics and similar events.
4.5 Valve changing, restricting or discontinuing access to the CS2 game files, item schema or Steam services we depend on, or any other third-party dependency changing or ending in a way that disrupts the service.
4.6 Features we have explicitly labelled beta, preview or experimental.
4.7 A denial-of-service or similar attack we mitigate in good faith, even where the mitigation itself causes some unavailability.
5. Service credits
If monthly uptime falls below 99.5%, you are entitled to a credit against that month's subscription fee:
| Monthly uptime | Credit |
|---|---|
| 99.0% to under 99.5% | 10% of that month's subscription fee |
| 95.0% to under 99.0% | 25% |
| 90.0% to under 95.0% | 50% |
| Under 90.0% | 100% |
Credits for a single month are capped at 100% of that month's subscription fee.
6. New content
The commitment to make newly released CS2 content available within 7 days is separate from uptime and is in Terms section 9.
7. Claiming a credit
7.1 Email hello@inspekt.gg within 30 days of the end of the affected month, with the dates and approximate times you saw downtime.
7.2 We check the claim against our monitoring under section 3 and, if the monitoring supports it, apply the credit to a future invoice. Credits are not paid in cash, are not transferable, and expire 12 months after they are issued.
8. Sole remedy
Service credits are your only remedy for our missing the uptime commitment in section 2.1. This limits remedies for downtime only. Your remedies for any other breach of the agreement are unaffected and remain subject to Terms section 13.
9. Changes
We update this SLA the same way we update the Terms, under Terms section 16.