Incident management that keeps updates clear under pressure

Built for teams that want incident communication tied directly to monitoring and status pages.

Create incidents in seconds, keep your status page accurate as the situation changes, and notify subscribers across every channel without scrambling during an outage.

Manage incidents Manage incidents arrow Start Managing Incidents Free

14-day free trial • No credit card required

No Cookies European Infrastructure GDPR-Ready All-in-One Stack
Communication

Keep Users Informed

Transparency builds trust. Keep your users in the loop during service disruptions.

  • Live Incident Timeline Post real-time updates as the situation evolves. Choose from simple, structured, or technical formats — the public timeline stays in sync automatically.
  • Scheduled Maintenance Plan ahead with maintenance windows that appear on your status page and notify subscribers before work begins.
  • Quick Presets & Templates Jump-start with built-in presets (API Down, Degraded, Maintenance) or save your own templates for fast, consistent communication every time.
  • Task Checklists Track response work with structured task lists. A built-in library covers notify, triage, mitigate, and postmortem steps so nothing gets missed.
  • Response Roles & On-Call Assign an Incident Commander, Comms lead, and Investigator. Wire incidents to on-call schedules for automatic escalation and acknowledgement.
  • Postmortems & Runbooks Attach a structured postmortem (summary, root cause, remediation, timeline) and link runbooks directly to incidents for future reference.
Setting a status update during an incident
How incident management works

From first alert to resolved incident

StatusPage.me gives you a simple workflow to capture, update and close incidents while keeping customers and teammates aligned.

Step 1
Create or auto-create an incident

Open a new incident manually using quick presets (API Down, Degraded, Maintenance) — or let monitors auto-create one when checks start failing. Choose affected components, pick a severity, and you're live in seconds.

Step 2
Post timeline updates

Share what you know as you investigate: acknowledgements, identified root causes and mitigation steps, all added to a clear incident timeline.

Step 3
Resolve & follow up

Mark the incident as resolved, notify subscribers automatically, and keep a permanent record you can reference in reports and postmortems.

Incident management works hand-in-hand with uptime monitors and status pages, so you never have to copy updates between tools.

Need communication playbooks, severity guidance, and postmortem structure? Browse the University incident management guides.

Creating Incidents Incident Templates Scheduling Maintenance
Incident auto-created from a failing monitor
Monitor-driven incidents

Incidents that start and end with your monitors

No copy-paste between tools. When a monitor starts failing, an incident opens automatically — and when it recovers, the incident resolves itself.

  • Auto-create on failure Configure any monitor to open an incident the moment checks start failing — even if nobody is at the keyboard.
  • Auto-resolve on recovery When your monitor comes back up, the incident closes and subscribers are notified automatically — no manual cleanup required.
  • Status page stays accurate Affected components are updated the moment an incident opens, so your public status page always reflects what monitors are seeing.
Incident FAQ

Common questions about incidents and maintenance

A quick overview of how incidents, maintenance windows and notifications work in StatusPage.me.

Yes. You can configure monitors to auto-create incidents when uptime checks fail. This keeps your status page accurate even if nobody is at the keyboard the moment something goes wrong.

Incidents are unplanned disruptions, while maintenance windows are planned work with a known start and end time. Both appear on your status page, but maintenance can be announced in advance to reduce surprise.

StatusPage.me can notify subscribers via email and send updates to Discord, Slack, Telegram and custom webhooks. You can choose which channels to enable per project.

You control which incident state changes send notifications. For example, you can notify on creation, major updates and resolution while keeping minor internal notes out of subscriber inboxes.

Yes. Once an incident is resolved, you can attach a postmortem with a structured root-cause analysis. Postmortems are kept in your incident history for future reference and are visible to your team only — not published on the public status page. If you want a reusable process, the University incident management hub covers severity design, update cadence, templates, and postmortem workflows.

Yes. Incidents support assignable task checklists so different team members can own specific steps during the response. All activity is timestamped in the incident timeline, giving the whole team a shared view of what’s happening and what’s been done.

Ready to manage incidents with confidence?

Set up your first status page, connect your monitors, and keep customers informed automatically — in minutes.

Start Free Trial Read Incident Guide
14-day free trial No credit card required Auto-create from monitors