- Home
- Monitoring
- Third-party monitoring
Third-party monitoring: know when it is the provider, not you
Follow the status feeds of services your site depends on. When one turns non-operational you get a single alert, and incidents on the monitors you linked are tagged with that provider for the next 30 minutes.
- 30 monitors free
- No credit card
- Failures confirmed from other regions
- GitHub
- Operational
- Cloudflare
- Degraded
- DigitalOcean
- Operational
- Your incidents tagged
- Cloudflare (30 min)
Illustrative example
Check it now, in your browser
No account. Third-party monitoring: type a target and see roughly what it looks at. Nothing you type is stored.
Reads the provider’s public status JSON from your browser, with the same indicator mapping Tenium uses when you follow a provider.
What a third-party monitor looks at
Followed status feeds
Pick providers from a catalogue (Stripe, Cloudflare, AWS, Vercel, GitHub, Mailgun, Postmark, PayPal, Twilio, OpenAI, Let’s Encrypt, Google Workspace). Each is read from its public statuspage.io JSON or RSS/Atom feed.
Polled every two minutes
Each feed is read about every two minutes. A provider that moves from operational to degraded or outage triggers one alert to the contact you chose.
Incidents get a cause
For 30 minutes after a feed goes non-operational, incidents on the monitors you linked to it carry the provider as the upstream cause, in the alert and in the report.
Honest limits
This reads what the provider chooses to publish, which can lag the real outage. It complements your own checks; it never replaces them. The feature is in beta.
Third-party monitoring: what an alert looks like
The same event arrives as an e-mail, a Telegram message or a Slack card. This is the wording the channels send; the host, times and numbers are made up.
Cloudflare
Cloudflare status: degraded — Elevated error rates on some edge locations
| Provider | Cloudflare (statuspage.io) |
|---|---|
| Status | degraded |
| Linked monitors | shop.clienta.com, api.clienta.com |
| Next step | Upstream provider Cloudflare is reporting problems. Incidents on linked monitors in the next 30 minutes will be tagged "Cloudflare". |
Open monitor
Tenium · checked from Amsterdam · 14:02 UTC
Tenium alerts
🟠 CLOUDFLARE DEGRADED · Cloudflare status: degraded — Elevated error rates on some edge locations
open
TTenium APP 2:02 PM
CLOUDFLARE DEGRADED · Cloudflare
Cloudflare status: degraded — Elevated error rates on some edge locations
- Provider: Cloudflare (statuspage.io)
- Status: degraded
- Linked monitors: shop.clienta.com, api.clienta.com
Open monitor
Upstream provider Cloudflare is reporting problems. Incidents on linked monitors in the next 30 minutes will be tagged "Cloudflare". · checked from Amsterdam
Third-party monitoring: e-mail, Discord and Google Chat work on every plan; Slack, Telegram, Teams and Mattermost start on Starter. There are no SMS or voice-call alerts.
Response time with a threshold
Every check stores how long the response took. Third-party monitoring: drag the threshold and see when a slow-response alert would have fired.
How fast you find out
Pick a plan to see its check interval and how long a failure takes to reach you, including the confirmation round.
Third-party monitoring: a failure lands at a random moment between two checks, so on average you wait half an interval, and the worst case is a whole interval plus the confirmation window. A single failing region is not enough: all two regions must agree before an incident opens. The other regions are asked straight away, and we allow up to 60 seconds for the answers.
How to set up third-party monitoring in 30 seconds
Follow the providers you depend on
Open the third-party page in the app and follow the services behind your checkout, mail or deploys.
Link the monitors
For each followed provider, tick the monitors that rely on it. Only linked monitors get tagged.
Pick one contact
Choose who is told when a provider changes state. Telegram or e-mail works well; the alert names the provider and its own status text.
Read incidents with context
When your site fails during a provider incident, the incident says so, and the monthly report separates your downtime from theirs.
What each error means
This is the text an incident shows in its Error line, the usual cause, and the first thing to look at.
DEGRADEDProvider status: degraded
The provider’s status page reports a minor incident. You get one alert on the transition, and incidents on linked monitors in the next 30 minutes are tagged with the provider.
Shown as: Provider status: degraded
OUTAGEProvider status: outage
The provider reports a major or critical incident. Your own monitors are probably failing for the same reason.
Shown as: Provider status: outage
UNLINKEDMy incident was not tagged
Tags apply only to monitors you linked to that provider, and only within 30 minutes of the status turning non-operational.
Shown as: My incident was not tagged
FEEDStatus feed not readable
The provider’s status JSON or RSS did not load. The feed is skipped on that poll and tried again; nothing alerts.
Shown as: Status feed not readable
Third-party monitoring by plan
| Free $0/mo | Starter $7/mo | Pro $29/mo | Agency $59/mo | |
|---|---|---|---|---|
| Available | ✓ | ✓ | ✓ | ✓ |
| Monitors | 30 | 100 | 300 | 1000 |
| Fastest interval | 5 min | 1 min | 30 s | 30 s |
| Regions | 1 | 2 | 2 | 2 |
| Custom headers | — | — | ✓ | ✓ |
| Response-time alerts | — | — | ✓ | ✓ |
| Escalation to a second contact | — | — | ✓ | ✓ |
| Status pages | 1 | 3 | 10 | Unlimited |
Other monitor types
The question it answers
When checkout stops working, the first minutes go to one question: is it us or is it them? Third-party monitoring answers it from the provider's own public status feed. You follow the services your site leans on, link them to the monitors that depend on them, and Tenium reads each feed about every two minutes.
When a followed provider changes from operational to degraded or outage, the contact you chose gets one alert naming the provider and its own status text. For the next 30 minutes, incidents that open on the monitors you linked to that provider are tagged with it as the upstream cause. The tag shows up in the alert, the incident and the monthly report, so a client can see that the hour of downtime started at a payment processor.
What it reads, and what it cannot know
Feeds are statuspage.io JSON endpoints where a provider has one, and RSS or Atom otherwise. The catalogue today covers Stripe, Cloudflare, AWS, Vercel, GitHub, Mailgun, Postmark, PayPal, Twilio, OpenAI, Let's Encrypt and Google Workspace. The page demo above reads a few of those feeds live from your browser so you can see the status words.
The limits are real. A provider publishes when it decides to, and that is often later than the problem starts. A feed that is unreachable is skipped on that poll and nothing alerts. Tagging is a correlation inside a 30-minute window, not a proof of cause. The feature is in beta, and it exists to add context to your own checks, never to replace them.
Setting it up well
Follow only what would really hurt: the payment processor, the CDN, the mail API, the platform that hosts the app. Following twenty services creates twenty reasons to ignore the alert. Link each provider to the specific monitors that break when it does, so the tag stays meaningful. Send the provider alert to a quieter channel than the down alert, because it is information, not a page.
Pair it with a website or API monitor on the thing that actually matters, and with a public status page so clients see the same story you do.
Third-party monitoring questions
Does following a provider cost extra?
It is a beta feature and the app does not charge for it separately. The plan table above shows what each plan includes for the monitors you link.
Can I add a provider that is not in the catalogue?
Not today. The catalogue is fixed. If you rely on a service that is missing, tell us through the [contact page](/contact).
Will it tell me before the provider admits the outage?
No. It reads the feed. Your own monitors will usually notice first, and the tag appears on those incidents afterwards when the feed catches up within the window.
Why are some of my incidents not tagged?
Only monitors linked to that provider are tagged, and only for incidents that open within 30 minutes after the feed turns non-operational.
Start third-party monitoring free
30 monitors on the Free plan, no card needed, with failures confirmed from other regions (2 regions live today). Upgrade when the client list grows.