Stay up to date

We've added bulk editing support, allowing you to update fields, roles, and more en masse.

Use follow-ups priorities with policies and workflows.

We've added the ability to create incidents in triage. They're a great way to investigate things that look like problems, but require some deeper investigation before promoting them to a live incident.

Making it easy to write workflow steps that send nicely formatted messages.

Making it easy to export follow-ups to the right place in Linear.

A more dynamic and welcoming dashboard for both observers and responders.

You are now able to see who might be experiencing the most disruption when on-call.

We've improved the post-incident flow with a better Notion integration for post-mortems and post-incident notifications.

You can now receive a monthly overview of your organisation’s incident activity. We've also created an integration for Asana, and enabled Opsgenie for our on-call pay calculator.

You are now able to save the filters that affect your insights dashboards as a view, and share them with others in your organisation.

You can now subscribe to incidents via Slack and/or email to receive updates whenever an incident changes.

You can now configure duration metrics that you want to track using incident.io.

You can now choose the bookmarks and quick actions you want to appear when an incident channel is created.

We've revamped the homepage of the incident.io dashboard to give you relevant information at a glance. We've also improved the post-mortem export, with an improved layout and native Confluence integration.

We've released 4 new insights dashboards to help visualise your incident data. You can also now save and share views from the follow-ups page, and allow users to dynamically create custom field options.

Following a consistent process after an incident closes is key to your team's efforts to improve resilience.

Write expressions to change parts of a workflow based on a set of conditions.

Use the new dashboard to explore your follow-ups, apply bulk actions and send reminders.

Connect incident.io to Jira Cloud to auto-export incidents as Jira tickets

You can configure Custom Statuses and Timestamps to perfectly suit you and your organisation

You can now page users, teams and policies using Splunk On-Call, all without leaving Slack

You can declare an incident after it's happened. You can also create post-mortem policies, and keep track of compliance using weekly reports.

Now you can use your statuspage templates from inside incidents. Also, you can now rename incident leads.

Use policies to encode your organisational rules for following-up on incidents.

Connect incident.io to Zendesk to keep your organisation in sync.

We've just launched timeline curation, giving you the power to tell the story of your incident and find insights from the key events.

You can now choose a timezone for your post-mortem document to be generated in.

We've been working on improving our rich text editor, so you can easily send formatted emails.

We've been working on reducing noise coming from us, allowing you to streamline your incident response and see the stuff that really matters.

We've been working various bits of polish, including giving more options when templating workflow messages and post-mortems.

You can now calculate on-call pay using incident.io, as well as three new workflow triggers.

You can now be more specific about the incidents you want your workflows to run on

We've loved seeing you all!

Workflows can now be set to run with a delay after the trigger happens

Use attachments to keep track of related GitHub Pull Requests and more

Spend more time collaborating and less time moving between places with incident auto-create

We're releasing our API today, and can't wait to see what you'll build with it

Now you can harness the power of workflows and private incidents, together!

We now sync Jira Cloud issue updates immediately.

We now show timestamps in both UTC and local time.

Now you can filter incidents in the follow-ups page.

Custom fields support freeform text, numbers and URL links

We now have account roles, so you can control who can manage settings

You can now connect incident.io to Jira Server

We're giving you better insights so you can spot patterns in incident response

Use incident.io to manage sensitive incidents.

We'll auto-archive incident channels after 7, 14 or 28 days.

New year, new workflows: automated emails & auto-assign roles

Use /inc tutorial to learn the basic of incident.io

Supercharge your incident workflows with variables!

You can now encode your processes into incident.io using Workflows

Integrate with Zoom to create call links for each incident

You can now close incidents from the dashboard

Your team can stay informed about the things that matter to them

We've supercharged incident filtering!

You can now create incidents directly from the dashboard, with inc.new!

Introducing decision flows: an easier and more transparent way to make decisions during incidents.

You can now configure incident.io to create a Jira ticket whenever an incident reaches a certain severity.

Upgraded support for exporting follow-ups to Jira, and initial incident message and invites

You can now export data about incidents and follow ups to a CSV, to help with analysis and reporting

Create follow-up actions for tasks that need tracking post-incident

We've added filtering so you can more easily find the incidents you're interested in

You can now define custom fields on your incidents, and have incident.io collect it for you before, during or after an incident!

On top of the usual collection product improvements, this week we've also shipped our new blog.

We've made it even easier for your whole organisation to onboard with incident.io

Instead of doing just one, we made lots of smaller improvements to the product.

We've tidied up incident actions, to help you coordinate and collaborate in an incident

We've added Intercom to our product to make support and feedback easy

We've introduced "incident updates" to make it faster and easier than ever to keep everyone in the loop

We're holed up in the Wye Valley for a concentrated week of thinking, planning and building.

You can now customise what you include in your postmortem templates, making it easier to bring what you already have into incident.io

You can now define custom incident roles, to make it even clear who's taking care of what.

We've moved over to Slash commands and spruced up our interface

We now gather feedback on your behalf, making it easier to improve your incident response process

Get up to speed and let others know if you're here to help with new messages when you join an incident.

Use test incidents to practice with incident.io and run game days

We've onboarded a lot of new faces recently, so we've been spending some time ensuring we make a good first impression!

You can now control your public statuspage in Slack, using incident.io

Export your incident actions directly into Clubhouse

This week we've been addressing an obvious gap in the product - incident states!

Rather than storing generic 'document' links, we now explicitly links to post mortems

Export your incident actions directly into GitHub Issues

Page users from Slack using our Opsgenie integration

You can now export incident actions straight into Linear, and track them with incident.io

From today, you can manage actions in the dashboard, export them to Jira and finally keep track of what was actually followed up post-incident.

Today we're releasing the first version of Insights, to help you extract even more value from your incident data.

We re-designed how the bot communicates to make it easier to scan incident channels

You can now quickly list all important links shared during an incident, no more rummaging through slack messages!

You can now page users and rotations directly in Slack, and we'll stream notifications and acknowledgements into the channel as they happen so you know who's on their way.

We launched our public product roadmap.

Lots of smaller updates this week while we onboarded our first 4 customers and focussed on talking to them, and figuring out what to build next!

We launched to the world!