Monitor Your Own Endpoints Alongside Your Dependencies

Statusfield has always been about one thing: knowing when the services you depend on go down, before your users tell you. We aggregate 2,000+ service status pages so you get one dashboard instead of 20 browser tabs.

But there's always been a gap. Your stack doesn't just depend on AWS and GitHub. It also depends on your own services — your app, your APIs, your internal tools. And those don't have public status pages.

Now you can add your own endpoints to the same dashboard.

---

Your Dependencies AND Your Services, One Dashboard

The idea is simple: if your team's incident response starts with "is it us or is it them?", your monitoring dashboard should answer that question in one glance.

Before, Statusfield showed you the "them" part — third-party service status. Now it shows you both:

• Third-party services: AWS, Stripe, GitHub, Vercel, and 2,000+ more
• Your own endpoints: your app's /health endpoint, your internal APIs, your staging environment

Same dashboard. Same alerts. Same notification channels — email, Slack, Discord, webhooks.

---

What Should You Monitor?

This isn't for monitoring random websites. Adding google.com and checking if it returns a 200 doesn't tell you anything useful — a landing page can be up while the actual service is down.

This is for endpoints you control or that return meaningful health information:

• Your app's health check — /health, /api/status, or whatever your readiness probe hits
• Internal APIs — microservices, backend endpoints, admin tools
• Staging and production URLs — catch issues before your users do
• Critical vendor endpoints — if you hit a third-party API directly and need to know it's responding

The key difference: these are URLs where a non-200 response actually means something is wrong.

---

How It Works

1. Go to your monitors page and click Add Custom URL
2. Enter the endpoint URL
3. Done — we check it on every sync cycle

When the endpoint stops responding (or returns a non-200 status), you get notified through whatever channels you already have configured. No separate setup needed.

The endpoint appears in your monitors dashboard alongside all your third-party services. During an incident, you can see at a glance: is GitHub down? Is your API down? Or both?

---

What This Isn't

Worth being explicit: this is not an uptime monitoring tool.

We're not doing multi-region checks, response time tracking, SSL certificate monitoring, or synthetic transactions. If you need deep observability into your own infrastructure, tools like Better Stack, Datadog, or UptimeRobot are purpose-built for that.

Custom endpoint monitoring in Statusfield is for the same question we've always helped answer: is it up or down? It's a health check, not a performance audit. The goal is a complete picture in one place — not replacing specialized tools.

---

The Full Picture

Here's what a typical dashboard looks like now:

Service	Type	Status
AWS US East	Third-party	Operational
GitHub Actions	Third-party	Degraded
Stripe API	Third-party	Operational
api.yourapp.com/health	Your endpoint	Operational
staging.yourapp.com	Your endpoint	Down

One look tells you: GitHub Actions is having issues (not your fault), and your staging environment is down (that's on you). No context-switching between tools.

---

Get Started

Each custom endpoint counts as one monitor toward your plan limit — available on every plan, including Free.

Already on Statusfield? Head to your monitors page and click Add Custom URL to add your first endpoint.

New here? Start monitoring free — two monitors on us, for third-party services, your own endpoints, or both.