How to monitor AWS, Stripe, Supabase and other providers your app depends on
A step-by-step guide to third-party service monitoring: find the providers your site uses, watch only the regions and components you rely on, and choose when to be alerted.
· 4 min read · By the Spot Downtime team
Your site can be up while the services behind it fail: the database host, the payment API, the email provider. A third-party service monitor watches a provider's official status page and alerts you, through the same channels as your own monitors, when it reports an outage in the parts you use. Spot Downtime covers 93 providers, including AWS, Google Cloud, Azure, Supabase, Stripe, Vercel, Cloudflare and OpenAI.
Step 1: find the services you use
- Open Monitors, click Add monitor and choose Third-party service.
- Enter your domain, such as
example.com. Spot Downtime reads its DNS, headers and pages to find its hosting, CDN, email, payments and sign-in providers. - Add the ones it finds, and pick anything else from the list. Services only your servers call, like a database host, can't be seen from outside, so add those by hand.
Step 2: narrow it to what you use
Big providers almost always have an incident open somewhere. To avoid alerts about regions you don't use, narrow each service to its components or regions, for example Supabase's Postgres in eu-west-1.
Supabase · Postgres (eu-west-1) is down: alert sent to #ops-alerts
- AWS asks for regions. Pick the ones you run in, plus Global services if you use Route 53, IAM or CloudFront.
- Leave it unnarrowed to go by the incidents the provider declares for the whole service.
Step 3: choose when to be alerted
Set Alert on to Outages (partial or major), or to Outages and degraded performance if slowdowns matter to you. Maintenance the provider announces never alerts. Then click Add monitor.
Step 4: put it to work
- On your status page. Add the service next to your own monitors, so customers see that a payment problem is Stripe's, not yours. See how to set up a status page.
- Check the alert channel with Send test under Alerts.
Good to know
- Status pages are read at least once a minute.
- A provider's status page speaks for its whole platform. For AI providers, an LLM API monitor also catches problems with your own key and quota.
More in this series
Get new guides by email
Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.
Keep reading
- How-to · Monitoring · APIsHow to configure gRPC health checkingLearn how to implement and configure gRPC health checking for reliable service discovery and load balancing: server status, Kubernetes probes, client-side health checks, Envoy, cloud load balancers and Consul.November 7, 2026 · 7 min read
- How-to · Servers · MonitoringHow to monitor CPU, memory and disk usage on a Linux serverCheck CPU, memory and disk on Linux with top, free and df, learn which numbers actually matter, pick sensible alert limits, and get alerted before a server runs out.November 4, 2026 · 8 min read