NimbusNexus
Legal · Service Level Agreement

Service Level Agreement

Our 99.99% monthly uptime commitment for production-tier workloads, the Service Credits available if we miss it, and how to claim them.

VERSION
2.0
EFFECTIVE
Pending
LAST CHANGE
Major rewrite
REVIEW CYCLE
Quarterly
NEW · v2.0Major rewrite, published with Terms v2.0. Defines Covered Services (VMs, block storage, network), the 5-minute outage threshold, scheduled vs emergency maintenance, and a 10/25/50% credit tier ladder.
View summary →
Plain-English version

This Service Level Agreement ("SLA") sets out our uptime commitment for the NimbusNexus™ cloud service, the Service Credits available if we miss it, and how to claim them. This SLA is part of the Terms of Service ("Terms") at /terms-of-service. Capitalized terms not defined in this SLA have the meanings given in the Terms. By using the Service, you agree to this SLA, the Terms, and the other policies referenced in the Terms.

01

Uptime commitment

IN PLAIN ENGLISH

We aim to keep the Service running 99.99% of the time each month. If we miss that, you can claim a credit on your next invoice.

For workloads on our production tiers, Fortlab Corporation ("Fortlab", "we", "us") commits to a monthly uptime of 99.99% for the Covered Services: Virtual Machines, block storage, and network services. Other Service tiers — including trial, free, and promotional Services — are not covered by this SLA.

As Fortlab adds new generally-available Service tiers, we will update the Covered Services list above and notify customers in accordance with §7.

02

How we measure uptime

IN PLAIN ENGLISH

We add up the minutes of qualifying downtime in a month and subtract them from the total minutes in the month. If less than 99.99% of the month was up, you can claim a credit.

Uptime for a calendar month is calculated as: Uptime = (Total Minutes in Month − Unscheduled Downtime Minutes) ÷ Total Minutes in Month.

"Unscheduled Downtime" means any period of more than five (5) consecutive minutes during which a Covered Service is not generally available, as measured by Fortlab's monitoring systems, excluding any period attributable to:

Scheduled maintenance, as defined in §3.

Emergency maintenance, as defined in §3.

Force majeure events, as set out in §16 of the Terms (including events outside Fortlab's reasonable control, internet access disruptions, and third-party service disruptions).

Customer's actions or inactions, including misconfiguration, exceeding rate limits, or use of unsupported configurations.

Acts of any third party not under Fortlab's direct control.

Violations of the Terms (including the Acceptable Use Policy), or suspension or termination resulting from such violations or from non-payment.

Beta, preview, trial, free, or promotional Services, which are not Covered Services.

Outages of five (5) consecutive minutes or fewer are not counted as Unscheduled Downtime, regardless of frequency.

03

Maintenance

IN PLAIN ENGLISH

Routine maintenance is announced at least 36 hours ahead. Security or emergency maintenance may be shorter or unannounced — we'll let you know as soon as we reasonably can.

Scheduled maintenance. Fortlab may perform scheduled maintenance from time to time. We will announce scheduled maintenance windows at least thirty-six (36) hours in advance by email and via the status page. Scheduled maintenance is not Unscheduled Downtime.

Emergency maintenance. Where maintenance is required for security or critical operational reasons (including responding to vulnerabilities, urgent capacity changes, or incident remediation), we may perform it with shorter notice or without prior notice. We will communicate emergency maintenance as soon as practicable, including the reason and the affected Services. Emergency maintenance is not Unscheduled Downtime.

We will use commercially reasonable efforts to schedule maintenance during off-peak hours and to minimize disruption.

04

Service Credits

IN PLAIN ENGLISH

If we miss the SLA, here's what you can claim. Bigger misses get bigger credits.

If Fortlab fails to meet the 99.99% uptime commitment for a Covered Service in a calendar month, you may claim a Service Credit calculated as a percentage of the Affected Monthly Fee (defined below):

Less than 99.99% but at least 99.0% — 10% of the Affected Monthly Fee.

Less than 99.0% but at least 95.0% — 25% of the Affected Monthly Fee.

Less than 95.0% — 50% of the Affected Monthly Fee.

"Affected Monthly Fee" means the fees attributable to the affected Covered Services for the month in which the SLA failure occurred, calculated based on the per-second metering described in §5 of the Terms. It does not include fees for unaffected Services, support plans, or one-time charges.

05

Claiming Service Credits

IN PLAIN ENGLISH

Email us within 30 days with the details. We'll review and apply credits to your next invoice.

To claim a Service Credit, submit a written request to [email protected] within thirty (30) days after the end of the month in which the SLA failure occurred. Your request must include:

• The affected Service and Customer account.

• The date(s) and approximate duration of the downtime.

• The impact on your workload, including any logs, screenshots, or status-page references that support the claim.

Fortlab will acknowledge the request within five (5) business days and review it in good faith. Approved Service Credits will be applied to your next invoice. If your account is on a prepaid plan and there is no future invoice to credit against, the Service Credit will be applied to a renewal or refunded if no renewal occurs.

Service Credits are your sole and exclusive remedy for any failure of Fortlab to meet the SLA.

06

Limits on Service Credits

IN PLAIN ENGLISH

Credits cap at the affected month's fees, can't be transferred between accounts, and can't be combined to exceed 100%.

• The total Service Credits issued in any month for a Covered Service cannot exceed 100% of the Affected Monthly Fee for that Service.

• Where multiple Covered Services miss the SLA in the same month, Service Credits are calculated separately per Service and aggregated, subject to the cap above.

• Service Credits are non-transferable and may not be applied to a different account, a different Customer, or unrelated Services.

• Service Credits cannot be exchanged for cash, except as set out in §5 (where there is no future invoice to credit against).

• This SLA does not apply to beta, preview, trial, free, or promotional Services.

07

Modifications

IN PLAIN ENGLISH

We may update this SLA. For changes that materially reduce your benefits, we'll give 30 days' email notice.

Fortlab may modify this SLA from time to time. The current version will always be posted at /service-level-agreement with a revision date. Material changes that reduce the Service Credits available, narrow the Covered Services, or otherwise reduce a Customer's benefits under this SLA will be announced by email at least thirty (30) days before they take effect, in accordance with §18 of the Terms. Continued use of the Service after the effective date constitutes acceptance.

08

Contact

IN PLAIN ENGLISH

For SLA claims, email [email protected]. For technical support during an outage, contact support per your support plan. Live status: status.nimbusnexus.net.

For SLA claims, email [email protected]. For technical support during an outage, contact support per your support plan. The current Service status is available at status.nimbusnexus.net.

SIGN-OFF
Fortlab Corporation · Sheridan, WY, United States
Issued by Fortlab Corporation, Office of the General Counsel · effective date pending publication
Download signed PDF →
Version history

Every change, on the record.

v2.0PendingMajor rewrite. Published alongside Terms v2.0.view →