Surface Vendor Outages in Your Incident.io Workflow

IsDown monitors 6020+ vendor status pages and creates incidents in Incident.io automatically with full context. Your team stops wasting triage time on outages they didn't cause and can't fix.

Start Free Trial Book a Demo

14-day free trial No credit card required 5-minute setup

Very happy with isDown. Setting up and managing the monitoring is straightforward. The customer support team has been excellent, always quick to answer questions and provide assistance.
I definitely recommend IsDown.

Laurent D., Lead SRE & Platform

Previously we had multiple different channels to observe statuses of the services we depended on. But with IsDown I just had to select which services I need to monitor.

Ishan K., DevOps Engineer

IsDown + Incident.io

Vendor Outages, Visible in Your Incident Workflow

IsDown feeds third-party incidents from 6020+ services directly into Incident.io with full context, so your team can triage faster and build better postmortems.

Instant Context

Vendor context from the first minute

When AWS or GitHub has an issue, an Incident.io incident is created automatically with affected components, start time, and severity. Your team has context before they open their laptops.

Automatic incident creation with full vendor details
Affected components, severity, and start time included
Direct links to vendor status pages

Faster Triage

Stop misdirected triage

30% of incidents are caused by vendors. Without vendor visibility, your team spends 20-40 minutes ruling out their own code before checking status pages. IsDown eliminates that lag.

Vendor incidents surface alongside internal alerts
Skip the "is it us or them?" investigation
Triage the right problem from minute one

Postmortems

Accurate postmortem timelines

Every vendor incident includes exact timestamps and affected services. When you write the postmortem in Incident.io, vendor data is already in the timeline. No manual reconstruction needed.

Exact timestamps for vendor incident start and resolution
Affected services and regions tracked automatically
Full vendor timeline in your postmortem data

Auto-Resolve

Auto-resolve when vendors recover

Incidents created by IsDown automatically resolve in Incident.io when the vendor confirms recovery. Your incident timeline closes cleanly without manual intervention.

Automatic resolution when vendors recover
Clean incident timelines with no stale incidents
Zero manual work for vendor incident lifecycle

Simple Setup

How it works with Incident.io

Get started in minutes. Three steps to surface vendor outages in your incident workflow.

Step 01

Pick the vendors you rely on

Select from our 6020+ supported status pages and choose the services critical to your business. Don't see what you need? Let us know and we'll add it ASAP.

Step 02

Connect your Incident.io workspace

Enter your Incident.io webhook URL and API token, then select which teams and services should receive alerts. Incidents are routed to the right teams automatically.

Step 03

Get incidents when vendors go down

IsDown monitors your services continuously. When we detect an incident, Incident.io gets a full incident with affected providers, regions, severity, and every status update as a comment.

Setup takes less than 2 minutes. Try it free.

Start Free Trial

14-day free trial • No credit card required • No code required

Why IsDown + Incident.io

Stop Debugging Vendor Problems as If They're Yours

Without IsDown

Your on-call spends 20-40 minutes debugging before someone thinks to check a vendor status page.
Vendor outages are invisible in Incident.io. Internal incidents pile up while the actual cause is external.
Postmortem timelines are incomplete. You know when your service degraded, but not when the vendor incident started.

With IsDown + Incident.io

Vendor incidents appear automatically in Incident.io.
Your team knows it's a vendor issue from minute one.
Postmortems include full vendor timeline data.
Vendor incidents auto-resolve when the vendor recovers.

Start Free Trial

14-day free trial · No credit card required

Use Cases

How engineering teams use IsDown + Incident.io

Vendor outage context in the incident workflow your team already uses.

SRE Teams

Know it's a vendor issue before you start debugging

Your on-call is paged for elevated error rates. Before spending 20 minutes debugging, Incident.io already has an open incident: "AWS us-east-1 degradation detected by IsDown." You triage the right thing immediately.

Platform Teams

Complete operational health including vendors

You depend on 40+ SaaS tools. IsDown feeds all third-party incidents into Incident.io, each with full context, so your team has a complete picture of operational health including vendors.

Post-Incident Review

Vendor data already in the incident timeline

After an incident, your team reviews what happened in Incident.io. IsDown's vendor data is already in the timeline. Exact timestamps for when Stripe started degrading, correlated with your own service impact.

Frequently Asked Questions

How is IsDown different from Incident.io's existing integrations?

Incident.io's integrations alert you to problems in your own infrastructure (via PagerDuty, Datadog, etc.). IsDown monitors your vendors' infrastructure and creates Incident.io incidents when they have issues. It's the third-party blind spot that most incident management setups miss.

Will vendor incidents clutter my Incident.io workflow?

You control which vendors and severity levels create Incident.io incidents. Most teams monitor 10-30 critical vendors and route only high-severity issues to Incident.io. Lower severity degradations can go to Slack instead.

How does the IsDown and Incident.io integration work?

When IsDown detects a status change in your monitored services, it automatically creates or updates incidents in Incident.io with full context, including affected providers, regions, and status updates. Every vendor update appears as a comment in the incident, maintaining a complete timeline.

How do I set up the integration?

After signing up, go to your IsDown dashboard, then Alerts & Integrations, then Add Incident.io. Enter your webhook URL and API token, select which teams and services should receive alerts, and you're set. Takes less than 2 minutes.

Which services does IsDown monitor?

IsDown monitors 6020+ services including AWS, Azure, GCP, Stripe, GitHub, Salesforce, Datadog, and more. If a service has a public status page, we likely monitor it.

How are incidents resolved in Incident.io?

Incidents are automatically resolved when the vendor's status page indicates the service has returned to normal operation. Your incident timeline stays in sync with the actual service status without requiring manual intervention.

How quickly will I be notified of outages?

IsDown monitors status pages continuously and creates Incident.io incidents within seconds of detecting a change. You'll know about vendor issues as soon as they're reported.

Start monitoring third-party vendors in Incident.io

Start Free Trial

14-day free trial • No credit card required • No code required