// SLA & Support

Enterprise SLA and service commitment.

Imperium Solutions LLC backs covered managed environments with clearly defined service standards, support priorities, and a 99.9% monthly uptime commitment — a transparent operating framework, stronger accountability, and clearer expectations around availability and support response.

Availability Commitment
99.9%monthly uptime

Provider will use commercially reasonable efforts to make each covered production environment available at least 99.9% of the time during each calendar month, excluding excluded downtime. 99.9% monthly availability permits approximately 43 minutes and 50 seconds of downtime in a 30-day month.

Service Credits

If monthly uptime falls below the contracted threshold for a covered environment, service credits may be issued in accordance with the client's managed services agreement. Credits are the client's sole monetary remedy for SLA misses, capped at 50% of the monthly recurring fee for the affected service.

Below 99.9% — at or above 99.0%10%
Below 99.0% — at or above 95.0%25%
Below 95.0%50%
// Response Framework

Priority response targets.

Defined by business impact. Presented as enterprise service standards — to be formally contracted in the managed services agreement.

PriorityLevelInitial ResponseStatus UpdatesPosture
P1Critical Outage15 minutesEvery 30 min until stabilizationContinuous reasonable efforts
P2Major Degradation1 hourEvery 4 business hoursExpedited triage
P3Standard Issue4 business hoursNext update by next business dayStandard queue
P4Service Request1 business dayAs reasonably neededScheduled handling
// Escalation

A defined escalation path.

[01]Service Desk
[02]Infrastructure Lead
[03]Senior Escalation
[04]Executive Oversight

Executive oversight engages for prolonged or high-impact incidents. Quarterly reviews evaluate incidents, trends, recommendations, and roadmap priorities.

// Excluded Downtime

What does not count against uptime.

  • Scheduled maintenance performed during published windows with required notice.
  • Emergency maintenance reasonably necessary to protect service integrity or security.
  • Outages caused by client systems, acts, omissions, unsupported software, or unauthorized changes.
  • Failures of third-party systems, networks, carriers, DNS, cloud services, or APIs outside contracted responsibility.
  • Force majeure events.
// Engagement

Govern your infrastructure with a real service framework.

Define your covered environments, response priorities, and escalation paths in a formal managed services agreement.

Discuss Your Environment