Maintenance
Scheduled maintenance announced at least 48 hours in advance, and emergency maintenance performed to protect service integrity. Emergency notice will be provided when reasonably possible.
Service policy
This Service Level Agreement explains which paid services qualify, how monthly uptime is calculated, which events are excluded, and the service-credit remedy available when the commitment is not met.
Effective June 12, 2026
Scope and eligibility
The 99.9% monthly uptime commitment applies to active, paid Web Hosting, Managed WordPress Hosting, Agency Hosting, Cloud Hosting, NVMe VPS Hosting, Dedicated Server, Titan Business Email, Google Workspace, OX App Suite, and VPN Security services when the applicable order, product page, or service description references this SLA.
Domains, SSL certificates, backup products, monitoring products, professional services, migrations, trials, beta services, and complimentary services are not covered unless a written order states otherwise. Third-party services are covered only to the extent expressly stated in the applicable order.
Measurement method
Uptime is measured per eligible service for each calendar month. An eligible outage begins when the service is unable to accept connections or deliver its core hosted function from at least two independent external monitoring locations for five consecutive minutes, and the condition is confirmed by InterProWebHost monitoring or service logs.
Eligible unavailable minutes end when the service is restored. Brief interruptions below the five-minute confirmation threshold, partial degradation that does not prevent the service's core function, and excluded events are not counted as unavailable minutes.
Monthly uptime formula
Availability and credit bands
SLA remedy
When an eligible service falls below the monthly commitment because of eligible unavailable minutes, an approved credit is calculated against that service's monthly recurring charge, excluding taxes, one-time fees, add-ons, usage charges, licenses, and third-party fees.
| Monthly uptime percentage | Service credit | Remedy |
|---|---|---|
| 99.900% or higher | 0% | Commitment met; no credit applies. |
| 99.000%–99.899% | 10% | 10% of the affected service's monthly recurring charge. |
| 95.000%–98.999% | 25% | 25% of the affected service's monthly recurring charge. |
| Below 95.000% | 50% | 50% of the affected service's monthly recurring charge. |
What is not counted
Scheduled maintenance announced at least 48 hours in advance, and emergency maintenance performed to protect service integrity. Emergency notice will be provided when reasonably possible.
Force majeure, internet-wide routing failures, upstream carrier failures, government action, widespread power events, and third-party DNS, registrar, CDN, vendor, or network failures outside our reasonable control.
Distributed denial-of-service attacks, malicious traffic, compromises, abuse, or emergency protective actions unless the outage is directly caused by InterProWebHost failing to provide the contracted service.
Customer code, configuration, credentials, DNS changes, resource exhaustion, unsupported software, third-party integrations, account access, or failure to follow documented technical requirements.
Suspension, restriction, or termination arising from non-payment, fraud review, legal requirements, customer request, or violation of the Terms of Service or Acceptable Usage Policy.
Migrations, cutovers, maintenance windows, upgrades, customer-approved testing, beta services, trials, free services, and work performed at the customer's request.
Credit request process
A claim must be submitted through the client support portal within seven calendar days after the end of the affected month. The account must be current and in good standing. Customer monitoring can support a claim, but InterProWebHost monitoring, platform logs, and exclusion records determine eligibility in good faith.
Use the account associated with the affected service.
Provide the service ID, date, start and end time, timezone, and observed impact.
Include monitoring output, errors, traceroutes, or other relevant records when available.
We validate the event and apply an approved credit to the account balance.
Frequently asked questions
No. It is a monthly availability commitment for eligible services. Scheduled maintenance, excluded events, and short interruptions below the confirmation threshold are not counted as eligible downtime.
Your monitoring may support a claim, but it does not by itself determine eligibility. We reconcile customer evidence with InterProWebHost monitoring, service logs, incident records, and the exclusions in this SLA.
No. Submit a complete claim through the client support portal within seven calendar days after the affected month ends. This allows us to validate the service, duration, impact, and exclusions.
No. An approved SLA credit is applied to the account balance for future InterProWebHost charges. It has no cash value and is capped as described in the remedy table.
The recurring service fee for the billing term is divided by the number of months in that term. Taxes, one-time fees, add-ons, licenses, usage charges, and third-party fees are excluded.
Sign in to submit the affected service ID, timestamps, timezone, evidence, and impact details so our support team can investigate.