Your vendor's outage is your outage.
Hear it from us, not your customers.
When Stripe stops answering or Cloudflare declares an incident, your product breaks and your support queue fills — while the announcement sits on a status page nobody was watching. Vendor watches put every service you depend on in one list, with alerts in your email, Slack, or Discord.
Official status feeds, polled for you
These vendors' own status pages are polled every 5 minutes — when they declare an incident, you're alerted with their component-level detail:
Plus reachability watches on any of the 1177 services in our public catalog — Stripe, AWS, PayPal, and the long tail — probed directly with 4 methods, no official feed required.
The status page is not the truth
During real incidents, official status pages famously lag reality by 30+ minutes. Our direct probes are the second opinion: when the feed says green and the API times out, you see both signals and believe the probes.
One list, one alert format
Instead of eleven per-vendor email subscriptions in eleven formats, one watch list feeding the channels your team already reads — email on every plan, Slack, Discord, and webhooks on Pro.
Rides probes we already run
Every watch attaches to monitoring that powers our public status pages — the marginal cost is near zero, which is why watches are priced like a feature instead of a product.
Plans
- 3 watched vendors
- Email alerts on incident + recovery
- Checked every 5 minutes
- Unlimited watched vendors
- Slack + Discord + webhook delivery
- Everything else Pro includes
Standalone status-page aggregators sell this exact capability as their entire product, at many times this price. Ours is bundled because the probes already exist. No SLA theater, no invented regions — the honest mechanics are documented on every check page.
Questions
What exactly is a vendor watch?
A subscription to a service you depend on but don't run. When its state changes — its own status page declares an incident, or our direct probes stop reaching it — you get the same alert pipeline as any monitor: email on every plan, Slack, Discord, and webhooks on Pro.
Where does the data come from?
Two honest sources, kept distinct. Status-feed watches poll the vendor's own status page feed every 5 minutes — that's the vendor's declared truth about component-level incidents. Reachability watches use our 4-method direct probes against the service itself — that's what's actually answering, which often disagrees with the status page during the first half hour of a real incident.
Which vendors have status-feed watches?
The vendors whose official feeds we poll are listed on this page — currently 12, including Discord, GitHub, Cloudflare, and the major AI providers. Everything else in our 1177-service catalog (Stripe, AWS, and the rest) is available as a reachability watch. If a feed vendor you need is missing, tell us and we'll add it if its feed is publicly pollable.
Why not just subscribe to each vendor's status page directly?
You can — one inbox subscription per vendor, each in its own format, none of them covering the case where the status page stays green while the API times out. A watch list puts every vendor in one place, one alert format, one Slack channel, with our independent probes as the second opinion.
Does this count against my monitor limit?
No. Watches have their own allowance — they ride probes we already run for the public site, which is why they're cheap: 3 on Free, unlimited on Pro.