Third-party status

Your product depends on services you don't run: payment gateways, clouds, CDNs, email and SMS providers. Third-party status follows the official status pages of those services and sends their incidents through your normal alert channels. You can also show their status on your own status pages.

SutramX reads what each provider publishes on its official status API or feed. It does not test the services itself. To check that an integration actually works for you, use an API & multi-step check as well.

Following services and getting their alerts is a plan feature. See Plans & limits. Every plan can browse the catalogue.

Follow a service#

1. Go to Third-party status in the sidebar (under Checks & insights).
2. Search for the service or filter by Category.
3. Click Follow on the service.
4. Choose what to watch and when to alert (see the options below).
5. Click Follow.

The service moves to Services you follow, with its current status. Changes appear under Recent updates. Click Alerts on the service to change the settings, or Unfollow to stop. Unfollowing stops alerts; status pages that list the service keep showing it.

Follow options#

Component filtering notes:

• With Only these components, provider-wide incidents that name no component are still sent.
• Some providers publish only an incident feed with no components (for example Azure and GitLab). Use keywords for them.
• For Amazon Web Services, use keywords to narrow alerts to your regions and services, for example us-east-1, EC2.

A workspace can follow up to 100 services.

Supported services#

SutramX follows these services through their official status APIs and feeds:

Workspaces billed in India see India-focused providers (such as Razorpay, Juspay and Setu) first. If a service you rely on is missing, email support@sutramx.com.

What you get alerted about#

SutramX polls each followed provider every 2 minutes (every 5 minutes for Amazon Web Services, Google Cloud, Microsoft Azure, Firebase and Google Workspace) and compares the result with the last poll. Each change becomes an update:

Rules:

• Resolutions and recoveries are filtered with the same Alert from level as the original problem, so you always get both halves.
• Scheduled maintenance is not alerted when it is announced, only when it starts and ends.
• At most 5 updates per service are sent from one poll, so a large provider outage doesn't flood your channels.
• A component that flips back and forth on every poll is not alerted each time.
• Updates older than 24 hours that could not be delivered are dropped rather than sent late.

Where alerts go#

Third-party alerts go to your workspace's alert recipients by email and to your connected Slack, Discord, Microsoft Teams, Google Chat, Mattermost, Telegram and webhook channels. Webhooks receive the events third_party.incident, third_party.resolved and third_party.maintenance.

Third-party alerts are notices, not SutramX incidents. They don't open incidents, page your on-call rotation or affect your uptime.

Show third-party status on a status page#

You can show the official status of the services you depend on alongside your own components, so your users can see when a problem is upstream.

1. Go to Status pages and open a status page.
2. Find the Third-party services section.
3. Choose it under Add a service and click Add.
4. Optionally choose Components (optional) to show only some components. With none selected, the page shows the provider's overall status.
5. Optionally set Name on the page (optional), for example Payments (Stripe).
6. Use Move up and Move down to order them, then click Save third-party services.

A status page can list up to 30 services, with up to 50 components each. You don't need to follow a service to show it on a status page, but your plan must include third-party status. See Status pages overview.

Common questions#

The provider's own page shows an incident but I got no alert. Check Alert from (a minor incident is skipped with Partial outages and worse), your component selection and keywords, and that Send alerts is on. Recent updates shows what SutramX picked up.

Why do I see an update minutes after the provider posted it? SutramX polls every 2–5 minutes depending on the provider, and providers often post a few minutes after an issue begins.

Does a third-party incident affect my monitors or uptime? No. Third-party updates are kept separate from your monitors. To hold back alerts for monitors that depend on another of your own monitors, use monitor dependencies; see Reliability insights.