Stay up to date

Tell the full story with your incident timeline

On-call is now available to our Microsoft Teams users.

Incident trends will proactively highlight what’s important in your incident data so you know where to dig in further. Figure out exactly which parts of your incident response process need attention without sifting through the data yourself.

We've added 25 new workflow templates, and also introduced manually triggered workflows

Escalate to anyone, from anywhere, whether you have an incident or not.

It’s now even easier to get started with policies, and get a configuration you’re confident in the first time round.

Introducing incident.io for Microsoft Teams

Simplify your monthly and quarterly reporting to level up your incident management

We’ve now made our integration even richer, showing when a call is active, who’s on the call, and when the call is finished in the channel and on the incident timeline.

We've brought the magic and ease of suggested summaries and follow-ups into the dashboard

A completely new way to look at your incidents, the Kanban view!

It’s difficult to ensure that follow-up actions, post-mortems, and debriefs are completed on time, and it often takes hours of manual work to keep track of everything. Policies are flexible ways to set rules to ensure they’re completed on time and let you know if they’re not.

We’ve had a busy couple weeks improving incident.io On-call. While we like to ship big features, we’ve lately taken some time to sweat the details.

Tracking your incident follow-ups is now even easier.

Get started quickly with our new onboarding wizards

Arranging cover for holidays has just become a lot easier: you can now bring public and personal holidays in incident.io to view them directly in your On-call schedules and easily arrange cover!

You can now quickly populate your Catalog by using AI to suggest likely values

Upgrades to our escalation paths

Manage large scale incidents by breaking the work down into streams with their own Slack channels and calls.

On-call schedules, overrides and cover-requests are now available on iOS and Android.

You can now choose whether or not to exclude weekends from your policies

We're bringing your teams to Insights, letting you filter and split your data by team.

You can now create escalation paths with priorities and/or working hours!

'OR' conditions level up configurability across the entire platform.

All of the components powering our most used and loved features have been redesigned from the ground up.

We've improved our UX and updated our Insights to include Post-incident data

We now support terraforming your workflows

We now show incidents in Catalog, so it’s much easier to gain an understanding about what’s happening across your company, directly from Catalog!

This week, we’ve been doing a ‘backlog crush’ where we work through a long list of bug fixes, bits of polish and small feature requests.

You can now create and manage your On-call Schedules through the incident.io API

You can now configure future changes to an On-call schedule with the confidence of knowing exactly how your schedule will look after the change.

This week, we've dramatically expanded our support for syncing objects from Salesforce to our Catalog

We have built a native incident.io Atlassian app that allows you to install incident.io directly into Jira and Confluence.

Since launching alerts, we now support over 10 additional alert sources to help you achieve your specific workflows - here’s an overview of some of our most used integrations.

Unlock powerful automations by modelling your teams in Catalog

Export follow-ups and link MRs to GitLab

Get alerts when your status page experiences a spike in page views.

We've been hard at work building On-call, which we launched last week. Here's a sneak peek into the last few weeks of work that we weren't able to talk about before!

Building up your Catalog just got a lot easier

Level up your post-incident flow! We'll now send reminders when tasks are due and let you dynamically choose which flow to enter.

You can now write pre-defined updates that responders can use when updating your Status page

We’ve introduced the ability to pause your incidents! ⏸️

Streamlining your tasks and follow-ups

We’ve added new functionality which allows you to inspect your alerts, giving you a better understanding of what’s going on under the hood for a particular alert.

This week, we’ve been doing a ‘backlog crush’ where we work through a long list of bug fixes, bits of polish and small feature requests.

Users across are now a first-class citizen in our Catalog, unlocking many new options in your automations.

You can now create custom timeline events, postmortem tasks for giving shoutouts, and configure your suggested summaries.

Auto-create incidents with our new Alerts feature.

Get hands-on with Assistant, our new AI feature aimed at simplifying historical incident analysis, by exploring patterns, spotting anomalies, and building insightful charts.

Easily sync your Salesforce accounts with the Catalog to keep track of affected customers, account owners, and other key customer information.

✨ Never forget to create a follow-up ever again! At the end of an incident, we will suggest follow-ups that you have mentioned within the incident channel, helping you learn and improve from your incidents.

Our customers love our Insights product, so we’ve spent some time to see how else we could improve the experience. This week, we are releasing some improvements to Insights that should make everyone's lives a bit easier.

Different teams have different incident response processes that don't always fit into the same series of statuses. You can now configure different incident lifecycles for different incident types. Additionally, each lifecycle can use a different post-incident flow, so you can customise the set of tasks responders should complete after an incident is resolved.

Add conditions to incident types so you can control which users in your organisation can declare or accept them.

Helping you quickly link two incidents together

We’ve spent the last couple of weeks improving our Slack experience, making sure we present the information you need in an easy-to-digest format.

Get a sneak peek of some of the initial pieces of work we’ve done to make the Slack experience feel a little smoother.

It's now easier to keep the summary up to date using AI

Use rich text to write better Incident summaries and updates.

Use configurable forms to streamline the incident response process and tailor it to your organisation.

Create dedicated, authenticated status pages for your most valued customers, and only share updates to the customers that are impacted.

You can now export your incident data using a Singer tap

You can now connect multiple Jira instances to your incident.io account

Simplify your incident follow-up workflow with automatic exports to Jira and Linear.

We've been busy making small improvements all around the app, adding some new features and fixing lots of bugs.

We’re delighted to announce we’ve shipped Status Page sub-pages. With sub-pages, we'll allow you to create multiple connected status pages and communicate with various different audiences through them.

We know how important it is that your incident announcement posts contain the information that matters to you, so we now let you configure the post from the revamped announcement settings page!

We know that it’s important that you can depend on Incident.io, even when other tools you rely on are experiencing issues. This week we’ve shipped two new features that make Incident.io even more resilient to Slack issues.

We've made a number of updates including providing the ability to copy timestamps to your clipboard to speed up the process of setting additional timestamps, collapsing the auto set timestamps to streamline the modal, and timestamps can now be input in ISO8601 format, in any timezone.

Encourage responders to provide excellent summaries

Remind responders to take actions, on a schedule you define.

Tell us who should be invited to your debrief and whether you'd like any policies to apply.

Following the release of internal status pages, we're now adding Slack and email subscriptions to them, allowing you to always be up-to-date with incidents in your organisation.

We've given Workflows a complete overhaul, introducing new ways to view, create and edit your workflows more intuitively.

We’re delighted to share that we now support internal status pages. With Status Pages, we helped get timely and clear updates during an incidents to customers. We now think it’s time to solve this for internal stakeholders. From Customer Success Managers to Executives, we think it’s critical that everyone in your organisation has an understanding of what’s going on.

You can now link a debrief event to your incident, so everyone knows when it is

Additions to users, catalog-based custom fields, actions and follow-ups on the public API.

Follow-up export templates define how follow-ups should be exported to your preferred issue tracker

Announcing incident.io Catalog.

Define the steps you want to take to learn from your incidents, and configure the kinds of incidents you want to learn from.

You can now use tables and lists within your postmortem templates.

Automatically publish updates to your status page.

Link internal and status page incidents for easier navigation.

Declare incidents on your status page after the fact, and dynamically set custom fields from an incident trigger.

Use predefined templates for your status page updates and let users subscribe to updates directly from Slack — and introducing `/inc cancel`.

Share postmortems within your organization, to share learnings from your incidents.

Subscribe to selected components in Status Pages, plus custom field groups.

Use the new handover Slack command to substitute a user into an incident, plus a host of performance improvements for our dashboard.

You can now set default Jira projects and labels for your incident follow-ups.

Announcing incident.io Status Pages.

You can now view and export auditable events for changes made within your incident.io account.

You can now use SCIM to provision users and control permissions.

You can now use our public API to make changes to incidents, such as updating the summary or setting a custom field.

We've been busy working on some smaller features, such as a new 'when you react to an emoji' workflow trigger.

You can now install the incident.io Slack app to multiple Slack workspaces in your Slack Enterprise Grid.

You can now control which permissions are granted to users.

You'll now see a timeline entry for each update to a follow-up or action.

We've added the ability to receive updates about your organization's incident via SMS.

Export your postmortems to Google Docs.

Use webhooks to notify external systems when something happens in incident.io.

Keep all the context in one place by adding rich descriptions to your follow-ups.

Focus on what really matters by letting us auto-create incidents based on Opsgenie alerts.

See your Datadog monitors right inside your incident channels with our new Datadog integration.

Respond to incidents at the speed of thought with a powerful keyboard driven CMD+K menu.

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 organization’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 organization.

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 organization

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 organizational rules for following-up on incidents.

Connect incident.io to Zendesk to keep your organization 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 organization 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!