The incident was caused by the Priority Server being unresponsive, with timeouts and connection errors across multiple regions. The server experienced several downtimes with repeated "timeout" errors, but it eventually recovered and the incident was resolved automatically.