Issues when attempting to post new incidents to external status pages
This summary is created by Generative AI and may differ from the actual content.
Overview
Between August 7, 2026, at 16:12 UTC (EU) and August 10, 2026, at 05:22 UTC (US), customers were unable to create new incident or maintenance posts on their PagerDuty Status Pages via the web interface due to a validation mismatch in the post-creation request pathways. The issue began in the EU region at 16:12 UTC and later affected the US region at 18:54 UTC, resolving after a rollback at 05:22 UTC on August 10, 2026.
Impact
Customers could not publish new status page posts via the web interface during the incident period, while automated posts (API, integrations, and Incident Workflows) remained unaffected. Existing status pages remained fully accessible with no data loss. No revenue impact was reported, but the disruption affected critical communication for customers during incidents.
Trigger
A deployment update to the PagerDuty Status Pages service introduced validation checks for post classification fields. The update included a data conversion step in the API request pathway but not in the web interface pathway, causing the validation logic to misinterpret web interface requests as malformed.
Detection
The issue was escalated by the Support team at 04:53 UTC on August 10, 2026, after a customer reported post-creation failures. Responders reproduced the failure, identified validation rejections in request logs, and traced the issue to the recent validation deployment.
Resolution
A rollback of the validation deployment was initiated at 05:18 UTC and completed at 05:22 UTC, immediately restoring web-based post creation across both EU and US regions. Full recovery was verified by successfully creating posts, and the incident was declared resolved at 05:33 UTC.
Root Cause
The root cause was a divergence in request pathway handling between the PagerDuty API and web interface. The API pathway included a data conversion step to format request fields for validation, while the web interface pathway lacked this step. This mismatch caused the validation logic to reject all web interface post-creation requests as malformed.