New

Dependency Monitoring

Most of your outages start somewhere you do not control. See the status of the services you depend on, right next to the monitors they take down.

Not every red dashboard is your fault

Your payment provider degrades. A CDN has a regional incident. Your email API starts timing out. Your monitors go red — and your on-call spends the first twenty minutes proving the problem is not theirs to fix.

NoDisrupt watches the status pages of the providers you depend on and puts their state next to your own checks, so the first thing you see is whether this one is yours or someone else's.

Their status, on your dashboard

Pick the services you rely on and NoDisrupt reads each one's official status page — operational, degraded or outage — and keeps it current. No scraping, no guesswork: it is the provider's own reporting.

A provider that is quiet stays quiet. The moment one degrades, it surfaces.

DependenciesLive
  • Stripe
    API, Webhooks
    Operational
  • Cloudflare
    All components
    Degraded
  • SendGrid
    Mail Sending
    Outage
  • GitHub
    Actions
    Operational
Upstream outage
SendGrid — Elevated delivery latency

The provider is reporting a Mail Sending incident. Your monitor is still passing its own checks — the failures are downstream of this.

Opened 09:14 · annotated on your incidentView status page →

Your incidents, with the cause attached

When a provider you depend on has an open incident, your own incident is annotated with it — so whoever responds can see at a glance that the failure is downstream of a third party, not a bug on your side.

The link to the provider's status page is right there. No hunting for whether it is just you.

Do not page for a fire you cannot put out

Every dependency has a mode. Alert is the default — nothing changes, the incident opens and carries the upstream cause. Suppress holds the page while the provider reports an outage: the incident still opens and is still recorded, but your on-call is not woken at 3am for a provider only they can fix. Paging resumes the moment the provider recovers.

Alert

Page as normal. The incident opens, annotated with the provider's outage so the responder has the context immediately.

Suppress

Hold the page while the provider is down. The incident is still opened and annotated — you keep the record, you skip the needless wake-up.

Attach it where it belongs

A provider one endpoint uses belongs on that monitor. A provider the whole project runs on belongs on the project, inherited by every monitor in it. And the suppliers your whole company depends on get a standalone organisation-wide view. You set it once, at the right level.

Per monitor

One endpoint, one provider. Scoped to the check that needs it.

Per project

Shared across a project and inherited, read-only, by its monitors.

Per organisation

A company-wide view of the suppliers everything depends on.

Thousands of providers

Stripe, AWS, Cloudflare, GitHub, Twilio, SendGrid, OpenAI, Anthropic and thousands more that publish a status page.

Whole provider or components

Depend on all of a provider, or just the components you use -- Stripe's API without its Dashboard, say.

Straight from the source

It reads the provider's own published status, not a guess. When they say degraded, you see degraded.

Show it on your status page

Optionally list your dependencies publicly, so your users see an upstream outage is the cause -- without a ticket.

Quiet when it should be

Suppress mode keeps the record without the 3am page for an outage only the provider can resolve.

Nothing to install

It runs from the monitoring you already have. No agent, no credentials, no new access.

Know whose outage it is

Dependency monitoring is included on Pro and Elite, alongside everything else NoDisrupt watches for you.