> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://myoperator.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How does MyOperator calculate uptime — cumulative or per component?

Short answer: Per component. Each item on the Status Page (for example, Incoming Calls — Delhi or Outgoing Calls — Mumbai) has its own uptime percentage. We do not publish a single cumulative uptime across all components.

---

## On this page

* Key definitions
* The uptime formula
* Step-by-step: how we calculate it
* Examples with real numbers
* Edge cases & notes
* How to verify uptime on the Status Page
* Troubleshooting & escalation
* Related articles
* Schema markup

---

## Key definitions

* Component: A distinct service/region shown on the Status Page (e.g., Incoming Calls — Delhi).
* Incident: A tracked event affecting a component’s availability.
* Downtime minutes: The total minutes a component is in an outage state during the measurement window.
* Measurement window: Usually a calendar month (00:00–23:59, local time specified on the Status Page).

|| Info We report availability per component to give a precise view of which regions/services were impacted.

---

## The uptime formula

Copy/paste for your notes:

```
uptime_% = ((total_monitored_minutes - downtime_minutes_for_component) / total_monitored_minutes) * 100
```

* total_monitored_minutes in a 30-day month = 30 × 24 × 60 = 43,200 minutes.
* total_monitored_minutes in a 31-day month = 31 × 24 × 60 = 44,640 minutes.

---

## Step-by-step: how we calculate it

1. Pick the component (e.g., Incoming Calls — Delhi).
2. Sum downtime minutes for that component across all incidents in the month.
3. Exclude/Include maintenance as defined in our Maintenance Policy (see your plan/policy).
4. Apply the formula to get the monthly uptime %.
5. Publish per-component uptime on the Status Page.

---

## Examples with real numbers

**Example A — Single component outage (30-day month)**

* Component: Incoming Calls — Delhi
* Downtime: 60 minutes
* Uptime = (43,200 − 60) / 43,200 × 100
* = 43,140 / 43,200 × 100 ≈ 99.86%

**Example B — Another component unaffected**

* Component: Outgoing Calls — Mumbai
* Downtime: 0 minutes
* Uptime = (43,200 − 0) / 43,200 × 100 = 100.00%

**Why not cumulative?**
Averaging these two components would show ~99.93%, which hides that Delhi had a distinct issue. Reporting per component keeps the impact clear and localized.

---

## Edge cases & notes

* Overlapping incidents: We count unique downtime minutes for the component (no double-counting).
* Partial degradation: Only minutes classified as outage reduce uptime; informational/degraded states may be reported separately.
* Multi-region events: Each affected region’s component is calculated independently.
* Maintenance windows: Whether scheduled maintenance counts toward downtime depends on your Maintenance Policy/plan.
* Time zone: Uptime windows follow the Status Page’s stated time zone.

---

## How to verify uptime on the Status Page

1. Open Status Page → Components.
2. Select the component (e.g., Incoming Calls — Delhi).
3. Review Incidents within the month and note durations.
4. Confirm the monthly uptime % shown for that component.

---

## Troubleshooting & escalation

* The math doesn’t match what I see.
* Check the time zone, month length, and whether an incident was partial vs outage.
* Confirm if scheduled maintenance is excluded per your plan.
* Need a breakdown (minute-level or CSV)?
* Contact Support with the component name, month, and incident links/IDs.
* Include your account ID and email for the report.

Support: [support@myoperator.com](mailto:support@myoperator.com) • 92129-92129