Incident Room
One room per incident. Every second on record.
The moment a monitor goes down, an incident opens with its own timeline and Slack channel. Checks, pages, acknowledgements, deploys and status updates are written down for you, so the postmortem is half done before the fix ships.
- 20:41:12monitorCheckout API down from 3 regions · HTTP 502
- 20:41:15pageArjun paged by call and push
- 20:41:40aiLikely cause: deploy v4.18.2 changed DB pool size
- 20:41:52roleArjun took Incident Commander
- 20:42:05statusStatus page: Investigating
- 20:43:30deployRollback to v4.18.1 started
- 20:44:10monitorRecovered in all regions · 210 ms
Incident timeline recorded automatically
How it works
Set up in four beats.
- 01
Incident opens itself
A confirmed failure creates the incident, sets severity and opens a Slack or Teams channel.
- 02
Assign roles
Incident commander, communications lead and responders, each with a clear checklist.
- 03
Work, while it records
Every alert, acknowledgement, deploy, message and status update lands on one timeline.
- 04
Review the postmortem
A draft with impact, timeline, cause and action items is ready when the incident closes.
Capabilities
What you get with Incident Room.
Auto-created incidents
Opened from monitors, alerts from your other tools, or by hand from Slack.
Roles and checklists
Everyone knows who decides, who talks to customers and who fixes.
Severity levels
SEV1 to SEV4 with rules for who is paged and how often customers hear from you.
Live timeline
Machine events and human notes in one ordered record, with exact timestamps.
Channel per incident
A dedicated Slack or Teams channel with the right people already invited.
Customer updates
Publish to your status page from the incident without switching tabs.
Postmortem drafts
Generated from the timeline and editable before anyone sees it.
Action items
Follow-ups pushed to Jira or GitHub Issues with owners and due dates.
MTTA and MTTR
Time to acknowledge and time to recover, tracked per team and per service.
Specifications
The details engineers ask about.
- Chat tools
- Slack, Microsoft Teams
- Ticketing
- Jira, GitHub Issues
- Severity scale
- SEV1 to SEV4, customisable
- Postmortem format
- Impact, timeline, cause, actions, lessons
- Export
- PDF, Markdown, JSON via API
- Availability
- Team and Scale plans
FAQ
Incident Room questions
Do we have to use Slack?
No. Everything works from the web app. Slack and Teams simply let you run the incident from where your team already talks.
Who writes the postmortem?
Your team does. Xuptify prepares a draft from the timeline so you start editing, not typing from memory.
Can we run incidents that are not outages?
Yes. Open an incident by hand for a security review, a data issue or a slow rollout and use the same timeline.
Same pulse
Works together with
60 bpm 10 monitors · 1-minute checks · free, no time limit