SutramX notices when a vendor API such as Stripe, OpenAI, an AWS region, Razorpay or Supabase is failing for several SutramX customers at once, from its own checks rather than the vendor's status page. Your incident and alert then say "Likely external", and show how the vendor's official status page compared. On every plan.
How it works
Many SutramX customers monitor endpoints that call the same vendors, or the vendor APIs directly. When checks against a known vendor API hostname start failing for several different customer accounts at the same time, SutramX marks that vendor as degraded and links the matching incidents to it.
The Vendor health view in the dashboard shows each vendor's "Detected by SutramX" state next to its "Official status", so you can see whether the vendor has acknowledged the problem yet.
The same aggregate signal is public: the live vendor status pages show whether Stripe, Razorpay, AWS, OpenAI and the other vendors look down right now, with 30 days of disruption history.
Privacy by design
Only aggregate signals are used. A vendor is only flagged when at least 3 different customer accounts are affected, only known vendor API hostnames are matched (your own domain is never pooled, even behind a CNAME), and no customer's monitors, URLs or results are ever shown to another customer.
Only failures that point at the vendor count: timeouts, 5xx errors, connection failures and TLS errors. Detection adds context to your incident; it never changes whether or when an incident opens or an alert is sent.
What it does not promise
Detection depends on enough customers checking that vendor at the time, and the comparison with the official status depends on how often the status page is polled. SutramX often sees a problem before a status page is updated, but not always, and it never replaces your own checks of the integration.
Specifications
| Plans | Every plan, including Free |
|---|---|
| Providers | About 80, including Stripe, OpenAI, AWS (by region), Razorpay and Supabase |
| Signal | SutramX check results across customers, not vendor status pages |
| Threshold | At least 3 different customer accounts affected |
| Matching | Known vendor API hostnames only |
| Shown as | "Likely external" on the incident and alert; Vendor health view |
Learn more
- Guides: Incident Response Basics and Why Is My Website Down?
- Free tools: Is It Down?
- Use cases: Monitoring for SaaS Platforms
- Comparisons: SutramX vs Better Stack
- Documentation: Vendor health and Third-party status
- More from SutramX: Live status of Stripe, AWS, OpenAI and other vendors