Our commitment to service availability, downtime criteria, and service-time remedies.
Effective Date: 25 October 2026RivinCloud targets 99.9% network and power availability for active hosting infrastructure during each calendar month, subject to the definitions, exclusions, conditions, and remedies set out in this SLA.
RivinCloud will use reasonable operational efforts to maintain the hypervisors, physical host nodes, central routing equipment, storage infrastructure, and power systems used to deliver its hosting services.
Virtualized services, including Virtual Private Servers (VPS) and game-server services, may be deployed on bare-metal infrastructure using datacenter-grade server hardware, ECC memory, and enterprise storage configurations.
RivinCloud reserves the right to upgrade, replace, migrate, or reconfigure infrastructure where reasonably necessary for reliability, security, maintenance, capacity management, or other operational requirements.
Depending on the service and hosting location, infrastructure may be deployed in professional data-centre facilities that utilize redundant power and cooling systems, Uninterruptible Power Supplies (UPS), backup generators, physical security controls, multi-carrier network connectivity, and DDoS mitigation capabilities.
The facilities, technologies, and safeguards available may vary depending on the hosting location and infrastructure provider.
For the purposes of determining SLA eligibility and calculating service-time extensions, the following definitions apply.
“Downtime” or “Outage” means a period during which the Customer’s hosted instance is completely inaccessible over the public network or unable to route traffic due to a verified hardware, network, hypervisor, or power failure attributable to RivinCloud.
Downtime is measured from the time the incident is reported through an official support ticket or detected by RivinCloud’s infrastructure monitoring systems until the affected service is restored.
“Verified Downtime” means downtime substantiated by RivinCloud’s internal network logs, hypervisor monitoring, infrastructure monitoring systems, or other reasonably reliable technical records.
“Active Billing Cycle” means the billing period during which the outage occurs and for which the Customer maintains an active, paid hosting service.
All qualifying downtime occurring during the applicable billing cycle will be accumulated, regardless of the number of incidents, their individual duration, or the time at which they occur during that billing cycle.
RivinCloud may conduct routine infrastructure maintenance, software upgrades, security updates, hardware maintenance, network upgrades, and other planned operational activities.
RivinCloud will make reasonable efforts to provide advance notice of scheduled maintenance where practicable.
Downtime resulting from scheduled maintenance is excluded from SLA calculations and is not eligible for a service-time extension.
RivinCloud may perform emergency maintenance without prior notice when urgent intervention is reasonably necessary to protect or restore infrastructure.
Such circumstances may include:
Downtime resulting from emergency maintenance reasonably necessary to protect or restore infrastructure is excluded from service-time extension eligibility.
This SLA does not apply, and no service-time extension will be provided, for interruptions or service unavailability caused by or arising from the following circumstances, to the extent applicable:
To request a service-time extension, the Customer must submit a support ticket through RivinCloud’s official billing portal or Discord ticket system within seven (7) calendar days of the relevant outage.
The request should include:
RivinCloud may rely on its internal monitoring systems, network logs, hypervisor records, and infrastructure logs as the primary sources for determining whether downtime qualifies under this SLA and establishing its duration.
SLA claims will normally be reviewed by the billing or support team within fourteen (14) business days.
Where a qualifying service outage results from an issue attributable to RivinCloud, the affected service’s subscription period will be extended by a duration equivalent to the verified qualifying downtime.
The duration will be calculated using RivinCloud’s available infrastructure, network, hypervisor, and monitoring records.
The approved extension will be added directly to the expiry date of the affected service. The Customer will not be charged for the additional service time.
All qualifying downtime during the applicable billing cycle will be accumulated.
Where multiple qualifying outages occur, the verified duration of each qualifying incident will be combined. The total qualifying downtime will then be added to the affected service’s expiry date as additional service time.
If a Customer experiences multiple qualifying infrastructure outages during a billing cycle, RivinCloud will calculate the verified duration of each eligible outage and combine those durations.
The resulting total will be added to the Customer’s service expiry date, subject to the terms and exclusions of this SLA.
A service-time extension under Section 6 constitutes RivinCloud’s standard remedy for qualifying downtime under this SLA.
No separate monetary refund or account credit will be provided for qualifying downtime unless:
A service-time extension does not reduce or otherwise alter the Customer’s existing service resources, configuration, data, or subscription plan.
RivinCloud will assess qualifying downtime using available technical records, which may include:
Where multiple sources are available, RivinCloud may compare and correlate these records to establish the beginning and restoration times of the qualifying outage.
Customer-provided evidence may also be considered during the review.
This SLA does not provide a separate percentage-based service credit for qualifying downtime.
Instead, qualifying downtime is compensated through an extension of the affected service’s subscription period equivalent to the verified qualifying downtime, as described in Section 6.
Where a core hosting service becomes completely unavailable due to a verified RivinCloud infrastructure failure, the service-time extension described in Section 6 will continue to apply for the duration of the verified qualifying downtime, subject to the exclusions and conditions contained in this SLA.
Any additional refund or alternative remedy remains subject to RivinCloud’s applicable Refund Policy and its requirements.
RivinCloud may migrate or transition Customer services between:
Such changes may be undertaken for reliability, security, capacity planning, hardware lifecycle management, infrastructure upgrades, maintenance, performance improvements, or other operational requirements.
RivinCloud will make reasonable efforts to minimize Customer disruption during such activities.
Where an infrastructure migration causes qualifying downtime attributable to RivinCloud and no exclusion under this SLA applies, the verified qualifying downtime will be added to the Customer’s service period.
RivinCloud provides network-level DDoS mitigation where available.
During significant attacks or security incidents, RivinCloud may implement protective measures, including:
Where such measures are reasonably necessary to protect the Customer, other customers, or RivinCloud’s infrastructure, resulting downtime may be excluded from service-time extension eligibility in accordance with Section 4.
The 99.9% availability commitment represents RivinCloud’s infrastructure availability target, subject to the definitions, exclusions, conditions, and remedies contained in this SLA.
It does not constitute a guarantee of uninterrupted operation for every application, component, or service running within the hosting environment.
RivinCloud does not guarantee uninterrupted operation of:
Customers are responsible for maintaining appropriate backups of their data and applications.
RivinCloud may provide backup services where expressly included in the applicable service plan. However, Customers should maintain independent backups of important data and critical workloads.
Customers remain responsible for the applications, operating systems, configurations, databases, plugins, and other software operating within their hosted environments.
RivinCloud reserves the right to update or amend this SLA from time to time to reflect changes in infrastructure, services, security requirements, operational practices, data-centre arrangements, or business requirements.
Subject to applicable law, the version generally applicable to an incident will be the version in effect for the Customer’s service at the time of that incident.
This SLA establishes RivinCloud’s availability commitment and the applicable process for assessing qualifying downtime and determining service-time extensions.
In the event of an availability incident, RivinCloud will review relevant infrastructure monitoring data, network records, hypervisor logs, and other available technical records to determine whether the incident qualifies under this SLA and the amount of additional service time applicable to the affected service.
For each qualifying outage attributable to RivinCloud, the verified qualifying downtime will be added to the affected service’s subscription period, subject to the terms, conditions, and exclusions contained in this SLA.