phoenixNAP incident

Elevated Temperatures at PHX DC

Notice Resolved View vendor source →

phoenixNAP experienced a notice incident on August 20, 2026 affecting Colocation and Dedicated Servers and 1 more component, lasting 9h 29m. The incident has been resolved; the full update timeline is below.

Started
Aug 20, 2026, 09:15 AM UTC
Resolved
Aug 20, 2026, 06:45 PM UTC
Duration
9h 29m
Detected by Pingoru
Aug 20, 2026, 09:15 AM UTC

Affected components

ColocationDedicated ServersBare Metal CloudData Security Cloud (DSC)Virtual Private Data Center (VPDC)Managed Private Cloud (MPC)Backup as a Service (BaaS) - Veeam Managed BackupsBackup as a Service (BaaS) - Veeam Cloud ConnectManaged Backup for Office 365Disaster Recovery as a Service (DRaaS) - Zerto

Update timeline

  1. investigating Aug 20, 2026, 09:15 AM UTC

    We're observing the elevated temperatures in RadiusDC, which triggered our environmental monitoring systems. Our team is actively investigating the cause and monitoring temperature levels across the affected area. Systems remain under close observation, and we are taking precautionary measures to maintain safe operating conditions and service stability.

  2. investigating Aug 20, 2026, 09:40 AM UTC

    Our teams are working closely with the RadiusDC team, as the incident has been escalated to them for further investigation and resolution.

  3. investigating Aug 20, 2026, 10:34 AM UTC

    We are seeing temperatures stabilize in the affected data center. Our teams continue to closely monitor the situation.

  4. monitoring Aug 20, 2026, 10:57 AM UTC

    We’ve received feedback from customers that temperatures have stabilized on their end. We’re continuing to monitor the situation closely and will provide further updates as needed.

  5. monitoring Aug 20, 2026, 01:20 PM UTC

    So far, all alerts have cleared, and temperatures have returned to normal levels. We continue to monitor the situation closely to ensure conditions remain stable.

  6. monitoring Aug 20, 2026, 02:01 PM UTC

    The issue is now considered resolved, and no further impact has been observed. We will continue to monitor the environment as part of our normal operations.

  7. resolved Aug 20, 2026, 06:45 PM UTC

    The issue is now considered resolved, and no further impact has been observed.