Availability Policy

Scope

This Availability Policy describes VPSRoom’s operational approach to the availability of Services. It is informational and policy-based. It does not establish a contractual numerical uptime guarantee, a service-credit entitlement, a compensation formula or a promise of uninterrupted operation. The Terms of Service govern the customer relationship.

Availability objectives

VPSRoom designs and operates infrastructure with availability and recoverability in mind. Actual availability can vary by Service, configuration, location, workload and events within or outside VPSRoom’s reasonable control. Customers should select resources and resilience measures appropriate to their needs.

Planned maintenance

Planned maintenance may be required for security, reliability, capacity or platform changes and may affect a Service. Where reasonably practicable, maintenance information may be communicated through available account or support channels. Maintenance timing and impact can change as operational conditions require.

Emergency maintenance

We may perform emergency maintenance with limited or no advance notice when reasonably necessary to address a security risk, active incident, data-integrity concern or material threat to platform stability.

Customer systems and configuration

Outages or degradation caused by Customer Data, customer software, operating-system configuration, credentials, firewall rules, exhausted resources, customer-requested work or failure to maintain an application are not infrastructure availability commitments. Customers are responsible for monitoring applications, maintaining backups and testing recovery.

Third-party and upstream dependencies

Internet routes, upstream networks, power, facilities, software and other third-party systems can affect reachability or operation. VPSRoom works to manage dependencies it controls but does not guarantee the conduct or uninterrupted availability of external systems.

Network incidents

A reachability issue may arise within a Service, a VPSRoom-controlled segment, an upstream path, a destination network or a customer’s access network. Investigation may require timestamps, source and destination details, region information and sanitized diagnostics. A single path failure does not necessarily establish platform-wide unavailability.

DDoS and security mitigation

DDoS mitigation and other security controls are layered safeguards. Attack characteristics, upstream conditions and the affected Service may require filtering, rate limiting, rerouting, isolation or temporary restriction. VPSRoom does not guarantee that every attack will be mitigated without degradation or interruption.

Events outside reasonable control

Availability may be affected by natural disasters, widespread utility or network failures, war, civil disorder, governmental action, labor disruption, third-party failure or other events outside reasonable control. Treatment of those events remains subject to the Terms and mandatory applicable law.

Incident reporting and cooperation

Report a suspected Service interruption through the authenticated customer support flow. Include the affected Service and region, timestamps with time zone, symptoms, recent relevant changes and sanitized diagnostics. Do not include passwords or private keys. Customers must cooperate with reasonable troubleshooting and preserve relevant evidence.

Support escalation

Account-specific incidents should remain in the authenticated support channel so ownership and Service details can be verified. Urgent abuse or security reports may be sent to abuse@vpsroom.com. Escalation supports investigation but does not create a numerical availability promise or compensation entitlement.

Contact

VPSRoom Hosting LLC, 8401 Mayland Dr, Ste S, Richmond, Henrico County, VA 23294, USA.

Customer availability questions should use the authenticated customer support flow. Abuse and security reports: abuse@vpsroom.com.