Vendor & dependency status
Know when it's your vendor — not you.
Half your 3am pages aren't your fault. Your AI provider, your email API, a cloud region — when a third party goes down, your stack goes red and your team 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.
No credit card · nothing to install
What it watches
Straight from the vendor's own status.
A vendor monitor reads a provider's official status page — the one the vendor posts its own incidents 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.
Pick from our supported list — Anthropic, OpenAI, GitHub, Cloudflare, Vercel, Datadog, Twilio, SendGrid and more. Each one reads that provider's official status feed.
AWS is watched at the service×region level from its health feed — so “S3 in eu-west-1” can show as degraded without dragging every other service with it.
Each vendor monitor carries the vendor's own indicator — operational, degraded, or a major/critical outage — plus the affected components and any unresolved 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”.
How it works
Pin the vendors a monitor leans on.
On a 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.
Pin in the monitor form. Open a monitor and add its dependencies from the vendors you already watch. Only vendors you monitor can be pinned — no dangling references, no surprise data.
One rollup, no noise. 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.
Honest by design
We show you the facts. We don't guess causation.
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.
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 — just faster.
When a vendor you watch posts an outage or degradation, that vendor monitor alerts on its own — with the vendor's incident title or the affected components — so you don't have to be staring at a monitor to catch it.
Why it matters: a false “it's the vendor” sends you to wait on a status page while your real bug ships to more users. Showing status without asserting cause keeps you honest and keeps you moving.
Stop proving it wasn't the vendor.
Add a vendor to watch, pin it to the monitors that depend on it, and let the answer show up on its own. Vendor monitors and pinning are on the free plan.