# Introducing Investigations, powered by Nexus.

DevFeed: [Introducing Investigations, powered by Nexus.](<https://devfeed.tech/articles/introducing-investigations-powered-by-nexus-11855.md>)

Original publisher: [Read original article](<https://incident.io/blog/introducing-investigations-powered-by-nexus>)

Author: Pete Hamilton

Published: 2026-08-05T13:48:00Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Incident response](<https://devfeed.tech/topics/incident-response.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [reasoning](<https://devfeed.tech/tags/reasoning.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

## AI overview

The article introduces Investigations, an incident.io feature powered by Nexus that autonomously investigates and diagnoses incidents alongside human responders. It analyzes context such as postmortems, logs, metrics, deployments, and dependencies, then provides hypotheses, evidence, next steps, and visible reasoning throughout incident resolution.

## Source excerpt

Today we're launching Investigations: agentic root cause analysis that starts the moment you're paged, figures out what broke and why, and works with your team through to resolution. Here's what we built, what's powering it, and why it took some time to get right.