LoginSign Up
← Back to all sparks
I

Instatus

INFRA · APIS
Velocity0.0

Instatus has grown from status pages into a Slack-native incident response platform.

status-pageincident-responseslack-nativemonitoringintegrationsmigration
◆Current state
After launching Instatus 2.0 in mid-2025 with monitoring and incident response added to the existing status-page core, the past two quarters have been about polishing the incident lifecycle. The January release was the biggest expansion: full /incident command set in Slack, dedicated per-incident channels, postmortems from chat, and emoji-driven incident creation. Recent months added recurring maintenance windows, third-party status-page aggregation (Statuspage), General Notices, Freshstatus migration, Zapier, Jira, WhatsApp, Resend, and Brevo integrations.
◆Where it's heading
The arc is clear: Instatus is going head-to-head with Atlassian's Statuspage and Better Stack on a single integrated stack — monitoring, incident response, public communication. The Slack-native push is the real differentiator; incident commanders rarely want to leave Slack. Migration tools (Freshstatus) and third-party aggregation (Statuspage import) point at land-and-expand against incumbents.
◆Prediction
Expect on-call and scheduling integrations next, expanded migration tooling for other status-page incumbents (Better Stack, Status.io), AI-powered incident summarization and postmortems, and broader monitoring coverage — likely synthetic and browser checks.

◆Recent moves

  1. 2mo ago

    Recurring maintenance windows and Statuspage aggregation

    Maintenance windows can now repeat daily/weekly/monthly/yearly with auto-start, auto-end, and reminders. Status pages can also aggregate incidents from third-party providers, starting with Atlassian Statuspage. The Statuspage hook is the more interesting move — a wedge for migration conversations.

  2. 3mo ago

    Persistent General Notices on status pages

    Adds General Notices: pinned, persistent announcements on the status page that aren't tied to a specific incident. Useful for policy updates and ongoing scheduled work — a small but commonly-requested gap closed.

  3. 4mo ago

    Freshstatus migration import; Slack incident-channel toggle

    Direct migration import from Freshstatus (incidents, maintenances, subscribers, components, templates), plus an option to stop creating Slack channels for new incidents. Continues the migration-tooling pattern aimed at conversions from incumbents.

  4. 5mo ago

    Slack-native incident response: /incident commands and per-incident channels

    ⚡ SPARK

    Instatus ships a full Slack-native incident response surface — /incident commands, per-incident channels, ack/lead/responder assignment, action items, postmortems, and emoji-triggered incident creation. This is the move that promotes Instatus from status-page tool to incident-response platform.

  5. 6mo ago

    Zapier integration, OR conditions, Workspaces API

    Zapier integration with both trigger and action support, OR conditions in routing rules and monitor assertions, a new Workspaces API, and timezone-based country detection on SMS forms. Solid platform-grade additions that broaden integration reach without changing positioning.

  6. 7mo ago

    Jira Service Management, WhatsApp alerts, Resend, Brevo

    Jira Service Management bidirectional integration (issue → incident, Done → resolved), WhatsApp monitor down-alerts, plus Resend and Brevo as email integrations. Continues the steady integration-breadth strategy across communication channels.