phoenixNAP incident

Connectivity Issues in Singapore

Major Resolved View vendor source →

phoenixNAP experienced a major incident on October 11, 2025 affecting Dedicated Servers and Virtual Private Data Center (VPDC), lasting 5h 5m. The incident has been resolved; the full update timeline is below.

Started
Oct 11, 2025, 03:58 AM UTC
Resolved
Oct 11, 2025, 09:04 AM UTC
Duration
5h 5m
Detected by Pingoru
Oct 11, 2025, 03:58 AM UTC

Affected components

Dedicated ServersVirtual Private Data Center (VPDC)

Update timeline

  1. investigating Oct 11, 2025, 03:58 AM UTC

    We have identified network disrupting issues in our Singapore datacenter. Our engineers are investigating. More updates will follow...

  2. investigating Oct 11, 2025, 04:04 AM UTC

    We have identified network disrupting issues in our Singapore datacenter. Our engineers are investigating. More updates will follow...

  3. investigating Oct 11, 2025, 04:36 AM UTC

    We are continuing to investigate this issue in our Singapore datacenter. Our engineers are investigating. More updates will follow...

  4. identified Oct 11, 2025, 04:58 AM UTC

    We encountered an unexpected issue at one of our data centers that is currently impacting services. Our team has identified the cause and is actively working to implement a fix.

  5. identified Oct 11, 2025, 05:45 AM UTC

    We encountered an unexpected issue at one of our data centers that is currently impacting services. Our team has identified the cause and is actively working to implement a fix.

  6. identified Oct 11, 2025, 07:42 AM UTC

    We’ve implemented a fix that has partially restored functionality for some customers. Our team is continuing to monitor the situation and working to ensure full resolution. We’re actively engaging with affected customers to verify service recovery and will share further updates as we make progress.

  7. identified Oct 11, 2025, 09:00 AM UTC

    Hello, This issue has been resolved based on our monitoring systems and confirmations from our customers. f you have any questions about this incident, feel free to reach out to [email protected].

  8. identified Oct 11, 2025, 09:02 AM UTC

    We are continuing to work on a fix for this issue.

  9. resolved Oct 11, 2025, 09:04 AM UTC

    This incident has been resolved.