Half your 3am pages aren't your fault. Your auth provider, your payment API, a cloud region — when a third party goes down, your stack goes red and your on-call burns twenty minutes proving it wasn't them. CuliPulse watches your vendors' own status and shows it right next to the monitors that depend on them, so the answer is on the screen before you start digging.
A vendor monitor reads a provider's official status page — the same one their SRE team publishes to — and turns it into a monitor you can alert on, roll up, and pin. No scraping a marketing page; the machine-readable status feed itself.
Any provider on a standard status page (Statuspage-style) — Anthropic, OpenAI, Stripe, GitHub, Cloudflare, Slack, Twilio and more. Pick from the gallery or point at a status URL.
AWS is watched at the service×region level from its health feed — so “S3 in eu-west-1” can be red without dragging every other service down with it.
Each vendor monitor carries an indicator — operational, degraded, or a major/critical outage — plus the affected components and any active incident the vendor has posted.
Vendor status is checked on your normal monitor interval, agentless. A status page that's briefly unreachable is reported as inconclusive — never a false vendor “down”.
On any monitor, pin the third-party services it depends on. Their live status then shows on that monitor's page and rolls up into one line — so when you open a red monitor, you can see at a glance whether one of its dependencies is having a bad day too.
Open a monitor, add its dependencies from the vendors you already watch. Only vendors you monitor can be pinned — no dangling references, no surprise data.
The monitor's page shows each pinned vendor's current status and one factual line — an active incident, the degraded components, or the vendor's own summary. No timestamps to chase, no second dashboard.
When a monitor pages you, the dependency context comes with it — and a vendor's own outage fires as its own alert transition, so the vendor problem is never silent.
Pinning is context, not blame. CuliPulse shows a dependency's status beside your incident; it does not claim the vendor caused it. You get the two facts side by side and draw the conclusion — which is exactly what a good on-call does anyway, just faster.
It's tempting to draw an arrow from “vendor is down” to “so that's why you're down” — and it's often wrong. A vendor can be degraded while your incident is something else entirely. CuliPulse deliberately stops at the facts: here is your monitor's state, here is each dependency's vendor-reported status, at the same moment. The judgment stays yours.
You don't have to be staring at a monitor to catch it — when a pinned vendor posts an outage, CuliPulse sends the alert with the vendor, the affected components, and when it started.
Add a vendor to watch, pin it to the monitors that depend on it, and let the answer show up on its own. Every feature is on the free plan.
Start free