---
title: Provider Status Monitoring
description: Monitor the public status of the third-party providers your applications depend on from inside Coralogix, and compare provider incidents against your own telemetry.
url: https://coralogix.com/docs/integrations/provider-status-monitoring/
product: integrations
feature: Provider Status Monitoring
feature_id: provider-status-monitoring
feature_identifier: integrations/provider-status-monitoring
last_updated: '2026-11-03'
---

# Provider Status Monitoring

Note

This feature is available for early-access customers. To request access and confirm your organization meets the feature criteria, contact your account representative or Support.

The Provider Status Monitoring page gives you a single view of the third-party services your applications depend on, such as cloud platforms, SaaS applications, developer tools, and other external providers. Rather than checking each dependency separately, you can track them all in one place.

To open the **Provider Status Monitoring** page, select **Integrations**, then **Provider Status Monitoring** in the navigation sidebar. The page lists providers sorted by their [status](#status-and-severity). For each provider, you can see how many components are monitored, its uptime over the selected [time range](#uptime-history), and when its status was last checked. Use it to quickly determine whether a problem in your environment coincides with a known outage at one of your dependencies.

[![Provider Status Monitoring page](/docs/assets/images/provider-status-monitoring-2-5eac2e63344e1e3b561e04d8ad7c14c6.webp)](https://coralogix.com/docs/assets/images/provider-status-monitoring-2-5eac2e63344e1e3b561e04d8ad7c14c6.webp)

## What you need

Before you start monitoring providers, make sure you have:

* These [permissions](https://coralogix.com/docs/user-guides/aaa/access-control/permissions/permissions-list.md):

  <!-- -->

  * `INTEGRATIONS:READCONFIG` to view the Provider Status Monitoring page.
  * `INTEGRATIONS:DEPLOY` to add, edit, or delete a provider, and to [connect services](#connect-services-to-a-provider) to it.
  * `ALERTS:READCONFIG` to view the **Alerts** tab and a provider's **Alerts** section.
  * `ALERTS:UPDATECONFIG` to create, edit, enable, disable, or delete an alert, and to use the **Alerts** step when adding a provider.

* An archive configured on your storage service, to view a provider's recent incidents and maintenance periods. Learn more about configuring your [Amazon S3](https://coralogix.com/docs/user-guides/data-flow/s3-archive/connect-s3-archive.md) or connecting a [Google Cloud Storage](https://coralogix.com/docs/user-guides/data-flow/gcs-archive.md) archive bucket.

## Provider overview

Each provider card shows its [category and tier](#category-and-tier), its [uptime history](#uptime-history), and the number of [alerts](#alerts) watching it.

### Status and severity

A provider or component might report any of the following statuses, sorted by increasing severity:

* **Operational**: Service is operating normally.
* **Degraded**: One or more monitored components report degraded performance.
* **Partial outage**: Service is partially unavailable.
* **Major outage**: Provider reports a significant outage.

A provider's status reflects the most severe status of any of its components. Similarly, a component group's status reflects the most severe status of any component it contains, and a component's status reflects the most severe status of any of its regions.

A provider or component can also report:

* **Maintenance**: Provider is in a scheduled maintenance window.
* **No data**: Coralogix does not have status information for the component yet.

### Category and tier

Coralogix assigns each provider a category and a tier.

The category describes what kind of service the provider offers, such as DevOps, Security, or Cloud Infrastructure. You cannot change a provider's category, but you can use categories to filter the provider list or search for providers in a specific category.

The tier determines how often Coralogix checks the provider's status page: Tier 1 providers are checked every minute, and Tier 2 providers every five minutes. While a provider has an active incident, Coralogix checks its status every 30 seconds regardless of tier, and returns to the regular tier frequency after three consecutive checks find no active incident.

### Uptime history

Each provider's **Uptime history** bar covers the selected time range. Select **24h**, **3d**, **7d**, or **30d** to apply that time range to the provider list and any [single provider you view](#view-a-single-provider). The bar is segmented into blocks, each color-coded to reflect the provider's status during that period.

Block length depends on the selected time range:

| Time range | Block length |
| ---------- | ------------ |
| 24 hours   | 15 minutes   |
| 3 days     | 1 hour       |
| 7 days     | 1 hour       |
| 30 days    | 12 hours     |

## Manage providers

You can add providers, edit existing ones, and delete providers you no longer want to monitor.

### Add a provider

To add a provider:

1. In the top right corner of the page, select **Add provider**, then select the provider you want to monitor.

   [![Add provider panel on the Select provider step, showing the searchable catalog grouped by category](/docs/assets/images/provider-status-1-select-provider-b-70aaea2c5e4078665be2368e5676053a.webp)](https://coralogix.com/docs/assets/images/provider-status-1-select-provider-b-70aaea2c5e4078665be2368e5676053a.webp)

2. In the **Select services** step, select what to monitor, then select **Next**:

   * **Region scope**: Providers that report per region have a region scope that every selected component inherits. To modify the scope, select **Edit regions**.
   * **Components**: Select the components you want to monitor. Providers that organize their components into groups show them as an expandable tree.

   [![Select services with the discovered components](/docs/assets/images/provider-status-2-select-services-b-ef54a1cb030990bfba4b1f46d7fd1884.webp)](https://coralogix.com/docs/assets/images/provider-status-2-select-services-b-ef54a1cb030990bfba4b1f46d7fd1884.webp)

3. In the **Alerts (optional)** step, set up [alerts](#alerts) for the new provider. You can do one or both of the following:

   * **Add to existing multi-provider alerts**: Add this provider to any existing [cross-provider alert](#create-a-cross-provider-alert).
   * **Create an alert for this provider**: Create a [single-provider alert](#create-a-single-provider-alert) for this provider.

   Note

   Alerts are automatically updated to match what you monitor. When you:

   * Stop monitoring a provider's components or regions, the alerts covering them are updated to match.
   * Delete a provider, its [single-provider alerts](#create-a-single-provider-alert) are deleted, and [cross-provider alerts](#create-a-cross-provider-alert) that include it are updated to match.

4. In the **Connected services (optional)** step, select the [services that depend on the provider](#connect-services-to-a-provider) and what they depend on.

5. Select **Add provider**.

   The provider appears on the Provider Status Monitoring page.

   [![Provider Status Monitoring page showing the newly added provider](/docs/assets/images/provider-status-3-provider-added-b-5eac2e63344e1e3b561e04d8ad7c14c6.webp)](https://coralogix.com/docs/assets/images/provider-status-3-provider-added-b-5eac2e63344e1e3b561e04d8ad7c14c6.webp)

### Edit or delete a provider

Editing a provider lets you change its region scope and monitored components. To edit or delete a provider, select the more actions menu on the provider's card, then select **Edit** or **Delete**. Deleting a provider also deletes the [alerts](#alerts) scoped to it.

When services are [connected](#connect-services-to-a-provider) to the provider, Coralogix warns you before the change takes effect:

* When you delete the provider, its connections are kept but become inactive.
* When you stop monitoring components or regions that connected services depend on, the connections are kept but no longer cover what you removed.

[![Provider card with the more actions menu open, showing the Edit and Delete options](/docs/assets/images/provider-status-edit-delete-button-9f050388d8c0ac9a90d0a08c85da6b23.webp)](https://coralogix.com/docs/assets/images/provider-status-edit-delete-button-9f050388d8c0ac9a90d0a08c85da6b23.webp)

## View a single provider

Select any provider to view its summary, the components being monitored, and a list of recent incidents and maintenance periods.

[![Provider panel for GitHub with 24-hour uptime, monitored component count, uptime history, the alerts watching it, and the components table](/docs/assets/images/provider-status-github-2eb22d4addeff60c46d18b4774b17088.webp)](https://coralogix.com/docs/assets/images/provider-status-github-2eb22d4addeff60c46d18b4774b17088.webp)

The summary shows the following information:

* **Uptime**: Provider's uptime over the selected [time range](#uptime-history).
* **Monitored components**: Number of components being monitored.
* **Reachability**: Whether Coralogix can reach the provider's status page for updates. It does not reflect the provider's health. While a provider is unreachable, its components report **No data**.
* **Last checked**: When the provider's status was last checked.

The **Uptime history** bar reflects the selected time range, segmented into color-coded blocks.

The **Components** section shows the status and uptime of each monitored component, followed by the **[Alerts](#alerts)** section that lists all alerts applied to the provider.

When your storage service has [an archive configured](#what-you-need), the **Incidents & maintenance** section lists recent incidents and maintenance periods.

## Connect services to a provider

Connect the services in your [Service Catalog](https://coralogix.com/docs/user-guides/apm/features/service-catalog.md) to the providers they depend on, so you can see which of your services a provider incident affects. Each connected service shows the current status of its providers in the **Providers** column of the APM [Services page](https://coralogix.com/docs/user-guides/apm-v2/services.md#columns) and in the header of its [APM drilldown](https://coralogix.com/docs/user-guides/apm-v2/entity-drilldown.md). A service can be connected to many providers, and a provider to many services. A connection applies to the service in every environment.

By default, a connection covers all the provider's monitored components and regions, but you can scope the connection to the components and regions the service actually uses. This prevents an incident in a component or region the service doesn't use from being attributed to it.

To connect services to a provider:

1. Select the provider. In the **Connected services** section of its side panel, select **Add services**.

2. In the **Services** dropdown menu, select one or more services. Services already connected to the provider are marked **Already connected**.

3. Under **Depends on**, set what the services depend on. By default, all the components you monitor are selected.

   * **Region scope**: For providers that report per region, the regions every selected component inherits. To modify the scope, select **Edit regions**.
   * **Components**: Select the components the services depend on. Each component **Follows scope** by default. To set regions for a single component, expand it. A region you add is marked **Added** and kept, even when the region scope drops it. A region you remove is marked **Removed** and excluded, even when the region scope includes it.

   [![Connect services dialog for 1Password, showing the Services picker, the region scope, and the components list with each component following the scope](/docs/assets/images/provider-status-connect-services-affbf7b5bdd318b3d42d785bd201f307.webp)](https://coralogix.com/docs/assets/images/provider-status-connect-services-affbf7b5bdd318b3d42d785bd201f307.webp)

4. Select **Connect**.

The services appear in the **Connected services** section with what they depend on, either **All components** or the components and regions you selected, and the provider's card shows the number of connected services.

[![Connected services section listing three services, one scoped to specific components and regions and two to all components](/docs/assets/images/provider-status-connected-services-bef91896b5a61d37c6ba48f407d557df.webp)](https://coralogix.com/docs/assets/images/provider-status-connected-services-bef91896b5a61d37c6ba48f407d557df.webp)

You can also connect services when you [add a provider](#add-a-provider).

To change a connection, select **Edit** next to the service, update what it depends on, then select **Save**. To remove a connection, select **Remove** and confirm.

### Connections no longer monitored

A connection only covers components and regions you monitor. When you [edit the provider](#edit-or-delete-a-provider) to stop monitoring some of them, the connection is marked:

* **Partly monitored**: Some of the components or regions the service depends on are no longer monitored.
* **Not monitored**: None of the components the service depends on are monitored anymore.

To restore full coverage, either narrow the connection to the components you still monitor, or monitor the removed components again.

## Alerts

An alert sends you a notification when a provider you depend on has degraded. Notifications are delivered by your [Notification Center](https://coralogix.com/docs/user-guides/notification-center/introduction.md) routers, so a provider outage reaches the same channels as the rest of your alerts.

### Defining an alert

You can create [alerts that apply for one, multiple, or all monitored providers](#create-a-cross-provider-alert). An alert of this type applies to each included provider in full, across all of its components and regions. To watch only part of a provider, create an [alert that applies to a single provider](#create-a-single-provider-alert). A provider can have multiple alerts with different scopes, statuses, and notification targets.

You can also create both types of alerts while [adding a provider](#add-a-provider).

Every alert has the following:

* **Name**: Identifies the alert in the **Alerts** list and in the notifications it sends. Coralogix fills it in from the providers and status you select, and you can replace it with your own.
* **Status**: The status that triggers the alert. An alert triggers at the status you select or worse. An alert set to **Degraded** also fires on **Partial outage** and **Major outage**.
* **Priority**: The priority the alert carries when it fires. Each status has a default you can change: P3 for Degraded, P2 for Partial outage, and P1 for Major outage.
* **Notification targets**: The **Team**, **Service**, and **Environment** labels your [Notification Center](https://coralogix.com/docs/user-guides/notification-center/introduction.md) routers use to decide where the notification goes.

In the **Alerts** list, you can [enable, disable, edit, or delete](#edit-disable-or-delete-an-alert) an existing alert.

Note

[Editing or deleting a provider](#edit-or-delete-a-provider) also updates the alerts scoped to it.

### Create a cross-provider alert

A cross-provider alert covers one, several, or all of the providers you monitor, each across all of its components and regions. To create one:

1. Select the **Alerts** tab, then select **Create alert**.
2. Optionally, replace the **Name**. Coralogix fills it in from the providers and status you select.
3. Under **What to alert on**, select **Edit providers**, then select the providers to include. By default, all the providers you monitor are included.
4. Set **Alert when** to **any** or **all** of the included providers reaching the status.
5. Under **Status**, select the status that triggers the alert: **Degraded**, **Partial outage**, or **Major outage**. This is the minimum status: the alert also fires on any worse status.
6. Set the **Priority**. Each status has a default you can change: P3 for Degraded, P2 for Partial outage, and P1 for Major outage.
7. Under **Who to notify**, set at least one of **Team**, **Service**, or **Environment**. The [Notification Center](https://coralogix.com/docs/user-guides/notification-center/introduction.md) uses these labels to route the notification.
8. Select **Create alert**.

[![Create alert panel for a cross-provider alert, showing the name, the providers it covers, the status and priority, and the notification labels](/docs/assets/images/provider-status-create-alert-cross-6c02c4cbc8e97937e88efb14727bdf30.webp)](https://coralogix.com/docs/assets/images/provider-status-create-alert-cross-6c02c4cbc8e97937e88efb14727bdf30.webp)

The new alert appears in the **Alerts** list, and is applied to every selected provider.

### Create a single-provider alert

A single-provider alert covers a specific combination of regions and services within one provider. To create one:

1. Select the provider, then select **Create alert** in the **Alerts** section of its side panel.

2. Optionally, replace the **Name**. Coralogix fills it in from the provider and status you select.

3. Under **What to alert on**, set the scope of the alert:

   <!-- -->

   * **Region scope**: Regions the alert applies to. Select **Edit regions** to edit, add, or remove regions. By default, all regions are included.
   * **Services**: Services the alert applies to. You can add or remove services. By default, all monitored services are included.

4. Set **Alert when** to **any** or **all** of the selected services reaching the status.

5. Under **Status**, select the status that triggers the alert: **Degraded**, **Partial outage**, or **Major outage**. This is the minimum status: the alert also fires on any worse status.

6. Set the alert **Priority**.

7. Under **Who to notify**, set at least one of **Team**, **Service**, or **Environment**. The [Notification Center](https://coralogix.com/docs/user-guides/notification-center/introduction.md) uses these labels to route the notification.

8. Select **Create alert**.

[![Create alert panel for a single provider, showing the services it covers, the any or all selector, and the status](/docs/assets/images/provider-status-create-alert-single-86c5a142582dc39b86b159b2a0f21308.webp)](https://coralogix.com/docs/assets/images/provider-status-create-alert-single-86c5a142582dc39b86b159b2a0f21308.webp)

The new alert appears in the provider's **Alerts** list, alongside any cross-provider alerts that include it.

### Edit, disable, or delete an alert

The **Alerts** tab lists every alert with the status it triggers at, its priority, and the labels it routes on. Filter the list by provider, or select **Enabled only** to hide alerts that are turned off.

[![Alerts tab listing every alert with the status it triggers at, its priority, the labels it routes on, and the Enabled toggle](/docs/assets/images/provider-status-alerts-tab-009d0f155cb6853d8d8ee1c0eba837df.webp)](https://coralogix.com/docs/assets/images/provider-status-alerts-tab-009d0f155cb6853d8d8ee1c0eba837df.webp)

To manage alerts:

* Use the **Enabled** toggle to stop an alert from firing without deleting it.
* Select **Edit** to modify an alert.
* Select **Delete** and confirm to delete an alert.

[![Edit alert panel, showing the Enabled toggle, the name, and the services the alert covers](/docs/assets/images/provider-status-edit-alert-a730ccc2b77cca1f27d4c19d09680a27.webp)](https://coralogix.com/docs/assets/images/provider-status-edit-alert-a730ccc2b77cca1f27d4c19d09680a27.webp)

## Limitations

* Availability history starts when you add the provider. Status updates that occurred before you added the provider are not reported.
* Connections are made by service name. Renaming a service does not carry its connections over, so connect the service again under its current name.
* [Editing which components you monitor](#edit-or-delete-a-provider) takes effect immediately, but past uptime is not recalculated. The **Uptime history** bar keeps the segments already recorded and reflects the new configuration from the moment you save. It does not indicate where the change occurred.