This Service Level Agreement (SLA) defines the service commitments and support levels for Atmos Pro.
Cloud Posse commits to maintaining 99.9% uptime for Atmos Pro services during each calendar month.
Availability is calculated as:
Availability = (Total Minutes - Downtime Minutes) / Total Minutes × 100
The following are excluded from uptime calculations:
Scheduled maintenance windows 
Force majeure events 
Issues caused by third-party services 
User-initiated actions or misconfigurations 
 
Initial Response : Within 2 business daysResolution : Best effort based on issue complexityCommunication : Email and documentation 
Initial Response : Within 4 business hoursResolution : Based on SLA commitments in your planCommunication : Email, documentation, and designated channels 
Initial Response : Within 1 business hour (for critical issues)Resolution : Immediate attention for service-impacting issuesCommunication : Phone and email escalation 
Monday–Friday, 9:00 AM – 5:00 PM PT 
Excludes U.S. public holidays 
 
Cloud Posse does not provide support on the following U.S. holidays:
New Year's Day (January 1) 
Martin Luther King Jr. Day (3rd Monday in January) 
Washington's Birthday (3rd Monday in February) 
Memorial Day (Last Monday in May) 
Independence Day (July 4) 
Labor Day (1st Monday in September) 
Veterans Day (November 11) 
Thanksgiving Day (4th Thursday in November) 
Day After Thanksgiving (4th Friday in November) 
Christmas Day (December 25) 
 
Service credits may be available if we fail to meet our uptime commitment:
99.0% - 99.9%: 10% credit 
95.0% - 99.0%: 25% credit 
Below 95.0%: 50% credit 
 
To request a service credit:
Submit a request within 30 days of the incident 
Include details of the downtime period 
We will review and respond within 10 business days 
 
We continuously monitor Atmos Pro services for:
System availability and performance 
Error rates and response times 
Security incidents and threats 
 
5.2 Status Page Service status is available at our status page with real-time updates on:
Current service status 
Incident reports and updates 
Scheduled maintenance notifications 
 
Incidents are classified by severity:
Critical : Service completely unavailableHigh : Major functionality impairedMedium : Minor functionality affectedLow : Cosmetic issues or minor bugs 
During incidents, we provide:
Initial acknowledgment within response time 
Regular updates on progress 
Resolution notification 
Post-incident report (for critical/high severity) 
 
7. Maintenance Windows 7.1 Scheduled Maintenance 
Frequency : Monthly or as neededDuration : Typically 2-4 hoursNotification : 7 days advance noticeTiming : Scheduled during low-usage periods 
7.2 Emergency Maintenance 
Notification : As much advance notice as possibleDuration : Minimized to essential fixes onlyCommunication : Immediate status updates 
For SLA-related inquiries:
Cloud Posse reserves the right to update this SLA periodically. Any material changes will be communicated to subscribers via email or website announcement.
Last updated: December 2024