Overview

Your own monitors tell you when your website, server, or API goes down. But a lot of downtime starts upstream, at a payment provider, a cloud platform, or a messaging tool your product relies on.

3rd party services let you track the official status pages of the services you depend on (for example, Stripe, AWS, or Slack). When a provider reports an incident, UptimeRobot notifies your usual alert contacts, so you know whether the problem is on your side or theirs.

How it works

UptimeRobot follows the provider's public status page. It does not send requests to the provider's systems itself.
The incidents you see are the provider's own incidents, as published on their status page – including their title, severity, and updates.
You can track the whole service or only the components you actually use (for example, only one region or one product).
3rd party services have their own allowance and do not count toward your regular monitor limit.

Plan limits

3rd party services are available on paid plans. The number of services you can track depends on your plan:

Plan	3rd party services
Free	Not included
Solo	1–5 (depending on plan size)
Team	20
Scale	40–100 (depending on plan size)
Enterprise	Custom

The exact limit for your account is shown in the 3rd party services section and on the pricing page.

Adding a service

In the dashboard, open 3rd party services and click on "New 3rd party monitor".
In Find a provider, type the name into Search providers or pick one from Popular services.
Choose who should be notified. Your personal E-mail and Push contacts are preselected; integrations (Slack, Microsoft Teams, webhook…) are available but need to be selected manually. You can also set a delay and repeat per contact.
Under Alert when, choose which incidents should notify you (see below).
Under Components of the service to monitor, keep all components or select only the ones you use (see Components below).
Click Create 3rd party monitor.

Components

Many providers split their status page into components, for example, individual products, APIs, or regions. Under Components of the service to monitor, you can choose which of them matter to you:

All components (default): you’re alerted about incidents on any part of the service.
Selected components only: you’re alerted only about the parts you actually use. This is useful for large providers like AWS or Stripe, where most incidents might not affect you.

You can change the selection at any time in the service’s settings.

Notification settings

Alert when (severity)

Option	What it does
All incidents (default)	You are notified about every incident the provider reports on the components you track.
Only major incidents	You are notified only about major incidents. Incidents where the provider doesn't state a severity still notify you, so you don't miss an outage.
No incident notifications	No alerts are sent. Incidents are still shown in the dashboard.

Incidents

Incidents belong to the provider – UptimeRobot shows them exactly as the provider publishes them. You can't acknowledge, edit, or comment on them like incidents of your own monitors.
As soon as you start tracking a service, you can see the provider's recent incident history, not only incidents that happen from now on.
Open an incident to see its details and updates. The activity log shows which alerts were sent for it – the channel, the recipient, the alert contact, and whether and when it was delivered.

Limitations

3rd party services can't be paused. If you don't want alerts for a while, set Alert when to No incident notifications, or delete the service.
3rd party services can't be renamed. They always use the provider's name.
Each provider can be tracked only once per account. To change what you track, edit the existing service.
Alerts depend on the provider updating its status page. If the provider doesn't report an incident, UptimeRobot can't alert you about it. To check a specific endpoint yourself, use an API monitor alongside.

Public API v3

3rd party services are monitors of the type THIRD_PARTY_SERVICE. You create, update, and delete them through the regular monitor endpoints, and there are extra endpoints for providers and incidents. Requests use your API key as a Bearer token.

Endpoint	What it does
`GET /third-party-providers?search=stripe`	Search the provider catalog and get the provider ID
`GET /third-party-providers/{id}`	Provider details, including its component IDs
`POST /monitors`	Start tracking a service
`PATCH /monitors/{id}`	Change tracked components or notification settings
`DELETE /monitors/{id}`	Stop tracking a service
`GET /monitors/{id}/third-party-service/status`	Current state of the service
`GET /monitors/{id}/third-party-service/incidents`	Incident history
`GET /monitors/{id}/third-party-service/incidents/{incidentId}`	One incident, with its updates and affected components
`GET /monitors/{id}/third-party-service/incidents/{incidentId}/activity-log`	Which alerts were sent for the incident

Example: POST /monitors body that tracks Stripe, notifies only about major incidents, and watches only two components:

{
  "type": "THIRD_PARTY_SERVICE",
  "config": {
    "thirdPartyService": {
      "providerId": 801,
      "trackedComponentIds": [106342, 106343],
      "notify": { "severity": "major", "incrementalUpdates": false }
    }
  }
}

notify.severity: all, major or none (the same as Alert when). notify.incrementalUpdates: also notifies on every update of an incident.
trackedComponentIds is optional. Leave it out to track all components.
assignedAlertContacts is optional. Leave it out to use your account's default alert contact.
To change the components later, send PATCH /monitors/{id} with a new config.thirdPartyService.trackedComponentIds list. Send null to track all components again.

CLI

The UptimeRobot CLI supports 3rd party services from version 1.1.0.

# Find the provider and its component IDs
uptimerobot third-party-providers list --search stripe
uptimerobot third-party-providers get 801

# Start tracking (omit --components to track all components)
uptimerobot monitors create third-party-service --provider-id 801 --components 106342 --components 106343 --notify-severity major

# Check the state and incidents
uptimerobot monitors third-party-service status MONITOR_ID
uptimerobot monitors third-party-service incidents list MONITOR_ID
uptimerobot monitors third-party-service incidents get MONITOR_ID INCIDENT_ID
uptimerobot monitors third-party-service incidents activity-log MONITOR_ID INCIDENT_ID

# Stop tracking
uptimerobot monitors delete MONITOR_ID

MCP Server

The UptimeRobot MCP server (https://mcp.uptimerobot.com/mcp) lets your AI assistant search providers, start tracking a service, change its components and notification settings, list incidents, and read their activity log. For example: "Track Stripe and notify me only about major incidents."

3rd party services – track the status of services you depend on