# Understanding Outage Severity Levels

Here are some of the descriptions for the different states.

* **Operational**&#x20;
  * The service is operating normally without a known problem affecting users.&#x20;
* **Minor Outage**
  * The service may experience intermittent downtime, but a workaround is available.
  * Customers may encounter minor inconveniences due to intermittent service interruptions.
  * A workaround is readily accessible to minimize the impact.
  * Some performance degradation may be noticeable, but overall usability remains feasible.
* **Major Outage**
  * Extensive service disruption with a critical impact on customer data.
  * A significant portion of customers are unable to access the customer-facing service.
  * Core functionality experiences severe disruptions, significantly impacting regular operations.

{% hint style="info" %}
99% of the time, the qualification of the outage state is up to the service provider and IsDown limits to map it to its internal models.&#x20;
{% endhint %}

If you have any questions, you can always send also an email to <support@isdown.app>.

***

**Related Articles**

* [**How to Get Filter Notifications by Outage Severity**](https://help.isdown.app/cloud-monitoring/how-to-get-filter-notifications-by-outage-severity)
* [**How to Filter Outages Affecting Some Specific Components**](https://help.isdown.app/cloud-monitoring/how-to-filter-outages-affecting-some-specific-component-s)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.isdown.app/cloud-monitoring/understanding-outage-severity-levels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
