Is PagerDuty down?
PagerDuty is up
Right now
No. PagerDuty API edge answers UpButler's independent probe; no machine-readable official status.
No official machine-readable status
For agents
proceed
Proceed.
GET upbutler.com/status/pagerduty/status.agent.json
MCP: upstream_status {"service":"pagerduty"}
Incident paging and on-call. If your alerts route through it, its incident is yours.
What PagerDuty says
status.pagerduty.com has no public JSON API or feed we may read; only the independent probe is shown.
Their site: status.pagerduty.comWhat UpButler measured
API edge is answeringHTTP 401 · 744 ms
One request without credentials to api.pagerduty.com every two minutes, from eu-central (one location, not a global view). An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 06:09 UTC
PagerDuty incidents, last 90 days
Without a machine-readable source there is no incident history to show. PagerDuty keeps its own at status.pagerduty.com.
Get alerted when PagerDuty goes down
No account. One email when our probe cannot reach PagerDuty for several minutes, one when it can again. You confirm the address first, and every email has a one-click unsubscribe.
On UpButler? Add PagerDuty as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show PagerDuty's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/pagerduty)Tell your outage from PagerDuty's
Declare that your project depends on PagerDuty. When one of your monitors fails while PagerDuty has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- pagerdutycurl -s https://upbutler.com/status/pagerduty/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "pagerduty",
"verdict": "proceed",
"status": "operational",
"reason": "PagerDuty API edge answers UpButler's independent probe; no machine-readable official status",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is PagerDuty down right now?
- No. As of 2026-10-10 07:19 UTC, PagerDuty is up. This page reads the status again every 2 minutes.
- Where does this status come from?
- status.pagerduty.com has no public JSON API or feed we may read; only the independent probe is shown.
- What does UpButler's own PagerDuty check prove?
- Every two minutes UpButler sends one request without credentials to the PagerDuty API edge (api.pagerduty.com) from eu-central. Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.
- How can my agent or app check PagerDuty status?
- Fetch https://upbutler.com/status/pagerduty/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"pagerduty"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or PagerDuty's?
- Add "pagerduty" to the dependencies of your UpButler workspace. When one of your monitors fails while PagerDuty has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with PagerDuty. Status and incident text belong to PagerDuty and are read from their public status source; the probe result is UpButler's own measurement.