One dashboard for every vendor you depend on
Starter is $19 a month for 30 vendors.
Most teams learn about a vendor outage from a customer, a Slack rumor, or someone who happened to open the right status page. A vendor status dashboard turns that into a habit: one screen that lists the services you actually use, with the current state of each.
What belongs on the board
Not every public status page. Only the vendors that would slow you down if they failed.
- Payments, auth, email sending and the cloud region you run in
- Source control, CI and the package registry your deploys pull from
- Chat, video calls and the help desk your staff live in
- DNS, CDN and the database host, if those are someone else's job
Five vendors is enough to start. Most product teams settle around 15 to 30 once they write the list down.
What each row should show
A useful board is boring on purpose. For every vendor you want:
- Name and the component you care about, not a 40-item dump
- Current state: operational, degraded, partial outage, major outage, maintenance
- When it last changed, and when you last polled
- The latest sentence the vendor posted, if anything is open
- A link to the official status page for people who want the full timeline
Color helps, but text has to stand on its own. Support staff print this, screenshot it, and paste it into tickets.
Who looks at it
Engineering during an incident, to see whether the error spike matches a vendor post.
Support before they escalate. If Stripe webhooks are degraded, they can say so instead of guessing at your app.
IT for the tools staff use all day: email, calendar, file storage, video.
On Pro, Outage Clock gives you a private page with this view. You can send the link to people who should not have a login.
How it stays current
We poll each official status page every few minutes, parse the components, and store a snapshot. One poll is shared across every customer who follows that vendor, so we are not hammering GitHub because fifty of you follow it.
A light reachability check of the vendor's homepage or API sits next to the official feed. It will not catch a subtle regional issue, but it flags a full outage when the status page is quiet or slow to update.
Keep the board small
The failure mode is following every component at a large cloud provider. The board turns into a weather map and nobody trusts it. Filter to the products and regions you run. Use email or Slack for urgent vendors, and the daily digest for the rest.
Questions
Can people without an Outage Clock account see the dashboard?
On Pro, the private dependency page is a link you can share. It does not list other customers' vendors.
Does this replace our own status page?
No. This board is for vendors you buy. Your status page is for the product you sell. They complement each other: when a vendor is down, you can post a note on yours with less guesswork.