StatusEagle
Incident management

Incident management that starts with the facts

When a failure is confirmed, StatusEagle opens an incident that already knows what failed, where, since when, and what error it saw. Your team picks it up from there, and your status page can tell customers at the same time.

INC · checkout-api
Live check snapshot
Active
StatusInvestigating
CauseHTTP 502 Bad Gateway
Confirmed from3 of 3 locations
Started14:03 UTC · 6 min
Acknowledged bySara

Example check · demo data

In brief

Incident management is the process of detecting, recording, responding to and communicating about service disruptions. In StatusEagle, incidents are opened automatically from verified monitor failures and carry the evidence your team needs to respond.

1

The life of a StatusEagle incident

Opened automatically when a monitor failure is confirmed from multiple locations, with the error it saw: “Connection refused”, “HTTP 502”, “keyword missing”, “certificate expired”.
Alerted to the right people through their channels.
Acknowledged by whoever takes it, moving it from open to investigating so everyone knows it has an owner.
Communicated on your status page, with updates as you learn more.
Resolved automatically when checks pass again, with total duration recorded.
2

Maintenance windows

Planned work shouldn’t page anyone or count against your uptime. Schedule a maintenance window, and it appears on your status page in advance; monitors covered by it don’t raise incidents during the window.

3

A lightweight incident process for small teams

You don’t need a war room. You need these four things decided in advance:

Eagle Intelligence (early access) drafts incident summaries, status updates and post-incident reports from the incident’s own evidence, for a person to review. See how it works.

Who responds. Route alerts per monitor to the person who owns that service.
Who communicates. One person posts status updates, so engineers can focus on the fix.
When to update. First post within about 10 minutes, then on a promised schedule. See our status page guidance.
What to write up. For anything customer-facing: timeline, impact, cause, and one change to prevent it.
4

Incidents in your own tools

The REST API returns ongoing incidents, so you can show them on internal dashboards or block a deploy while something is on fire:

curl https://api.statuseagle.com/v1/incidents/ongoing \ -H "Authorization: Bearer $STATUSEAGLE_API_KEY"See the API reference.

Configuration / Request snippet
curl https://api.statuseagle.com/v1/incidents/ongoing \
  -H "Authorization: Bearer $STATUSEAGLE_API_KEY"
5

What it is, and isn’t

StatusEagle incident management covers the path from verified alert to resolved incident and customer update. It doesn’t include on-call rotations or escalation policies. Teams that need those typically pair StatusEagle with a dedicated on-call tool through webhooks.

COMPLEMENTARY CHECKS

Related monitoring

Pair these monitoring checks to ensure complete stack coverage.

FAQ

Frequently asked questions

Still deciding? Start monitoring free and verify your first service in ~2 minutes.

The process of detecting, responding to, communicating about and learning from service disruptions.

GET STARTED IN MINUTES

Your first monitor takes about two minutes.

Free plan: 10 monitors, 3 locations, 1 status page. No credit card.