Investigating a Potential Issue

We have resolved an incident where PagerDuty Runbook customers were unable to read or write job execution logs during a short window (from approximately 16:00 to 19:45 GMT). The incident is now resolved. There should be no ongoing impact with job execution log access. We are investigating impacted customers.

We are monitoring improvement in an incident where Runbook instances are unable to access job execution logs. We have deployed a fix, and we expect systems to continue to improve. We currently expect that full resolution will require approximately 15 minutes, and will provide an update within that time.

There appears to be an issue with access (read & write) to Logs, specifically execution logs, for Runbook instances. We are currently investigating.

We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.