When Vendors Go Down, PagerDuty Knows First

IsDown monitors 6020+ vendor status pages and creates PagerDuty incidents automatically. Your on-call team knows it's a vendor issue, not your code, before they spend 30 minutes debugging the wrong thing.

Start Free Trial Book a Demo

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

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

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

IsDown + PagerDuty

Third-Party Visibility for Your On-Call Team

Stop debugging your own code when the problem is a vendor. IsDown fills the third-party blind spot in PagerDuty.

Instant Context

Know it's a vendor, not your code

IsDown creates a PagerDuty incident the moment a vendor reports an issue. Your on-call engineer has context before they even open their laptop.

Automatic PagerDuty incidents for vendor outages
Full context: affected services, regions, severity
Reduce MTTD for third-party issues

PagerDuty incident created by IsDown showing vendor outage details

Unified Queue

All your vendor incidents in one queue

AWS, GitHub, Stripe, Salesforce. All third-party incidents flow into your existing PagerDuty setup, alongside your own infrastructure alerts.

Works with your existing escalation policies
Route vendor alerts to the right on-call team
Monitor 6020+ services from one integration

PagerDuty service showing IsDown vendor incidents

Early Detection

Earlier than the vendor admits

IsDown detects outages through independent monitoring. Often before vendors update their own status pages. You get notified first.

Detection before official status page updates
Independent monitoring, not just scraping
Alert your team 20-45 minutes earlier

Auto-Resolve

Auto-resolve when they recover

PagerDuty incidents created by IsDown automatically resolve when the vendor confirms recovery. No manual cleanup.

Automatic incident resolution on recovery
No stale incidents cluttering your queue
Full incident timeline preserved

Simple Setup

How it works with PagerDuty

Get started in minutes. Three steps to add third-party outage detection to your PagerDuty workflow.

Step 01

Pick the vendors you rely on

Select from our 6020+ supported status pages and choose the services critical to your business. AWS, Stripe, GitHub, Salesforce, and thousands more.

Step 02

Connect your PagerDuty account

Add your PagerDuty integration key and select the service where you want to receive vendor incidents. The setup takes less than 2 minutes. No coding required.

Step 03

Get PagerDuty incidents for vendor outages

IsDown monitors your vendors continuously. When we detect an incident, PagerDuty gets a new incident with full context: affected services, severity, regions, and status updates. Auto-resolves when the vendor recovers.

Setup takes 2 minutes. Try it free.

Start Free Trial

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

Why IsDown + PagerDuty

Your Team Knows Before You Have to Tell Them

Without IsDown

Your on-call engineer gets paged at 3 AM, spends 30 minutes debugging before someone checks if it's a vendor issue.
Vendor incidents are invisible in PagerDuty. You only find out when customers complain.
Misdirected triage. The wrong team investigates while the vendor quietly resolves.

With IsDown + PagerDuty

PagerDuty incident created automatically when a vendor has an outage.
On-call knows it's a vendor issue instantly. No wasted debugging.
Incidents auto-resolve when the vendor recovers.
Your team triages faster with full context.

Start Free Trial

14-day free trial · No credit card required

Use Cases

How on-call teams use IsDown + PagerDuty

The right context reaches the right team, through the escalation policies you already have.

SRE Teams

Know it's a vendor before you start debugging

When AWS us-east-1 has elevated API error rates, IsDown creates a P3 incident in PagerDuty before your synthetic monitors fire. Your on-call engineer opens PagerDuty to find "AWS incident detected," not a wall of alerts to triage.

DevOps with Multiple Dependencies

Full context at 2 AM, not a guessing game

When Stripe has a payment processing degradation at 2 AM, PagerDuty wakes your on-call with full context: affected components, start time, severity. They know immediately it's not the latest deploy.

Platform Teams

40+ SaaS tools, one escalation workflow

You depend on 40+ SaaS tools. Rather than having someone manually check 40 status pages, IsDown feeds all third-party incidents into PagerDuty's existing escalation policies. The right people get paged for the right vendors.

Frequently Asked Questions

How is IsDown different from PagerDuty's built-in integrations?

PagerDuty's integrations alert you to problems in your own infrastructure. IsDown monitors your vendors' infrastructure (AWS, Stripe, GitHub, Salesforce, and 6020+ others) and creates PagerDuty incidents when they have issues. It fills the third-party blind spot.

Will IsDown create too many incidents in PagerDuty?

You control exactly which vendors and severity levels trigger PagerDuty incidents. Most teams monitor 10-30 critical vendors and set up routing rules so only high-severity issues create incidents. Low-severity degradations can go to Slack instead.

How do I connect IsDown to PagerDuty?

After signing up, go to your IsDown dashboard, then Alerts & Integrations, then Add PagerDuty. Add your integration key, select the service, and you're done. The entire setup takes less than 2 minutes.

What data is sent to PagerDuty?

IsDown sends full incident details: service name, affected components, severity, region, start time, and status updates. Your on-call team gets all the context they need to make a decision.

How quickly are incidents created in PagerDuty?

IsDown detects outages independently, often 20-45 minutes before vendors update their own status pages. PagerDuty incidents are created within seconds of detection.

Can I customize which services trigger PagerDuty incidents?

Yes. You choose which vendors to monitor and which severity levels trigger incidents. Set up different routing rules per team so AWS alerts go to infrastructure and Stripe alerts go to payments.

Never again lose time looking in the wrong place

Add third-party vendor outage detection to your existing PagerDuty workflow. Setup takes 2 minutes.

Start Free Trial

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