I’ve been thinking about a simple but painful problem:
When something breaks in production, how do you know if the issue is your own app or a third-party service?
Many apps today depend on services like AWS, GitHub, Vercel, Stripe, OpenAI, Anthropic, Cloudflare, Supabase, Firebase, Resend, SendGrid and many others.
If one of them has an outage or degraded performance, users usually do not care whose fault it is.
They just think your app is broken.
I built a small iOS app called StatusWatch to help with this.
It monitors 80+ public status pages and sends push alerts when services go down or degrade.
It is not meant to replace full observability tools.
It is more like a simple dependency health dashboard for developers, indie hackers and small SaaS teams.
The main question it tries to answer is:
“Is one of the services my app depends on having an incident right now?”
I would love feedback from other developers:
- Do you currently monitor third-party status pages?
- Would push alerts be useful?
- Which services should be added?
- Should this stay simple, or also include uptime monitoring?
Website: https://statuswatch.tech
App Store: https://apps.apple.com/us/app/statuswatch-service-status/id6761889971
Top comments (0)