VoIP Service Reliability: Read SLAs and Define an Outage Plan
Yenra | Prepared October 3, 2026
Guide: https://yenra.com/voip-service/

SLA REVIEW AND OUTAGE PLAN
Use your actual order, amendments and applicable agreement. This worksheet is
an operational reading aid. Fictional arithmetic below is not a provider offer.

Contract entity / product / region / tier / effective date:
Agreement URL and saved version:
Covered function:
Measurement period / denominator / time zone:
What qualifies as downtime? source of evidence? overlap/aggregation rule?
Exclusions and maintenance provisions:
Credit basis / cap / deadline / required claim records:
Support channel / severity definition / response target / escalation:

TIME-BASED EXAMPLE ONLY
Availability percent = 100 * (eligible minutes - counted outage) / eligible minutes
Assume 30 whole days: 30 * 24 * 60 = 43,200 eligible minutes.
99.9% target: allowed counted downtime = 43,200 * 0.001 = 43.2 minutes.
30 counted minutes: 99.930555...%, displayed as 99.9306%.
60 counted minutes: 99.861111...%, displayed as 99.8611%.
Use unrounded values for threshold decisions. Different contracts can measure
requests or events instead of time. Credit still requires the remedy terms.

OUTAGE RUNBOOK
Business calling outcome to preserve:
Alternate contact/route and activation authority:
Shared dependencies with primary route (power, access, platform, number control):
Supported diversion prerequisites / planned rehearsal / result:
Support contact if portal unavailable:
First failure / last failure / restored time, all with time zone:
Affected users, call directions and representative private call references:
Provider status incident and support case:
Full user interruption vs contract-counted interruption:
Next update owner/time / restoration checks / return-to-normal approval:
Renewal or product-change review date:

Supporting sources (see guide for context):
https://www.twilio.com/en-us/legal/service-level-agreement
https://status.twilio.com/