● Service Level Agreement

99.9% Uptime Commitment.
Every Server. No Exceptions.

Rubicon guarantees 99.9% monthly uptime on every provisioned server — with a service credit program when we fall short. No multi-zone requirement. No extra configuration. Every server, out of the box.

What the Competitor Numbers Actually Mean

AWS and Google Cloud advertise 99.99% uptime — but only for workloads deployed across multiple availability zones. For a standard single-server deployment, the real SLA figures tell a very different story.

SLA Metric AWS Azure Google Cloud Rubicon
Advertised Headline SLA 99.99% 99.9%–99.95% 99.99% 99.9%
Applies To Multi-AZ deployments only Single VM (Premium SSD) Multi-zone deployments only Every server, single site
Single-Server SLA 99.5% 99.9% (matches Rubicon) 99.5% 99.9% ✔
Allowable Downtime / Year (single server) ~3.65 days ~8.7 hours ~3.65 days ~8.7 hours
Rubicon's 99.9% single-server SLA beats AWS and Google Cloud on a direct apples-to-apples comparison — and matches Azure — without requiring redundant multi-zone deployments or additional configuration.

AWS single-instance SLA of 99.5% and Google Cloud single-instance SLA of 99.5% based on published SLA documentation. Customers should independently verify current SLA terms with each provider.

What 99.9% Means in Practice

SLA LevelMax Downtime / MonthMax Downtime / Year
99.9% — Rubicon ~43 minutes ~8.7 hours
99.0% ~7.2 hours ~3.65 days
95.0% ~36 hours ~18.25 days

Uptime Measurement

Uptime is measured from Rubicon's network edge to the server's network interface and is monitored continuously. A server is considered unavailable when it fails to respond to network connectivity checks for two or more consecutive minutes.

Scheduled maintenance windows, with a minimum of 48 hours advance notice to the customer, are excluded from uptime calculations. Rubicon will provide advance notice via email to the primary account contact.

Service Credit Schedule

If Rubicon fails to meet the 99.9% monthly uptime commitment for any individual server, the customer is entitled to a service credit applied to the following month's invoice.

Monthly Uptime Achieved Downtime in the Month Service Credit
99.0% to < 99.9% ~43 minutes to ~7.2 hours 10% of affected server fees
95.0% to < 99.0% ~7.2 hours to ~36 hours 25% of affected server fees
< 95.0% More than ~36 hours 50% of affected server fees
Credit Terms: Credits are applied to the customer's next monthly invoice for the affected servers only. Total credits in any billing period shall not exceed one full month's fees for the affected servers. Customers must submit a credit request within 30 days of the incident. Credits are the sole financial remedy for SLA breaches and do not apply to outages caused by planned maintenance (with 48-hour advance notice), customer actions, or force majeure events. Customers are advised to consult their own legal counsel when incorporating this SLA into downstream agreements with their end customers.

How to Request a Credit

Email sales@rubicon-technologies.com with subject line "SLA Credit Request" within 30 days of the incident. Include the server name, date and time of the outage, and a brief description. We will respond within 5 business days.

What Is Excluded

  • Planned maintenance (48-hr advance notice given)
  • Outages caused by customer action or misconfiguration
  • Force majeure events
  • Third-party service failures outside Rubicon's control

Data Transfer Fair Use Policy

Rubicon's flat monthly pricing includes unlimited data transfer with no additional charges for ingress or egress. This offering is governed by a Fair Use Policy to ensure consistent network performance for all customers.

The Fair Use Policy is a network quality assurance measure — not a billing mechanism. The vast majority of SMB SaaS workloads operate well within these thresholds. No customer has ever been charged for data transfer.
Server Class Expected Normal Usage Fair Use Threshold Above Threshold
Class 1 Up to 1 TB/month 2 TB/month Rubicon may contact customer to discuss workload optimisation or dedicated bandwidth options
Class 2 Up to 2 TB/month 5 TB/month Same as above
Class 3 Up to 5 TB/month 10 TB/month Same as above
Class 4 Up to 10 TB/month 20 TB/month Same as above
Class 5 (Bare Metal) Discuss with sales Defined at contract Discussed individually
Customers whose aggregate data transfer persistently and materially exceeds the fair use threshold may be contacted by Rubicon to discuss workload optimisation, infrastructure adjustments, or dedicated bandwidth allocation. Rubicon reserves the right to implement traffic shaping on servers that are materially and persistently degrading shared network performance for other customers. Customers with known high-throughput requirements are encouraged to discuss their needs with our solutions team prior to deployment.

Questions About Our SLA?

Our team is happy to walk through the SLA details and help you understand how to incorporate them into your own customer agreements.

Talk to Our Team →