Effective date: 5 September 2025
This SLA applies to Managed Services described in an active SOW (e.g., hosting support, DevOps, observability, security monitoring). If there is a conflict, the SOW controls.
Production environments and critical integrations listed in the SOW. Non-production is best-effort unless otherwise stated.
Priority | Response | Update Cadence | Workaround Target | Resolution Target* |
---|---|---|---|---|
P1 | 15 min | 60 min | 4 hrs | Best effort within 8 hrs |
P2 | 2 hrs | 8 hrs | 1 business day | 3 business days |
P3 | 1 business day | Every 3 business days | N/A | As prioritized |
P4 | 2 business days | Weekly | N/A | As scheduled |
*Resolution targets are objectives, not guarantees; complex third-party issues may extend timelines. We’ll provide root-cause and corrective actions for P1/P2 within 5 business days of closure.
Monthly uptime target: 99.9% for monitored production components we operate. Exclusions: scheduled maintenance (with ≥48h notice), emergency maintenance to address security risk, issues caused by Client or third parties outside our control (e.g., cloud provider regional outages, upstream gateways), force majeure.
Monthly Uptime | Credit |
---|---|
< 99.9% to ≥ 99.5% | 5% of monthly managed fee |
< 99.5% to ≥ 99.0% | 10% of monthly managed fee |
< 99.0% | 15% of monthly managed fee |
Credits must be requested within 30 days of the month-end and are applied to future invoices. Credits are not available where exclusions apply.
We monitor critical paths with alerting. On a suspected breach affecting Client data, we will notify without undue delay, investigate, mitigate, and provide updates and a post-incident report consistent with the DPA.
Monthly service report: incidents & SLAs, changes, capacity/cost notes, recommendations, and risk register updates.
Service levels may be updated by mutual written agreement or change order.