openstatus #15: Incident management, right in Slack

No dark-mode styles — this email renders the same in a dark client.

Incident management in Slack, maintenance updates, OAuth for the MCP server, and Monitor Packs.
openstatus Product Update #15
Incident management is here. Declare, debug, and write the post-mortem from Slack or the dashboard.
Hey,
Last time I said on-call was where we’re doubling down. The first piece just shipped: incident management, built for small teams that live in Slack.
It’s included in every plan, no add-on.
What’s Hot 🌶️
Most incidents are spicy by accident. This one’s on purpose.
We teamed up with our friends at Passbolt to make Secret Sauce, a Carolina Reaper hot sauce for anyone whose on-call isn’t spicy enough. Handle with care: it’s hotter than a Friday deploy.
What’s New
Incident Management: Because Slack Threads Suck
Everyone knows where to go. No more scrolling #general for the thread where someone said “looking into it.” One command and the incident gets its own channel and a clear owner.
Stay in Slack and keep fixing. React with 📌 on the messages that matter and they’re saved to the timeline. You don’t have to stop debugging to take notes.
Nothing gets left open. If an incident goes quiet, we nudge the channel. No more incidents still marked “open” three weeks later.
Post-mortems take minutes. We draft one from what already happened in the channel. You review it instead of rebuilding the story from memory on Monday.
Customers only see what you approve. Debug in the open with your team. Your status page changes only when you approve an update.
Not on Slack? You can do everything from the dashboard too: declare an incident, assign a commander, add notes, link a status report, and write the post-mortem. Only the Slack-specific parts, like the dedicated channel and 📌 pinning, need Slack.
Read the launch post →
Maintenance Updates: Keep Users in the Loop
Maintenance windows rarely go exactly to plan. Now you can post progress as it happens (“migration halfway done”, “running 30 minutes over”) and notify subscribers with each update.
Your status page, feeds, and Markdown view show the full timeline, so users don’t have to guess whether you’re still working on it. Existing API and Terraform setups keep working as before.
Read the changelog →
Connect the MCP Server With One Click
No more pasting API keys. Add https://api.openstatus.dev/mcp to Claude, ChatGPT, Cursor, or opencode, pick a workspace and read-only or read & write, and approve. You can see and revoke connected apps in Settings → Integrations.
Read the changelog →
Monitor Packs: Grow Without Changing Plans
Need a few more monitors? Add 10 for $15/month, up to 10 packs on Starter, Pro, or Scale. Settings → Billing → Add-ons.
Read the changelog →
Also worth a look
Response logs in the dashboard . Search, filter, and slice every check a monitor has run.
Introducing @openstatus/health . Health endpoints that tell you which dependency is down, not just that something is.
Four iterations of an incident timeline . How we got the incident timeline right, the fourth time.
Two dates for your calendar:
Sunday, October 25: we’re launching incident management on Product Hunt. An upvote or a comment that day would mean a lot.
Friday, October 30: we’ll be at BDX I/O in Bordeaux. If you’re around, come say hi.
If you try incident management on your next outage, hit reply and tell me what broke (in the product, not your infra).
Thibault
thibault@openstatus.dev
openstatus
Unsubscribe

Accession

nse/openstatus/2026-10-22/4787

From

Thibault Le Ouay Ducasse · thibault@ship.openstatus.dev

Sent

22 October 2026 · 13:00 UTC