We're no longer seeing errors from the PagerDuty endpoint and have confirmed escalations are polling successfully, meaning escalation messages (created in response to /inc escalate) are working once more.
We've followed up with PagerDuty to understand what caused this, and improved our retrying logic to make us more robust to future flakiness.