Anchor Hosting Incident History

1. resolvedFeb 3 · 14:29 UTC

   All sites are now loading successfully.

Reported by Anchor Hosting on their status page.

1. resolvedFeb 5 · 23:09 UTC

   At 5:10pm an outage affecting one of my WP Engine services experienced an outage affecting some customers. Everything appears to have stabilized within 20 minutes. Will post more details as I have info.

Reported by Anchor Hosting on their status page.

1. resolvedFeb 21 · 21:06 UTC

   After 8 minutes of outage, connection has been restored. Will post more info as it becomes available.

Reported by Anchor Hosting on their status page.

1. resolvedFeb 22 · 03:42 UTC

   This incident has been resolved.

Reported by Anchor Hosting on their status page.

1. resolvedMar 1 · 00:20 UTC

   At this time everything appears to be running smooth.

Reported by Anchor Hosting on their status page.

1. resolvedMar 16 · 02:35 UTC

   High load appears is due to high traffic. Examining traffic logs to identify which sites need to move to server with more capacity and will plan accordingly.

Reported by Anchor Hosting on their status page.

1. resolvedMar 16 · 11:02 UTC

   The server has been restored. The affected websites total downtime was 45 minutes. Everything is now up and running.

Reported by Anchor Hosting on their status page.

1. resolvedMar 21 · 16:41 UTC

   The instability is better however the server is continuing to run slower then normal affecting various backend pages. Will continue to work on this server until the backend performance improves.

Reported by Anchor Hosting on their status page.

1. resolvedMar 28 · 17:51 UTC

   This incident has been resolved.

Reported by Anchor Hosting on their status page.

1. resolvedMar 29 · 21:10 UTC

   Hardware upgrade completed. Everything appears to be running smooth now.

Reported by Anchor Hosting on their status page.

1. resolvedApr 25 · 23:38 UTC

   Other then the unscheduled restarts earlier today, both servers have been stable.

Reported by Anchor Hosting on their status page.

1. resolvedJun 1 · 14:35 UTC

   A server reboot became necessary which resulted in some additional downtime. At this time all websites are back up and running.

Reported by Anchor Hosting on their status page.

1. resolvedJun 23 · 09:31 UTC

   This incident has been resolved.

Reported by Anchor Hosting on their status page.

1. resolvedJun 25 · 15:45 UTC

   WP Engine engineers believe they have resolved the issues with the new server and the datacenter. Will continue to monitor for stability.

Reported by Anchor Hosting on their status page.

1. resolvedJun 26 · 17:31 UTC

   Everything has continued to remain stable today with exception of one large spike resulting in a few small outages around 10:50am. WP Engine believes have figured out what went wrong with the migration and are working to improve their automations to prevent this from happening on other servers. At this time they believe everything is healthy with anchorhost4. I'll continue to monitor for stability.

Reported by Anchor Hosting on their status page.

1. resolvedAug 6 · 01:55 UTC

   After 30 minutes of instability everything is back to healthy levels. The outages was caused due to high I/O wait. Will be doing some investigations as to why that might be.

Reported by Anchor Hosting on their status page.

1. resolvedAug 8 · 23:26 UTC

   After some brief instability this morning, the 'anchorhost2' server has remained stable throughout the day. Still working to trace down the source of slow down. Until that has been found and corrected I've begun internal migrations to other servers to help spread the higher then typical load.

Reported by Anchor Hosting on their status page.

1. resolvedAug 15 · 23:16 UTC

   The load on the server stabilized around 3hrs ago. Will continue to monitor and move installations to other servers until this server remains stable.

Reported by Anchor Hosting on their status page.

1. resolvedAug 16 · 16:59 UTC

   At this time all sites are stable. The root issue caused by database size has significantly been reduced. Will continue to monitor the server over the next few days for stability.

Reported by Anchor Hosting on their status page.

1. resolvedAug 18 · 14:32 UTC

   WP Engine performed a server reboot in order to bring things back online. Everything appears healthy now. Total of 30 minutes of instability.

Reported by Anchor Hosting on their status page.

1. resolvedAug 21 · 20:37 UTC

   WP Engine performed a server reboot in order to stabilize. I've manually offloaded some high usage installations. Will continue to monitor and followup with WP Engine to make sure this server is in a healthy state.

Reported by Anchor Hosting on their status page.

1. resolvedNov 16 · 00:40 UTC

   This incident has been resolved.

Reported by Anchor Hosting on their status page.

1. resolvedMar 24 · 20:14 UTC

   After 30 minutes of instability all sites are now healthy.

Reported by Anchor Hosting on their status page.

1. resolvedApr 25 · 15:46 UTC

   Service has been restored.

Reported by Anchor Hosting on their status page.

1. resolvedMay 17 · 03:17 UTC

   This incident has been resolved.

Reported by Anchor Hosting on their status page.

1. postmortemAug 2 · 16:37 UTC

   After some investigation, it appears that the downtime was due to a host-level issue with WP Engine's infrastructure provider. WP Engine hasn't found any indication of excessive resource usage, and this appears to be an isolated event.

Reported by Anchor Hosting on their status page.

1. resolvedAug 27 · 17:08 UTC

   All sites are back online.

Reported by Anchor Hosting on their status page.

1. resolvedSep 21 · 19:06 UTC

   All sites have been restored.

Reported by Anchor Hosting on their status page.

1. resolvedDec 30 · 22:04 UTC

   All sites have been restored.

Reported by Anchor Hosting on their status page.

1. resolvedMar 11 · 15:02 UTC

   Kinsta has restored all affected websites.

Reported by Anchor Hosting on their status page.

1. postmortemApr 30 · 18:51 UTC

   Google Cloud reported a [hostError](https://cloud.google.com/compute/docs/faq#hosterror) for one of Kinsta’s compute instances. These sorts of errors are quite rare and occur due to hardware or software failures at a Google Cloud data center. In this case, this error caused one of Kinsta’s virtual machines to go offline. Google restarted the affected compute instance as quickly as possible but that took several minutes and during that time all site containers associated with that instance were unavailable.

Reported by Anchor Hosting on their status page.

1. resolvedJun 3 · 02:05 UTC

   Last remaining websites have been fully restored.

Reported by Anchor Hosting on their status page.

1. resolvedOct 8 · 17:15 UTC

   All websites have been restored.

Reported by Anchor Hosting on their status page.

1. resolvedOct 31 · 16:44 UTC

   Kinsts is reporting the issue has been resolved.

Reported by Anchor Hosting on their status page.

1. resolvedMay 21 · 20:49 UTC

   All affected sites have been restored.

Reported by Anchor Hosting on their status page.

1. resolvedJul 24 · 13:23 UTC

   All customer sites have been restored.

Reported by Anchor Hosting on their status page.

1. resolvedAug 12 · 07:53 UTC

   All Live and Staging sites have been restored. The services are all fully available now.

Reported by Anchor Hosting on their status page.

1. resolvedSep 21 · 09:46 UTC

   This incident has been resolved.

Reported by Anchor Hosting on their status page.

1. resolvedDec 15 · 17:08 UTC

   The Anchor Hosting portal has been updated: https://anchor.host/account. Moving forward please use the listed IP addresses for SFTP and SSH connections.

Reported by Anchor Hosting on their status page.

1. resolvedJun 3 · 00:32 UTC

   Cloudflare has resolved the issue: https://www.cloudflarestatus.com/incidents/zbzjv8sm3g94.

Reported by Anchor Hosting on their status page.

1. resolvedJun 17 · 16:09 UTC

   Cloudflare has mitigated the issue and is monitoring the situation.

Reported by Anchor Hosting on their status page.

1. resolvedDec 16 · 21:20 UTC

   Cloudflare reported the issue is now resolved.

Reported by Anchor Hosting on their status page.

1. resolvedMay 6 · 15:17 UTC

   Site monitor is showing all sites are back online as of 10:30am. Kinsta is continue to monitor the situation.

Reported by Anchor Hosting on their status page.

1. resolvedAug 25 · 14:25 UTC

   All customers identified with PHP 8 compatibility issues have been rolled back to PHP 7.4. If you notice any issues with your website, be sure to reach out to support: https://anchor.host/account.

Reported by Anchor Hosting on their status page.

1. resolvedAug 18 · 02:26 UTC

   At this time all sites have been restored.

Reported by Anchor Hosting on their status page.

1. resolvedOct 30 · 21:07 UTC

   Cloudflare is reporting everything is restored on their end: https://www.cloudflarestatus.com/incidents/l6x2h1zp69bc. All customers continue to remain healthy. Most customers were restored at 4:20 EST. In total around 23 minutes of outage.

Reported by Anchor Hosting on their status page.

1. postmortemJun 13 · 09:20 UTC

   Cloudflare wrote a detailed blog post reviewing yesterday’s outage: [https://blog.cloudflare.com/cloudflare-service-outage-june-12-2025/](https://blog.cloudflare.com/cloudflare-service-outage-june-12-2025/). During that outage all sites hosted with Kinsta were down including our own [Anchor Hosting website](https://anchor.host). That meant customers couldn’t reach out via live chat. Major outages like this are posted to [https://anchorhost.statuspage.io](https://anchorhost.statuspage.io/). If your not already subscribed, I recommend doing so.

Reported by Anchor Hosting on their status page.

1. resolvedNov 18 · 14:57 UTC

   All customer website appears to be restored and healthy. Will continue to monitor the Cloudflare situation: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7.

Reported by Anchor Hosting on their status page.

1. resolvedApr 1 · 19:16 UTC

   The server has been stabilized. All customer websites should be restored.

Reported by Anchor Hosting on their status page.

1. resolvedAug 19 · 21:54 UTC

   WP Rocket doesn't have a patch yet so we patched it directly with our v3.23.2.2. All customers affected with the WP Rocket + WordPress 7.1 compatible issue should be restored. Whenever WP Rocket does release an official fix, customers should automatically upgrade to that. There were a few other plugins with similar compatible issues with v7.1. Reviewing and fixing as I discover them.

Reported by Anchor Hosting on their status page.