Vendor-reported status observed by INTERNETMON

PagerDuty status

PagerDuty · Pagerduty Status

Operational

PagerDuty reports 0 active incident(s), 0 maintenance item(s), and 64 public service(s).

Platform and regional services

Checked 2026-08-19T11:15:01.459898+00:00 Poll cadence every 60 seconds Feed state fresh

Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

0 retained of 0 reported

No active incidents were included in this vendor report.

Maintenance

0 retained of 0 reported

No active or upcoming maintenance was included in this vendor report.

Component health

Complete source scope

Reported

Retained

Affected retained

Projection scope: complete · 64 retained of 64 reported components across 19 source groups.

Internal Status Page (US) Group: Status Page Operational

REST API (EU) Group: REST API Operational

Events API (US) Group: Events API Operational

Events API (EU) Group: Events API Operational

Web Application (US) Group: Web Application Operational

Web Application (EU) Group: Web Application Operational

Mobile Application (US) Group: Mobile Application Operational

Mobile Application (EU) Group: Mobile Application Operational

Webhooks (US) Group: Webhooks Operational

Webhooks (EU) Group: Webhooks Operational

Jira Cloud (US) Group: Integrations Operational

Jira Cloud (EU) Group: Integrations Operational

Jira Server (US) Group: Integrations Operational

Jira Server (EU) Group: Integrations Operational

Microsoft Teams (US) Group: Integrations Operational

Microsoft Teams (EU) Group: Integrations Operational

Slack (US) Group: Integrations Operational

Slack (EU) Group: Integrations Operational

Incoming Email (US) Group: Integrations Operational

Incoming Email (EU) Group: Integrations Operational

Showing 20 of 64 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

Up to 30 days retained

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

2026-08-19T10:46:11.268730+00:00

Operational

HTTP 200 · 1011.18 ms feed latency

2026-08-19T09:45:34.896009+00:00

Operational

HTTP 200 · 1272.79 ms feed latency

2026-08-19T08:44:36.904192+00:00

Operational

HTTP 200 · 1289.05 ms feed latency

2026-08-19T07:44:24.428091+00:00

Operational

HTTP 200 · 1447.66 ms feed latency

2026-08-19T06:43:55.712506+00:00

Operational

HTTP 200 · 1073.82 ms feed latency

2026-08-19T05:43:22.977110+00:00

Operational

HTTP 200 · 1178.99 ms feed latency

2026-08-19T04:42:45.006491+00:00

Operational

HTTP 200 · 1332.9 ms feed latency

2026-08-19T03:41:54.764984+00:00

Operational

HTTP 200 · 1967.26 ms feed latency

2026-08-19T02:41:04.179541+00:00

Operational

HTTP 200 · 1952.59 ms feed latency

2026-08-19T01:40:06.030473+00:00

Operational

HTTP 200 · 1669.93 ms feed latency

Collection details

Sanitized public metadata

Provider adapter

Pagerduty Status

Feed response

HTTP 200

Feed latency

1525.32 ms

JSON source

Sanitized detail projection