What is third-party service monitoring?
Modern apps are built on other companies' services: a cloud provider, a database host, a payment processor, an email API, a CDN. When one of them has an outage, your app breaks in ways your own checks may not explain, and your customers notice first.
Third-party service monitoring watches each provider's official status page and treats it like any other monitor. When the provider reports an outage in what you use, an incident opens and your team is alerted on Slack, SMS, email or wherever your alerts go.
Watch the parts you depend on
Big providers have hundreds of components and some of them are always in trouble somewhere. You can narrow a monitor to the parts you use: Supabase Postgres in eu-west-1, AWS in us-east-1, Google Cloud Run in europe-west1, or Stripe's API but not its dashboard.
Watching a whole service goes by the incidents the provider declares, so one rerouted data center doesn't page you. You choose whether to be alerted on outages only, or on degraded performance as well. Announced maintenance never alerts.
Find your dependencies automatically
Enter your domain and Spot Downtime looks at its nameservers, DNS records, mail and SPF setup, response headers and the scripts its pages load. That reveals hosting such as Vercel, Netlify or AWS, CDNs like Cloudflare, email senders like SendGrid or Google Workspace, and front-end services like Stripe, Supabase or Sentry.
Pick what was found, add the backend services your servers call by hand, and add them all in one go. Each service counts as one monitor on your plan.

