Infrastructure Performance Standard · Version 2026.1

Service Level Agreement (SLA Framework)

Effective Date: November 16, 2026 · Last Updated: November 16, 2026. Performance objectives, uptime standards, and service credit guidelines for Arizen Cloud (Parent: Arizen Tech).

Operational Targets vs. Contractual Guarantees

Arizen Cloud operates enterprise hardware clusters designed for high reliability. This Service Level Agreement outlines our operational availability targets, measurement methods, and compensation credit remedies. While we engineer systems to maintain high uptime, no distributed cloud infrastructure can technically guarantee 100.0% uninterrupted service over public internet transit.

99.9% Monthly Target

Our target availability objective across dedicated host nodes (VPS1, VPS2, VPS3) and Pterodactyl cluster daemons.

< 1-Hour Outage SLA

Critical priority support response target for host node outages or major cluster infrastructure incidents.

24h Maintenance Notice

Advance notification via dashboard banner and Discord announcements for scheduled kernel upgrades or node optimizations.

1. Uptime Measurement Methodology

Service availability is measured continuously using independent external health monitoring probes that execute automated TCP and HTTP synthetic tests every 60 seconds against node daemons and panel APIs.

Monthly Uptime Percentage Formula:

Monthly Uptime % = ((Total Minutes in Month - Downtime Minutes) / Total Minutes in Month) * 100

A compute node is deemed “Down” when external probes record 100% packet loss or connection refusals for more than five (5) consecutive minutes. Real-time telemetry is published at azcloud.site/status.

2. Scheduled & Emergency Maintenance

  • Scheduled Maintenance: Routine operating system patching, hypervisor kernel updates, and network switch maintenance are scheduled during low-traffic windows (typically 02:00 to 05:00 UTC). We provide at least twenty-four (24) hours advance notice via our public status page and Discord community. Scheduled maintenance is excluded from downtime calculations.
  • Emergency Maintenance: Critical zero-day vulnerability mitigations, upstream fiber cuts, or immediate hardware replacement following component failure may be executed immediately without prior notice. Real-time status updates are posted continuously during emergency windows.

3. Service Credit Framework

If our physical node infrastructure fails to maintain our 99.9% availability target in a given calendar month (excluding permitted SLA exclusions), active customers are eligible to receive service credit applied toward their next renewal invoice:

Monthly Infrastructure UptimeEligible Service Credit Percentage
99.0% to 99.89%10% credit of monthly base plan fee
95.0% to 98.99%25% credit of monthly base plan fee
< 95.0%50% credit of monthly base plan fee

Claiming Service Credits: To request a credit, submit a ticket to [email protected] within fourteen (14) days following the affected calendar month. Credits are non-transferable, have no cash value, and apply strictly to future Arizen Cloud renewal invoices.

4. SLA Exclusions

The following events are explicitly excluded from downtime calculations and service credit claims:

  • Customer Software Faults: Unhandled exceptions, memory exhaustion, fatal crashes, syntax bugs, or bot restarts caused by customer-uploaded code or configuration files.
  • Third-Party Upstream Outages: Outages originating from external platforms outside our control, including Discord Inc. API Gateway outages, Cloudflare transit congestion, or upstream data center power grid failures beyond redundant backup generators.
  • Scheduled Maintenance Windows: Pre-announced maintenance windows that do not exceed their scheduled duration.
  • AUP Suspensions: Service suspensions resulting from Acceptable Use Policy violations or non-payment of invoices.
  • Force Majeure: War, natural disasters, national fiber severances, acts of government, or extraordinary events beyond reasonable human control.

5. Customer Support Response Targets

Our engineering support team triages tickets based on incident severity:

Severity LevelIncident DefinitionInitial Response Target
CriticalHost node crash, entire cluster unreachable< 1 Hour (24/7)
HighAutomated provisioning failure, invoice payment issue< 4 Hours
NormalGeneral technical assistance, SFTP questions, plan changes< 24 Hours

Incident Reporting & SLA Desk

Status Dashboard: azcloud.site/status

Support Desk: [email protected]

Emergency Operations: [email protected]