WordPress VIP Outage History

Started Oct 15, 2026, 03:48 PM UTC· resolved Oct 15, 2026, 07:17 PM UTC

1. investigating Oct 15, 2026, 03:48 PM UTC

   WordPress VIP is observing elevated temperatures in our DFW data center. There is no confirmed impact to customer sites at this time. We’re actively monitoring and will provide updates here as more information becomes available.

2. monitoring Oct 15, 2026, 03:54 PM UTC

   Temperatures in our DFW data center are beginning to stabilise. We continue to monitor closely and will provide further updates as needed.

3. monitoring Oct 15, 2026, 04:08 PM UTC

   Temperatures in our DFW data center have begun rising again and have exceeded earlier levels. We'll continue to provide updates here as they're available.

4. monitoring Oct 15, 2026, 04:09 PM UTC

   As a precaution, we are moving sites on Enhanced and higher support packages from our DFW data center to alternate data centers. We expect this to minimize disruption for these sites. Engineers continue to monitor temperatures closely, and we will provide another update when we have one.

5. monitoring Oct 15, 2026, 04:12 PM UTC

   Some sites hosted in our DFW data center are experiencing intermittent errors. Our engineers are actively working to mitigate the impact, and we'll continue updating here periodically.

6. monitoring Oct 15, 2026, 04:27 PM UTC

   Temperatures in our DFW data center continue to rise. Some sites hosted there may experience intermittent errors or slower performance. Our engineers are continuously working to minimize the impact, and we'll provide another update as soon as possible.

7. monitoring Oct 15, 2026, 05:00 PM UTC

   Temperatures in our DFW data center continue to rise. Some sites hosted there may experience intermittent errors or slower performance. Our engineers are continuously working to minimize the impact, and we'll provide another update as soon as possible.

8. monitoring Oct 15, 2026, 05:08 PM UTC

   Temperatures in our DFW data center remain elevated, and some sites hosted there may continue to experience intermittent errors or slower performance. As a result of moving sites from DFW, our DCA data center is also experiencing increased load, and some sites hosted in DCA may see slower performance.

9. monitoring Oct 15, 2026, 05:17 PM UTC

   Temperatures in our DFW data center have been decreasing steadily for the past several minutes. Our engineers are monitoring closely, though some sites in DFW and DCA may still experience intermittent errors or slower performance while conditions return to normal.

10. monitoring Oct 15, 2026, 05:35 PM UTC

    Temperatures in our DFW data center continue to trend downward. Site performance in our DCA data center is improving as load stabilizes. Our engineers continue to monitor DFW temperatures closely, while mitigating impact to customer sites to the extent possible.

11. monitoring Oct 15, 2026, 05:53 PM UTC

    Temperatures in our DFW data center have been trending downward consistently for approximately 45 minutes. Additional capacity allocated in our DCA data center is also helping affected sites recover. Load remains higher than usual, and some sites in DFW and DCA may continue to see slower performance, which we expect to improve as conditions stabilize and traffic is gradually returned to its usual data centers.

12. monitoring Oct 15, 2026, 06:12 PM UTC

    Temperatures in our DFW data center have continued to decline steadily for more than one hour. Some sites are still experiencing slower performance in DFW and DCA, and our engineers are monitoring closely and minimizing the impact where possible.

13. monitoring Oct 15, 2026, 06:25 PM UTC

    The cooling issue in our DFW data center has been resolved. We are gradually returning traffic to its usual data center at a pace that minimizes impact to customer sites. Some sites in DFW and DCA may experience temporarily slower performance while traffic is redistributed. Our engineers continue to monitor closely.

14. monitoring Oct 15, 2026, 06:47 PM UTC

    We are nearly finished returning traffic to DFW, and temperatures in our DFW data center are now at their lowest point in approximately three hours. Load in our DCA data center is returning to normal levels, and site performance in both data centers continues to improve.

15. resolved Oct 15, 2026, 07:17 PM UTC

    Traffic redistribution is complete, and site performance in DFW and DCA has returned to normal. The cooling issue in our DFW data center is resolved, and we apologize for any disruption this may have caused. If you continue to experience issues, please don’t hesitate to contact WordPress VIP Support.

Read the full incident report →

Started Aug 06, 2026, 03:22 PM UTC· resolved Aug 07, 2026, 12:00 AM UTC

1. monitoring Aug 06, 2026, 03:22 PM UTC

   GitHub is currently experiencing an issue that may affect deploying to WordPress VIP. The team is monitoring the situation, and you can follow updates on https://www.githubstatus.com/incidents/qcvjkzcs7j74

2. monitoring Aug 06, 2026, 10:18 PM UTC

   GitHub is continuing to make progress, and we are seeing early signs of recovery with queued GitHub Action workflows resuming. We are continuing to monitor. Full incident details at https://www.githubstatus.com/incidents/qcvjkzcs7j74

3. resolved Aug 07, 2026, 12:00 AM UTC

   The GitHub Actions service disruption has been resolved. GitHub has addressed the underlying issue, global queues have been reduced, and workflow runs are reporting a 99% success rate. For the latest from GitHub, see https://www.githubstatus.com/incidents/qcvjkzcs7j74

Read the full incident report →

Started Jul 21, 2026, 08:35 AM UTC· resolved Jul 21, 2026, 10:10 AM UTC

1. investigating Jul 21, 2026, 08:35 AM UTC

   We're investigating deployment failures affecting WordPress VIP customers. We'll post an update as we learn more.

2. investigating Jul 21, 2026, 09:39 AM UTC

   We're continuing to investigate deployment failures affecting WordPress VIP customers. We'll post an update as soon as we have more information to share.

3. monitoring Jul 21, 2026, 09:40 AM UTC

   We've implemented a fix for the deployment failures affecting WordPress VIP customers. New deployments should now complete correctly. We'll continue monitoring to confirm everything is stable.

4. resolved Jul 21, 2026, 10:10 AM UTC

   This issue has been resolved. The deployment failures were caused by an upstream GitHub incident affecting SSH authentication using certain types of deploy keys (see: https://www.githubstatus.com/incidents/g40zcbvchny4 ). VIP has since worked around the issue, and all deployments that failed during this window have been retried. Thank you for your patience.

Read the full incident report →

Started Jul 12, 2026, 01:16 PM UTC· resolved Jul 12, 2026, 04:22 PM UTC

1. monitoring Jul 12, 2026, 01:16 PM UTC

   On July 12, 2026, a subset of sites hosted in our DFW data center experienced two brief, isolated periods of elevated error rates and increased response times, caused by an issue affecting two database nodes. Impact was limited to sites whose primary database resided on an affected node: - 13:15–13:45 UTC — sites with a primary on the first node - 14:08–14:20 UTC — sites with a primary on the second node In both cases, databases automatically failed over to healthy replicas and the affected sites recovered. Cached and read-only traffic was largely unaffected; impact was concentrated on write and dynamic (uncached) requests. The API that powers the VIP Dashboard was also affected between 13:15 and 13:35 UTC, during which some dashboard actions, and the VIP CLI, may have been temporarily unavailable. Dashboard functionality was fully restored by 13:35 UTC.

2. investigating Jul 12, 2026, 03:45 PM UTC

   We continue to see some issues impacting the VIP Dashboard and VIP-CLI. We are investigating further.

3. monitoring Jul 12, 2026, 03:46 PM UTC

   Issue was identified and was restored. Monitoring the situation as all responses have recovered.

4. resolved Jul 12, 2026, 04:22 PM UTC

   Issue is resolved. VIP Dashboard and CLI are fully operational.

Read the full incident report →

Started May 08, 2026, 06:37 PM UTC· resolved May 09, 2026, 12:16 AM UTC

1. monitoring May 08, 2026, 06:37 PM UTC

   Let’s Encrypt is currently seeing service disruptions which may result in failed or delayed TLS certificate issuance and renewals for customers using automatic certificate management. https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3 Only customers requesting new certificates or renewals via Let’s Encrypt are impacted; existing certificates remain valid until expiry We’ll continue monitoring and share updates as they become available.

2. monitoring May 08, 2026, 09:07 PM UTC

   Let's Encrypt has resumed issuance and is continuing to monitor: https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3 We will continue to monitor and provide updates until the incident is fully resolved.

3. resolved May 09, 2026, 12:16 AM UTC

   The incident is resolved. Let's Encrypt is continuing to monitor on their end. Information on the incident can be found at: https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3

Read the full incident report →

Started Apr 05, 2026, 08:16 AM UTC· resolved Apr 05, 2026, 10:12 AM UTC

1. investigating Apr 05, 2026, 08:16 AM UTC

   The team has noted impacted performance to the filesystem, investigating

2. monitoring Apr 05, 2026, 10:12 AM UTC

   The team has applied a change and improved response times are being observed, the team is monitoring for further impact

Read the full incident report →

Started Nov 18, 2025, 11:48 AM UTC· resolved Nov 18, 2025, 06:10 PM UTC

1. monitoring Nov 18, 2025, 11:48 AM UTC

   Cloudflare is currently experiencing an issue that may affect customers accessing our platform through Cloudflare. You can follow updates on cloudflarestatus.com . Only customers routing traffic through Cloudflare are impacted. You can temporarily bypass Cloudflare by pointing your DNS records to VIP . We will continue monitoring the situation and share updates as available.

2. monitoring Nov 18, 2025, 01:08 PM UTC

   Cloudflare has identified the issue , and a fix is currently being implemented. We will continue to monitor the situation and share updates as they become available.

3. monitoring Nov 18, 2025, 01:44 PM UTC

   We have received reports that some customers are currently unable to create support tickets. If you need assistance, please email us directly at [email protected] , and our team will work with you via email.

4. resolved Nov 18, 2025, 06:10 PM UTC

   Cloudflare has identified and resolved the issue. Services are currently operating normally and their team is continuing to monitor. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Read the full incident report →