Version 1.0 · Last updated 21 October 2026 · Effective 21 November 2026
Service Level Commitments
How available we aim to keep the platform and cloud services each month, how we measure it, and the credits you can claim if we fall short.
1. What these commitments cover
- The platform (the Intersink panel, the Intersink API and channel apps): we aim for 99.9% availability each calendar month.
- Servers (Developers › Servers): we aim for 99.5% availability of each server’s network and power each calendar month.
- DNS for domains using our name servers: we aim for 99.9% availability.
- Availability is measured by our external monitoring from more than one location. A minute counts as unavailable when the service cannot be reached or answers with server errors throughout that minute.
2. What is not counted
- Planned maintenance we announced at least 48 hours ahead (limited to 4 hours a month), and emergency security work.
- Problems caused by you or your software, your internet connection, third-party services you chose, suspension under our terms, or events outside our reasonable control (force majeure).
- Beta, preview and free features.
3. Service credits
- Below the target but at least 99.0% in a month: a credit of 10% of that month’s charge for the affected service.
- Below 99.0%: 25%. Below 95.0%: 50%.
- Claim within 30 days of the end of the month through the Help Center, naming the affected service and times. Credits go on your next invoice, have no cash value, and in total cannot exceed the month’s charge for that service.
4. Status and incidents
Live status and incident reports are on the status page and in your panel. For incidents we publish what happened, its impact and what we changed to stop it happening again.
Questions about this document? Write to [email protected], or use the Help Center.