Hosting
Servers
Pricing
Resources
Get started → Log in

Service Level Agreement
99.95% monthly uptime.

Version 1.0 · Effective 14 November 2026Shared · Reseller · KVM VPS · Dedicated
Document version1.0
Effective date14 November 2026
Document ownerRapidServer Operations
Next scheduled reviewNovember 2027
Applies toAll customers with an active covered Service

99.95% monthly uptime commitment per covered Service · 30-minute first response target for P1 critical incidents, 24 x 7 · up to 100% of the monthly fee as service credit.

This Service Level Agreement sets out the availability RapidServer commits to for its hosting services, how that availability is measured, what is excluded, and the service credits available when the commitment is not met. It also records support response targets, backup and data protection practices, and the rules for planned maintenance, suspension and termination.

1. Purpose and scope

1.1 This Service Level Agreement (the "SLA") is between RapidServer, operated by Rudraksh Mittal ("RapidServer", "we", "us"), and the customer named on the active order or invoice ("Customer", "you").

1.2 This SLA applies to these services (each a "Service"): Shared Hosting (Web and WordPress Hosting), Reseller Hosting, KVM VPS, Managed VPS, Dedicated Servers, and the RapidServer control panel, in each case while bought under an active, paid order.

1.3 This SLA forms part of, and is governed by, our Terms of Service and Acceptable Use Policy (the "AUP"). Where those documents conflict with this SLA on availability, support targets or service credits, this SLA prevails.

1.4 This SLA does not apply to:

  • free trials, beta, preview or promotional services, and any service offered expressly without an SLA;
  • domains and DNS hosted outside the RapidServer network;
  • third-party software and licences supplied through RapidServer, including cPanel, Plesk, LiteSpeed, Softaculous, Windows Server, SSL certificates and third-party backup add-ons, which carry their own vendors' terms;
  • email deliverability to, acceptance by, or filtering decisions of third-party mail providers; and
  • work carried out as a one-off professional service, migration or custom engineering request.

2. Definitions

TermMeaning
Billing MonthA calendar month in which the Service is active. Where a Service starts or ends mid-month, the Billing Month is the part of the month it was active.
DowntimeAny continuous period of 60 seconds or more during which a Service is wholly unavailable, measured under clause 4 and excluding the events in clause 5. Partial degradation, reduced performance and single-feature faults are not Downtime; they are handled as support incidents under clause 8.
Downtime MinutesAll Downtime in a Billing Month for a Service, added together and rounded up to the nearest whole minute.
Monthly Uptime PercentageThe figure calculated for each Service under clause 3.2.
Monthly FeeThe recurring fee for the affected Service for the Billing Month, excluding set-up and installation fees, taxes and government levies, domain fees, third-party licence fees, bandwidth or resource overage charges, and one-off professional services.
Scheduled MaintenanceMaintenance notified in advance under clause 10.2.
Emergency MaintenanceUnplanned maintenance carried out under clause 10.6 to protect the security, integrity or availability of the platform.
Service CreditThe credit calculated under clause 6 and applied to the Customer's account under clause 7.
Business Hours10:00 to 19:00 India Standard Time (IST), Monday to Saturday, excluding public holidays published by RapidServer.
Business DayAny day on which Business Hours occur.

3. Availability commitment

3.1 RapidServer commits to a Monthly Uptime Percentage of 99.95% for each covered Service in each Billing Month.

3.2 The Monthly Uptime Percentage for a Service is calculated as:

Monthly Uptime Percentage = ( ( Total Minutes − Excluded Minutes − Downtime Minutes ) ÷ ( Total Minutes − Excluded Minutes ) ) × 100

where Total Minutes is the number of minutes in the Billing Month and Excluded Minutes is the total of all minutes that fall under clause 5 and clause 10.

3.3 The commitment is measured and applied per Service. If you hold several Services, each is assessed separately.

3.4 At 99.95%, the maximum permitted Downtime is:

PeriodTotal minutesMaximum Downtime
One day1,44043 seconds
One week10,0805 minutes 2 seconds
28-day month40,32020 minutes 10 seconds
30-day month43,20021 minutes 36 seconds
31-day month44,64022 minutes 19 seconds
One year (365 days)525,6004 hours 22 minutes 48 seconds

The commitment is assessed monthly. The daily and weekly figures are for guidance only and are not separately enforceable.

4. Measurement and monitoring

4.1 Availability is measured by our monitoring system using automated checks at intervals of no more than 60 seconds, from at least two independent locations outside the RapidServer network.

4.2 A Service is treated as unavailable when two consecutive checks from two different locations fail. Downtime starts at the time of the first failed check and ends at the time of the next successful check.

4.3 Availability means the Service can be reached at the network and platform layer, tested by ICMP, TCP or HTTP as suits the Service. For KVM VPS and Dedicated Servers it also means the instance or host is powered on and connected to the network, and that the hypervisor, host hardware and our upstream network are working.

4.4 Our monitoring records are the primary record of availability. If you provide conflicting evidence from a reputable independent monitoring service, stating its check interval, locations and timestamps in IST or UTC, we will review it in good faith and correct our own finding where the evidence supports it.

4.5 Incidents, their status and post-incident summaries are published on our status page. We encourage you to subscribe to status notifications.

5. Exclusions from Downtime

The following do not count as Downtime and do not give rise to a Service Credit:

  • Scheduled Maintenance notified under clause 10.2, and Emergency Maintenance within the limits in clause 10.6.
  • Any fault caused by you or your users, including application code, CMS, themes, plugins, cron jobs, database queries, misconfiguration, or changes made by you or anyone using your credentials.
  • Suspension or throttling because you exceeded the CPU, memory, disk, I/O, inode, entry-process or bandwidth limits of your plan.
  • Suspension under clause 12.1, including suspension for non-payment or breach of the AUP.
  • Any failure of software, operating systems or control panels installed, changed or managed by you on an unmanaged VPS or Dedicated Server.
  • Faults in networks, systems or equipment outside the RapidServer network, including upstream transit providers, internet exchange points, your own connectivity, third-party DNS, CDNs, payment gateways, APIs and external mail services.
  • Denial-of-service or other attack traffic beyond the mitigation capacity of your plan, and null-routing used to protect the wider platform, provided we apply mitigation in line with our published practice.
  • Any period in which you have not made a change, patch or migration that we told you in writing was required, after a reasonable time to act.
  • Force majeure, including natural disaster, fire, flood, epidemic, war, terrorism, civil unrest, strikes, failure of public utilities or telecommunications, and any act, order or restriction of a government or regulator.
  • Services listed as out of scope in clause 1.4.
  • Beta, trial and free use of any feature.

6. Service credits

6.1 If the Monthly Uptime Percentage for a Service falls below 99.95% in a Billing Month, you are entitled, on a valid claim under clause 7, to a Service Credit worked out as a percentage of the Monthly Fee for that Service.

6.2 Service Credits are tiered as follows:

Monthly Uptime PercentageDowntime in a 30-day monthCredit (% of Monthly Fee)
Below 99.95%, but 99.50% or moreOver 21 min 36 sec, up to 3 hr 36 min10%
Below 99.50%, but 99.00% or moreOver 3 hr 36 min, up to 7 hr 12 min25%
Below 99.00%, but 95.00% or moreOver 7 hr 12 min, up to 36 hours50%
Below 95.00%More than 36 hours100%

6.3 Service Credits are worked out separately for each affected Service and applied only against the Monthly Fee for that Service. They are not added together across an account.

6.4 The total Service Credit for one Service in one Billing Month cannot exceed 100% of its Monthly Fee.

6.5 For a Service billed annually or for several years, the Monthly Fee is the total prepaid fee for the term divided by the number of months in the term.

6.6 Service Credits are issued as non-transferable credit to your RapidServer account or wallet and are applied against your next invoice. They have no cash value, cannot be refunded or exchanged for cash, and expire when the account is closed.

6.7 No Service Credit is payable for set-up fees, domains, third-party licences, taxes, overage charges or professional services.

6.8 No Service Credit is payable if, at the time of the claim or the incident, your account is in arrears or suspended for breach of the AUP.

7. Claiming a service credit

Service Credits are not applied automatically. You must submit a claim within 30 calendar days after the end of the Billing Month in which the Downtime happened. Later claims are waived.

7.1 Send claims to sales@rapidserver.in, or through a ticket in the client area, with the subject line: SLA Credit Claim - [Service ID] - [Month YYYY].

7.2 A valid claim includes:

  • your account number and the identifier of the affected Service (hostname, IP address or VPS ID);
  • the date, start time, end time and time zone of each period of claimed Downtime;
  • a short description of the impact on you; and
  • supporting evidence, such as third-party monitoring reports, traceroutes, error logs or screenshots with visible timestamps.

7.3 We acknowledge a claim within 3 Business Days and give a written decision within 15 Business Days of receiving a complete claim, stating the Monthly Uptime Percentage calculated, the credit tier applied and the reasons for any rejection.

7.4 Approved Service Credits are applied to your account within one billing cycle of the decision.

7.5 If you disagree with a decision, you can escalate it in writing to our Head of Operations within 15 Business Days of the decision. We will give a final response within a further 10 Business Days.

8. Support response times

8.1 Support is available through these channels and hours:

ChannelAvailabilityUse for
Client area ticket24 x 7 x 365 (intake); staffed per priority belowAll incidents and requests. The record used to measure response times.
Email – support@rapidserver.in24 x 7 x 365 (intake); creates a ticketTechnical incidents and service requests.
Email – sales@rapidserver.inBusiness HoursInvoices, renewals, refunds and SLA credit claims.
WhatsApp – +91 89540 14227Business HoursPre-sales and short technical questions. Not a channel of record for P1.
Emergency phone escalation24 x 7 for P1 only, after a P1 ticket is raisedConfirmed P1 incidents still unacknowledged past target.

8.2 Incidents are classified and targeted as follows. Times run from the moment the ticket is received.

PriorityDefinitionFirst responseWorkaround or fix targetCoverage
P1 CriticalA Service is wholly unavailable, or data loss or a security compromise is in progress. Production is down with no workaround.30 minutes4 hours24 x 7
P2 HighMajor degradation or an important function unusable. Severe performance loss affecting most users. No practical workaround.2 hours8 hours24 x 7
P3 NormalPartial or minor problem affecting some users or a non-critical function. A reasonable workaround exists.8 Business Hours3 Business DaysBusiness Hours
P4 LowA question, help with configuration, a documentation request, a cosmetic issue or a feature request.1 Business DayBest effortBusiness Hours

8.3 "First response" means a real reply from a support engineer who has reviewed the ticket. An automatic acknowledgement or ticket-received email does not count.

8.4 We assign priority reasonably, based on your description of the impact. You may ask for a different priority and we will not refuse unreasonably.

8.5 Resolution times are targets, not guarantees, and are not backed by Service Credits. If a target is missed, we escalate under clause 8.7 and update you at least every 60 minutes for P1 and every 4 hours for P2 until the incident is resolved.

8.6 Response and resolution clocks pause while we are reasonably waiting for information, access or a decision from you, and restart when you respond.

8.7 Escalation path for an incident past its target:

StageOwnerEngaged when
L1Support EngineerWhen the ticket is created.
L2Senior Systems EngineerP1 at 1 hour; P2 at 4 hours; or on request.
L3Support ManagerP1 at 2 hours; P2 at 8 hours; or when you escalate.
L4Head of OperationsP1 at 4 hours, or any incident open longer than twice its target.

8.8 You will give us a named technical contact, reasonable access and the information needed to reproduce and diagnose an issue, and respond to reasonable requests without undue delay.

9. Backup, data protection and security

9.1 Backup coverage. Backups are provided as below. Coverage depends on your plan and any backup add-on you have.

ServiceBackup scheduleRetentionIncluded
Shared and Reseller HostingDaily automated full account backup7 daily copiesIncluded
Managed VPSNightly full-server backup with the backup add-onAs per add-onAdd-on
KVM VPS (unmanaged)Nightly full-server backup with the backup add-onAs per add-onAdd-on
Dedicated ServersManaged by you unless a backup add-on is boughtAs per add-onAdd-on

9.2 Recovery objectives. Where backups are included or an add-on is active:

ObjectiveTargetMeaning
RPO – Recovery Point Objective24 hoursThe most data change that may be lost when restoring from the latest successful backup.
RTO – Recovery Time Objective8 hoursThe target time to finish a restore, from when we accept a valid restore request.
Restore requests1 free per Service per calendar monthFurther restores may be charged, and you are told before work starts.

Backups are a convenience, not a replacement for your own backups. We make reasonable efforts to maintain and check backups, but we do not promise that any backup will be complete, uncorrupted or restorable. You remain responsible for keeping independent, off-platform backups of any data you cannot afford to lose. Our liability for any backup or restore failure is limited as set out in clause 13.

9.3 Data ownership. You own all content, data and databases you store on the Services. We process that data only as needed to provide, secure, bill and support the Services, and on your documented instructions.

9.4 Data location. Your data is stored in our data centre facilities in India: web and WordPress hosting in Mumbai, VPS and bare metal in the Mumbai or Delhi region you choose when ordering. Reseller hosting is the exception: it runs on servers in Germany.

9.5 Security measures. As a minimum, we maintain:

  • encryption in transit using TLS 1.2 or later for the control panel, client area and all administrative access;
  • encryption at rest for backup archives held on storage we manage;
  • network firewalls, intrusion detection and volumetric DDoS mitigation at the network edge;
  • multi-factor authentication available on the client area and control panel, and required for all our staff with administrative access;
  • role-based, least-privilege staff access granted only where needed, reviewed every quarter and logged;
  • security patching of the hypervisors, host operating systems and control panels we manage within 30 days of a vendor release, or within 7 days for vulnerabilities rated critical; and
  • separation of each customer's environment from every other customer's.

9.6 Breach notification. We will tell your registered contact without undue delay, and in any case within 72 hours of confirming a security incident that has, or is reasonably likely to have, affected the confidentiality, integrity or availability of your data. The notice will describe what is known, the types of data affected, the steps taken and what we recommend you do, and will be updated as the investigation continues.

9.7 Data on termination. When a Service ends or expires, your data is kept for 30 calendar days, during which you can ask for an export in a standard format. After that, the data and all backup copies are securely and permanently erased on the normal backup rotation. Data in accounts terminated for breach of the AUP may be erased immediately where needed for legal or security reasons.

10. Scheduled and emergency maintenance

10.1 The standard maintenance window is 00:00 to 06:00 IST. We schedule work that causes interruptions inside this window wherever reasonably possible.

10.2 We give notice of Scheduled Maintenance expected to interrupt a Service:

  • at least 72 hours ahead where the interruption is expected to last 30 minutes or less; and
  • at least 7 calendar days ahead where it is expected to last more than 30 minutes.

10.3 Notice is sent by email to your registered technical contact and posted on the status page. It states the window, the expected duration and the Services affected.

10.4 Scheduled Maintenance inside the notified window and within the notified duration is excluded from Downtime. Any overrun counts as Downtime from the moment it starts.

10.5 Scheduled Maintenance that causes interruptions will not exceed 8 hours in total in any Billing Month. Time beyond that counts as Downtime.

10.6 We may carry out Emergency Maintenance without the notice in clause 10.2 where it is reasonably needed to protect the security, integrity or availability of the platform, for example to apply a critical security patch or respond to a hardware or network failure. We give as much notice as we practically can. Emergency Maintenance is excluded from Downtime up to 4 hours in total in any Billing Month; time beyond that counts as Downtime.

10.7 We publish a post-incident summary on the status page within 5 Business Days of any incident that caused more than 60 minutes of Downtime for several customers.

11. Your responsibilities

The commitments in this SLA depend on you:

  • paying all invoices by the due date and keeping the account in good standing;
  • keeping your contact details, including technical and billing email addresses, accurate and monitored;
  • following the AUP and all applicable law;
  • securing your own credentials, applications, code and third-party components, and updating software you control;
  • staying within your plan's resource limits and upgrading when usage regularly approaches them;
  • keeping independent backups as described in clause 9.2;
  • reporting incidents promptly through a channel of record, with the information needed to diagnose them; and
  • acting within a reasonable time on any change, patch or migration we tell you in writing is required.

12. Suspension and termination

12.1 Suspension by us. We may suspend a Service where an invoice is still unpaid 7 calendar days after written notice of non-payment; you breach the AUP; the Service is compromised, or is being used to attack, spam or otherwise harm others; or suspension is required by law or a competent authority. Unless immediate suspension is needed to prevent harm, we give notice and, where practical, a chance to fix the problem. Suspension under this clause is excluded from Downtime.

12.2 Chronic failure. If, for a single Service, the Monthly Uptime Percentage is below 95.00% in three consecutive Billing Months, or below 99.00% in any four Billing Months within a rolling 12-month period, you may end that Service by written notice within 30 days of the last such month. You will not be charged any early-termination fee and will receive a pro-rata refund of prepaid fees for the unused rest of the term, in addition to any Service Credits already earned.

12.3 Termination for convenience. Either party may end a Service under our Terms of Service. This SLA ends automatically with the last covered Service.

12.4 Effect of termination. Clause 9.7 governs how your data is handled. Service Credits not yet applied to an invoice lapse on termination and are not paid in cash.

13. Limitations and sole remedy

13.1 Service Credits under clause 6, together with the termination right in clause 12.2, are your sole and exclusive remedy for any failure by us to meet the availability commitment or any support target in this SLA.

13.2 We are not liable for indirect, special, incidental or consequential loss, or for loss of profit, revenue, business, goodwill, expected savings or data, arising from any failure to meet this SLA.

13.3 Nothing in this SLA excludes or limits any liability that cannot be excluded or limited by law, including liability for death or personal injury caused by negligence, or for fraud.

13.4 Any overall liability cap in our Terms of Service still applies and is not increased by this SLA.

14. Changes to this SLA

14.1 We may change this SLA by giving your registered contact 30 calendar days' written notice and publishing the new version on our website.

14.2 If a change is materially worse for you, you may end the affected Service without penalty by written notice before the change takes effect, and receive a pro-rata refund of prepaid unused fees.

14.3 Continuing to use a Service after a change takes effect means you accept it.

14.4 Version history:

VersionDateSummary of changeApproved by
1.014 November 2026Initial release.RapidServer Operations

15. Contact and escalation

PurposeContactHours
Technical support and incidentsClient area ticket, or support@rapidserver.inPer clause 8.1
SLA credit claims and billingsales@rapidserver.inBusiness Hours
Formal escalationescalations@rapidserver.in, marked for the Head of OperationsBusiness Hours
Security incidents and disclosuressecurity@rapidserver.in24 x 7 monitored
Service status and incident historyStatus page24 x 7
Phone+91 89540 14227Business Hours; P1 escalation 24 x 7
Registered officeShakumbhari Dham Colony, Behat, Saharanpur, Uttar Pradesh 247121–

Annex A. Quick reference

This annex summarises the commitments above for convenience. If anything here differs from the numbered clauses, the clauses prevail.

CommitmentValueClause
Monthly uptime99.95% per Service, per Billing Month3.1
Permitted downtime21 min 36 sec in a 30-day month3.4
Measurement60-second checks, two or more external locations4.1
Credit tier 110% of Monthly Fee below 99.95%6.2
Credit tier 225% of Monthly Fee below 99.50%6.2
Credit tier 350% of Monthly Fee below 99.00%6.2
Credit tier 4100% of Monthly Fee below 95.00%6.2
Credit cap100% of the Monthly Fee for the affected Service6.4
Claim deadline30 calendar days after the end of the Billing Month7
Claim decisionAcknowledged in 3 Business Days; decided in 157.3
P1 first response30 minutes, 24 x 78.2
P2 first response2 hours, 24 x 78.2
P3 first response8 Business Hours8.2
P4 first response1 Business Day8.2
Backup RPO / RTO24 hours / 8 hours9.2
Breach notificationWithin 72 hours of confirmation9.6
Data kept after termination30 calendar days, then secure erasure9.7
Maintenance window00:00 to 06:00 IST10.1
Maintenance notice72 hours, or 7 days if over 30 minutes10.2
Maintenance cap8 hours scheduled, 4 hours emergency, per month10.5, 10.6
Termination for chronic failureBelow 95% for 3 consecutive months12.2

Acceptance

This SLA is part of our Terms of Service and applies automatically to every covered Service. A signature is needed only where the parties have agreed a negotiated or enterprise version of this document.

RapidServer · Operated by Rudraksh Mittal · GSTIN 09COVPV1278Q1ZH
Shakumbhari Dham Colony, Behat, Saharanpur, Uttar Pradesh 247121
rapidserver.in