PagerDuty Uptime Monitoring Setup and Monitor Costs
November 2026 · UptimeHub
Checked from regions with auto-retry. No single-location false alarms.
All systems operational. Steady pulse across every region.
api.example.com returned no response from all 2 regions. Auto-retry confirmed the outage, then we alerted your team.
api.example.com is back up. The incident is logged to your status page history automatically.
90-day uptime · branded · your domain
Live demo · drive it, no signup needed
PagerDuty does not check whether your website or API is up. It receives alerts from a monitoring tool, decides who is on call and wakes that person up. So PagerDuty uptime monitoring is always two products: a monitor that runs the checks and sends a trigger event when something fails, and PagerDuty routing that event. The monitor you pick decides how fast the page arrives, how many false alarms reach the rota, and whether the incident closes itself when the site recovers.
This article covers how the connection works, which monitor plans actually include it, and what the pair costs for a typical small team. PagerDuty figures come from its public pricing page as summarized in our PagerDuty pricing breakdown. UptimeRobot figures are what a US visitor sees, as tracked in our UptimeRobot pricing breakdown; its list is localized, so a European visitor sees euros.
How a monitor sends uptime alerts into PagerDuty
Almost every monitoring tool that talks to PagerDuty uses the PagerDuty Events API v2. You create a service in PagerDuty (or use Event Orchestration), add an Events API v2 integration, and PagerDuty gives you a 32 character integration key, also called a routing key. You paste that key into the monitoring tool. From then on the monitor posts JSON events to PagerDuty with one of three actions: trigger, acknowledge or resolve.
The detail that separates a good integration from a noisy one is the deduplication key. Each event carries a dedup_key. Events with the same key land on the same PagerDuty alert instead of opening a new one. A monitor that reuses one key per outage gives you exactly one incident for a 20 minute outage, and when the site comes back it sends a resolve with the same key, so the incident closes without anyone touching it. A monitor that sends a fresh trigger on every failed check, or never sends the resolve, leaves the on-call engineer cleaning up a stack of open incidents at breakfast.
UptimeHub sends one trigger per confirmed outage, keyed to that outage, and a resolve with the same key on recovery. The event severity is error, raised to critical when an escalation step fires on plans that have escalation, which lets you build PagerDuty urgency rules on top of it. You will find the setup under alert settings, next to Slack, Microsoft Teams, Discord, Telegram, webhook, email and SMS, as described on the alerts and notification channels page.
Why a false alarm is expensive once PagerDuty is in the loop
A Slack message about a blip that cleared in ten seconds costs nothing. A PagerDuty phone call at 3 a.m. for the same blip costs an engineer's night and a little of their trust in the rota. After a few of those, people start acknowledging pages without looking, which is how real outages get missed.
Most false alarms in uptime monitoring come from the monitor's own network: one probe location loses its route to your host for a few seconds, the check fails and the alert goes out. The fix is confirmation. UptimeHub runs checks from two regions and needs a second region to confirm a failure before it sends anything, so a single bad path never reaches PagerDuty. Whatever tool you choose, check this before you connect it to a phone rota. It matters more than the check interval.
Which monitor plans include the PagerDuty integration
The integration is not available on every plan of every tool, and that is where many teams get surprised. UptimeRobot, the most common starting point, lists PagerDuty together with webhooks and Zapier as additions on its Team plan. Free and Solo do not include it. Here is the plan math for a team that wants PagerDuty connected.
| Monitor plan | PagerDuty included | Monitors | Fastest interval | Seats | Price per month (US) |
|---|---|---|---|---|---|
| UptimeRobot Free | No | 50 | 5 minutes | None | $0 |
| UptimeRobot Solo | No | 10 or 50 | 60 seconds | Notify seats as a paid add-on | From $12 billed yearly |
| UptimeRobot Team | Yes | 100 | 30 seconds | 3 | $39 billed yearly ($46 monthly) |
| UptimeRobot Scale | Yes | 200 or 500 | 15 seconds | 5 | From $79 billed yearly |
| UptimeHub Starter | Yes | 20 | 60 seconds | Unlimited | $24 billed yearly ($49 monthly) |
| UptimeHub Pro | Yes | 100 | 30 seconds | Unlimited | $49 billed yearly ($99 monthly) |
| UptimeHub Business | Yes, plus escalation | 400 | 30 seconds | Unlimited | $99 billed yearly ($199 monthly) |
Read honestly, the table says two things. Below 20 monitors, UptimeHub Starter is the cheapest way in this set to get uptime checks into PagerDuty, because the integration is on the entry plan instead of behind a tier jump. Between 21 and 100 monitors, UptimeRobot Team is $10 a month cheaper than UptimeHub Pro at the same 30 second interval, and if you only need three people on the monitoring side, that is a fair reason to stay. UptimeHub earns the difference with unlimited seats, two-region confirmation before alerting, DNS and domain expiry checks on Pro, and unlimited branded status pages.
A worked example for a team of six engineers
Take a SaaS team of six engineers with 40 endpoints worth watching: the marketing site, the app, the public API, a few webhooks, the login page and the scheduled jobs that bill customers. They want phone alerts at night through a proper rota and a public status page during incidents.
PagerDuty. Six users is one past the free plan's limit of five, so the whole team moves to Professional at $21 per user per month billed annually. That is $126 a month, or $1,512 a year. If they also want PagerDuty's own status page, it is an add-on from $89 a month per 1,000 subscribers, another $1,068 a year. Our article on PagerDuty status page pricing breaks that add-on down.
The monitor. Forty endpoints rule out UptimeHub Starter and UptimeRobot Solo. UptimeRobot Team covers them at $468 a year and includes status pages, with three seats. UptimeHub Pro covers them at $588 a year with unlimited seats and unlimited status pages, so the PagerDuty status page add-on is not needed either way.
| Stack for 6 engineers and 40 endpoints | Per year |
|---|---|
| PagerDuty Professional plus PagerDuty status page plus UptimeRobot Team | $3,048 |
| PagerDuty Professional plus UptimeRobot Team, using its status page | $1,980 |
| PagerDuty Professional plus UptimeHub Pro, using its status page | $2,100 |
| PagerDuty Free (5 responders on the rota) plus UptimeHub Pro | $588 |
The last row is the one most small teams miss. PagerDuty's free plan covers five users with one schedule and one escalation policy. If only five of the six engineers carry the pager and the sixth is happy with Slack, the paid PagerDuty line disappears. Because UptimeHub does not charge per seat, the sixth person still gets a login and every Slack and email alert. That is a $1,512 a year decision, and it is worth having before you sign up for Professional. The trade-offs between the two big on-call tools are in our Opsgenie vs PagerDuty pricing comparison.
Do you need PagerDuty at all for uptime alerts?
Not always. PagerDuty earns its price when several people share an on-call rota with escalation, when alerts come from many systems (APM, logs, infrastructure and uptime) and need one place to land, or when incident response has a process with postmortems and stakeholders. For a team of two or three that only needs to know the site is down, a monitor that sends SMS and posts to Slack does the job, and every UptimeHub plan includes SMS credits (50 a month on Starter, 250 on Pro). Business adds escalation inside UptimeHub, so a page that goes unacknowledged moves to the next person without a separate on-call product.
The checks that matter most are the ones tied to money. If the endpoint that breaks is your checkout or your renewal job, the cost does not stop when the site comes back: failed renewals and confused customers turn into refund requests and disputes weeks later, which is a separate problem tools like Nochargeback exist to handle. Monitoring catches the outage, so put those endpoints on the shortest interval you have.
Setting it up in UptimeHub
- In PagerDuty, open the service that should own website alerts and add an integration of type Events API v2.
- Copy the 32 character integration key.
- In UptimeHub, open alert settings, paste the key into the PagerDuty field and save.
- Tick PagerDuty on the monitors that should page someone. Leave low-stakes monitors, like a staging site, on Slack or email only.
- Create a test monitor pointed at a URL that returns an error, wait for the confirmed failure, and check that one incident opens in PagerDuty and closes when the monitor recovers.
If you are also replacing a separate status page product, our Status.io alternative page shows how the same monitors drive a branded page, and the UptimeRobot alternative page covers the switch from UptimeRobot in more detail.
PagerDuty uptime monitoring questions
Does PagerDuty do uptime monitoring?
No. PagerDuty routes alerts and runs on-call schedules, escalation and incident response, but it does not run HTTP, ping or SSL checks against your site. It relies on integrations with monitoring tools that detect the outage and send an event. You need an uptime monitor connected through the Events API to get website alerts into PagerDuty.
Does UptimeRobot integrate with PagerDuty?
Yes, from the Team plan up. UptimeRobot lists PagerDuty, webhooks and Zapier as additions on Team, so the Free and Solo plans cannot send events to PagerDuty directly. Its integration opens an incident when a monitor goes down and sends an up event to resolve it on recovery. For a US buyer, Team is about $39 a month billed yearly.
Will the PagerDuty incident close when the site comes back up?
It does if the monitor sends a resolve event with the same deduplication key as the trigger. UptimeHub does this for every confirmed outage, so the incident opens once and closes itself on recovery. If your current tool leaves incidents open, check whether it sends resolve events at all and whether it reuses the key.
What is the cheapest way to get uptime alerts into PagerDuty?
For up to 20 monitors, UptimeHub Starter at $24 a month billed yearly includes the PagerDuty integration, with PagerDuty's free plan covering up to five responders. For 21 to 100 monitors, UptimeRobot Team and UptimeHub Pro are within $10 a month of each other, so seats, confirmation and status page needs decide it.
Ready to connect your rota? Start with the plan that fits your monitor count and paste your integration key in the first five minutes.
Know your site is down before your customers do
Start monitoring your sites, APIs and services from two regions, with alerts by Slack, email, SMS and webhook and a branded status page. Transparent, flat pricing per monitor.