Third-party and vendor status monitoring

When a client site breaks because of a dependency — a payment processor, a CDN, a hosting provider, an email service — the client contacts you first regardless of whose fault it is. Vendor dependency monitoring watches that vendor's own public status page directly, so you already know before anyone asks.

Adding a dependency

From a site's Infrastructure tab, the Vendor & dependency status card lets you add a dependency two ways:

1. Curated vendor — pick from the supported vendor list below. The status page URL and check driver are pre-filled.
2. Custom — paste the URL of any other Statuspage.io-hosted status page. DownCTL derives the standard /api/v2/summary.json endpoint from the base URL you provide. Not every vendor uses Statuspage.io — if the URL doesn't return that format, the check will report Unknown with an error message rather than silently failing.

Supported vendors

Don't see a vendor you depend on? Email support@downctl.com with the vendor name and status page URL — most requests are added within 24–48 hours.

Check cadence

Vendor dependencies are checked every 5 minutes.

Narrowing to specific components

Most vendor status pages report dozens or even hundreds of individual components (Stripe alone lists services like Global payments, Checkout, and Stripe Terminal separately). By default, adding a dependency watches the whole vendor — any degradation anywhere on that status page will show up and can trigger an alert.

If a site only depends on one or two of those services, select only the specific component(s) that actually matter. Once narrowed:

• The tile's status only reflects the health of the selected component(s), not the vendor's overall page status.
• Alert rules scoped to that dependency only fire when a selected component is degraded or down — an unrelated incident on the same vendor's status page won't trigger anything.

Alerting

Vendor dependency monitors participate in the same alert rule system as every other monitor type. Create a rule with the Vendor status degraded trigger, scoped to "all dependencies" or specific ones, with the usual failure/recovery threshold settings. A Degraded status counts as a failure for alerting purposes, not just Down — a vendor reporting a minor incident is still worth knowing about.

Supported drivers

Vendors that don't expose one of these formats can't be added as a "Custom" entry, since there's no generic way to parse them. Support for additional bespoke vendors is added on a per-vendor basis as drivers are built.