Statusfield LogoStatusfield

For Engineering & DevOps

Your app. Your dependencies. One place to investigate.

Your API returns an error. Your cloud provider reports operational. Check your own responses alongside vendor incidents, route the update to on-call, and watch scheduled work with heartbeat monitoring.

Start free trialSee the workflow

30-day free trial, no card needed · First-time customers

Engineering · Incident context

Illustrative workflow

Vendor report

Cloud API · API requests

Degraded

The provider reports elevated API errors in the region your team uses.

Example notification rule

Degraded → Slack · #platform

Your endpoint

503 response

api.example.com/health

Check history · 21 example checksScale: 620 ms
Earlier checksLatest check: failed
PassedSlowFailed

Two signals to investigate together. A matching vendor incident does not establish the cause of your endpoint failure.

Illustrative workflow with fictional data. Explore the example without changing a workspace or sending notifications.

Spend less time asking where to look.

Suppose your checkout API starts returning errors. Open its recent check results beside the payment provider’s reported status. Give the engineer responding a starting point, while your logs and traces help test the cause.

  1. 1

    Watch your dependencies and endpoints

    Choose the payment-provider components you use and add your public API URL. Set expected status, latency and response-body rules for the endpoint.

  2. 2

    Route the update to the owner

    Send the status changes you care about to the right channel. Send major outages to on-call and selected updates to chat.

  3. 3

    Verify the recovery

    Review the vendor’s update and your endpoint results, then check the application workflow before closing the incident.

The dependencies in your stack

Examples from the 7,000+-service catalog.

Explore the catalog

Component and regional coverage varies by vendor.

Keep your application monitoring in the picture.

A vendor report adds dependency context. An endpoint check tells you how a public URL responds. Your logs, traces and application checks explain what happens inside your service.

An HTTP response does not verify a complete login or checkout. For cron jobs, syncs and backups, send a heartbeat after successful work so a missing check-in becomes visible. Heartbeat monitoring is available with legacy Free plans, paid plans and eligible trials.

Explore heartbeats

Frequently Asked Questions

Monitoring, setup and sharing for engineering & devops.

How can I find out when a cron job or backup stops running?
Use a heartbeat monitor. Set how often the job should finish and how much extra time to allow, then add its check-in URL after your job’s success checks. After the first check-in starts monitoring, a missed deadline can trigger your configured alerts. Send /fail to report a known failure without waiting for the deadline. Your code must verify the work: a received ping alone does not prove a usable backup or correct data.
Can my website be down while my hosting provider reports operational?
Yes. A provider’s status page may be green while your own URL fails because of an application error, account restriction or configuration issue. An uptime monitor requests your public HTTPS URL and checks its response time, expected status code or range, and optional text or JSON body rules. This can surface a failing response independently of vendor reports; it does not identify the cause or verify a complete login or checkout.
Can we check our own endpoints and background jobs?
Add publicly reachable HTTPS URLs to check their responses alongside vendor status. You can also monitor domain and SSL/TLS expiry. Heartbeat monitoring watches expected job signals. Heartbeat monitoring is available with legacy Free plans, paid plans and eligible trials. Uptime checks do not test complete authenticated workflows.
How is this different from the vendor’s own status page?
Statusfield brings updates from 7,000+ services into one view. Manage component choices and alert channels across vendors instead of on each page separately.
Can I monitor a single component like GitHub Actions?
Yes. Open the service’s Overview from Monitors. Under Monitored components, choose “Add or remove” (or “Pick components” for an empty selection), select the components you use, and save. Available components depend on the provider.
Does it tell me when the outage is over?
Configured recovery notifications tell you when Statusfield detects that the vendor reports operational again. Confirm your own application has recovered before closing your incident.
How do I monitor all my dependencies for outages in one place?
Pick services from the catalog and connect your alert channels. Your dashboard shows reported problems by status. API and MCP access are available on supported plans.
Can we check delivery before a real outage?
Yes. Send a labeled test alert during setup or test a configured destination from Integrations. Check that the message arrives in the intended inbox or channel. A test verifies delivery; it is not a real vendor incident.
Will this detect problems before the vendor reports them?
The vendor-monitoring workflow follows official reported status. A provider may not have acknowledged a problem yet, and some issues affect only your account or region. Keep your own application monitoring alongside it.
Why do you recommend Pro for engineering and IT teams?
Pro is our recommendation for small engineering and IT teams coordinating checks, on-call alerts and incident reviews. At $60/month, it combines 40 monitor units, 10 alert destinations and 4 workspace seats with PagerDuty routing, API and MCP access, reports and priority support. Share monitoring responsibility, send relevant changes to chat or on-call, and bring recorded history into your reviews. Reports require at least 30 days of workspace monitoring history. Basic covers a small email-only setup; Starter adds chat and API/MCP access. Team expands capacity to 90 units and 8 seats.
I have more questions. Where can I get more information?
Email support@statusfield.com with your questions. We can help you understand component coverage, routing rules, integrations, and which plan fits your team.
I want a demo. Can I schedule time?
Yes. Schedule a demo to walk through Statusfield and discuss your team’s monitoring and routing needs.

Still have questions? Email us at support@statusfield.com or set up a meeting. All emails are read by humans.

Build your workflow

The products behind the process.

Choose the monitoring and workspace features that fit how your team works.

Give your next investigation a clearer starting point.

Choose your monitors, connect your destinations and test the setup with your team.

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

Start free trial