incident.io

incident.io's Investigations feature now messages responders as soon as early checks produce concrete, new, and actionable evidence, instead of waiting for the full hypothesis-and-review pipeline to finish, cutting median time to an accurate channel update from 6.7 to 3 minutes and raising the share of incidents with an accurate update within 5 minutes from 8% to 68%. This is a non-breaking behavioral change validated through backtesting and gradual rollout, so no action is required from existing users.

Matters for: This matters for on-call and incident response teams running alert-driven investigations where faster, evidence-based updates reduce time-to-resolution during live incidents.

You can now trigger workflows directly from alert creation or resolution, store and rotate sensitive strings as secrets to reference in webhook headers instead of plaintext, and sign outgoing webhook requests so receivers can verify they came from incident.io; the webhook step editor also now provides JSON syntax highlighting and validation. None of this is breaking, so existing workflows continue to run unchanged.

Matters for: Teams that connect incident.io to external tools or internal systems via webhooks, especially those needing to keep third-party systems in sync on alert state changes.

You can now group alerts and escalate on them without creating an incident, including grouping private alerts, attaching a group to an existing incident, choosing escalation behavior for new alerts joining a group, and picking fixed vs rolling time windows; all of this is configurable via Terraform and the updated alert route API. Existing customers who already group alerts into incidents will be migrated automatically over a couple of steps, and customers not yet using grouping will have it turned on within a few days, with no action required during migration.

Matters for: Relevant to on-call and SRE teams managing high alert volumes through incident.io's Terraform provider or alert route API.