How it works
During an investigation, the system:- Works out which third-party dependencies are relevant, from the incident’s context — the alert, the error, the discussion.
- Matches them against the third-party services it monitors.
- Builds an outage timeline for each match within your incident’s window.
- Surfaces any outage that could plausibly explain the incident as a finding — with timing, like “AWS us-east-1 went down 3 minutes before this incident started.”
What’s covered
We continuously monitor the health of around 150 widely-used providers in the background — cloud platforms (AWS, Google Cloud, Azure), source control (GitHub, GitLab), observability tools (Datadog, Grafana, Sentry), communication and SaaS platforms (Slack, Zoom), payment and messaging providers (Stripe, Twilio), and AI providers, among others. Because that history is already being tracked, the moment your incident starts an investigation can look back over exactly what each provider was doing, with no lag and nothing to wire up.Setup
There’s nothing to set up. This works automatically for every investigation, with no configuration.The list of monitored providers is maintained by incident.io and shared across all customers — these are services many
teams depend on, so we monitor them centrally. You can’t currently add your own services to the list. If there’s a
provider you’d like covered, let us know.
Related
How investigations work
How a provider outage becomes a finding.