Histórico de interrupções do Anchor Host

1. 19 Eost 2026 da 21:31 UTCidentified

   Como WordPress 7.1 começou a rolar, nos últimos 30 minutos, estamos vendo vários sites offline devido a problemas de compatibilidade com WP Rocket. Estou a trabalhar num remendo. Deve ter tudo de volta e restaurado aqui em breve.

2. 19 Eost 2026 da 21:54 UTCresolved

   WP Rocket ainda não tem um patch, então nós o remendamos diretamente com nosso v3.23.2. Todos os clientes afetados com o WP Rocket + WordPress 7.1 problema compatível deve ser restaurado. Sempre que WP Rocket lançar uma correção oficial, os clientes devem atualizar automaticamente para isso. Havia alguns outros plugins com problemas compatíveis semelhantes com v7.1. Revisando e consertando como eu descobri-los.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Ebrel 2026 da 18:30 UTCidentified

   Starting around 15 minutes we noticed some performance issues reported on a small batch customer WordPress sites at Kinsta. It seems to be isolated to individual server. Some customers at the Chicago (US) datacenter are currently experiencing an outage. We are working with Kinsta in order to restore the affected websites. Affected customers might be seeing slow loading or Cloudflare errors like "A timeout occurred Error code 524".

2. 1 Ebrel 2026 da 19:16 UTCresolved

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

1. 18 Du 2025 da 13:17 UTCinvestigating

   Starting an hour ago Cloudflare reported an outage which is affecting some Kinsta customers: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7. At this time many sites are seeing internal server error, error code 500. Will continue to monitor and report as new info becomes available.

2. 18 Du 2025 da 14:41 UTCmonitoring

   Cloudflare is working on restoring services. I'm starting to see many customer websites have been restored. Will continue to monitor and report back once everything has been restored.

3. 18 Du 2025 da 14:57 UTCresolved

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

1. 12 Mezheven 2025 da 18:22 UTCidentified

   We're aware of an issues affecting customer websites with Kinsta loading. See here for details on the outage: https://status.kinsta.com/incidents/xxy7fv9qk77f.

2. 12 Mezheven 2025 da 18:32 UTCidentified

   This appears to be related to the following Cloudflare outage: https://www.cloudflarestatus.com/incidents/25r9t0vz99rp. Will update as more details are available.

3. 12 Mezheven 2025 da 18:50 UTCidentified

   Starting around 2:10 EST an outage with Cloudflare is affecting Kinsta websites from loading. Everything on the server side appears to be healthy. However due to Kinsta's integration with Cloudflare the routing to the web servers is currently disrupted. Cloudflare is aware and working on a fix: https://www.cloudflarestatus.com/incidents/25r9t0vz99rp.

4. 12 Mezheven 2025 da 19:48 UTCidentified

   Around an 1 hour and 30 minutes ago an outage with Cloudflare is affecting Kinsta sites from loading. We still don't have an ETA on when services will be restored. Cloudflare has reported some of their services are coming back however our uptime monitors haven't see any Kinsta site restored yet. This unfortunately appears to be a large-scale outage affecting other services as well: https://www.theverge.com/news/686365/cloudflare-spotify-google-home-is-down-outage-offline.

5. 12 Mezheven 2025 da 19:54 UTCmonitoring

   We are starting to see Kinsta websites being restored. Will continue to report more info as we have it.

6. 12 Mezheven 2025 da 20:27 UTCmonitoring

   At this time all Anchor Hosting websites have been restored. Will be sending a post mortem followup when that's available. For now if you need anything feel free to reach out via live chat from your Anchor Hosting account: https://anchor.host/account.

7. 12 Mezheven 2025 da 20:58 UTCresolved

   This incident has been resolved.

8. 13 Mezheven 2025 da 09:20 UTCpostmortem

   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.

1. 30 Here 2023 da 20:11 UTCinvestigating

   Within the last 10 minutes site monitors are showing many customers sites with Kinsta are offline. We are aware and working on a resolution. Will post details here.

2. 30 Here 2023 da 20:21 UTCidentified

   This outage is due to an issue with Cloudflare. Kinsta is aware of the problem and working on a solution: https://status.kinsta.com/incidents/9bqvq6tbnc8l.

3. 30 Here 2023 da 20:26 UTCmonitoring

   All sites currently back online. Will keep monitoring the situation until everything is stable.

4. 30 Here 2023 da 21:07 UTCresolved

   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.

1. 17 Eost 2023 da 22:06 UTCinvestigating

   We are seeing a batch of customers receiving errors ranging from critical errors, staging urls and PHPmyadmin pages. Working with Kinsta to find out what's happening and restore affected customer websites.

2. 17 Eost 2023 da 23:00 UTCidentified

   Kinsta sysadmin are working on the issue. It appears that a batch of websites are incorrectly routing traffic from production environments to staging environments. The production sites appear healthy however are unavailable until proper domain routing is restored.

3. 17 Eost 2023 da 23:15 UTCmonitoring

   A fix is being rolled out to all affected customers. Some websites have already been restored. Will continue to monitor until everyone affected has been restored.

4. 18 Eost 2023 da 02:26 UTCresolved

   At this time all sites have been restored.

1. 25 Eost 2022 da 12:57 UTCidentified

   Some customers websites are currently running into issues with PHP update applied late last night. Currently rolling back any customer affected to PHP 7.4 to stablize. I will be applying any compatibly fixes as needed before upgrading PHP. Sorry for the disruption.

2. 25 Eost 2022 da 14:25 UTCresolved

   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.

1. 6 Mae 2022 da 13:31 UTCidentified

   At 9am this morning, a number of customer websites at one of Google Cloud's datacenter are experiencing an outage. Kinsta is aware of the issue and is working to restore the affected websites. See here for more details: https://status.kinsta.com/incidents/zsb97sw6y69w.

2. 6 Mae 2022 da 14:21 UTCidentified

   Outages are now affecting many different Google Cloud datacenter locations. Google engineers are actively working to restore affect locations.

3. 6 Mae 2022 da 15:17 UTCresolved

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

1. 16 Kerzu 2021 da 20:48 UTCidentified

   Getting reports that various customer sites are loading slow or experiencing a partial outage relating to disruption with Cloudflare. Kinsta and Cloudflare is aware of the issue and are working on it: https://status.kinsta.com/incidents/mlq5nl3v9cvd.

2. 16 Kerzu 2021 da 21:20 UTCresolved

   Cloudflare reported the issue is now resolved.

1. 17 Mezheven 2021 da 15:43 UTCinvestigating

   Seeing reports of various customers seeing an error 1105 Temporarily unavailable from Cloudflare. Taking a look and will followup when more information is available.

2. 17 Mezheven 2021 da 15:53 UTCidentified

   The Cloudflare outage appears isolated to individuals located in Canada: https://www.cloudflarestatus.com/incidents/1yz6wmypbmb9.

3. 17 Mezheven 2021 da 16:09 UTCresolved

   Cloudflare has mitigated the issue and is monitoring the situation.

1. 2 Mezheven 2021 da 18:44 UTCidentified

   There appears to be a localized outage with the Cloudflare network affecting visitors on the east coast from reaching websites. They are aware of the problem and are working to restore services as shown here: https://www.cloudflarestatus.com/incidents/zbzjv8sm3g94.

2. 3 Mezheven 2021 da 00:32 UTCresolved

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

1. 15 Kerzu 2020 da 15:11 UTCidentified

   Kinsta is working on improving their infrastructure and is making breaking changes to how their built in development urls operate (ex: sitename.kinsta.cloud). Anyone connecting via SFTP or SSH will need to replace their kinsta.cloud address with the IP or domain name of the website. I recommend using the IP address. Will be rolling out updates to https://anchor.host/account with updated IP info over the next few days. In the meantime feel free to reach out to [email protected] if you need help getting connected via SFTP or SSH.

2. 15 Kerzu 2020 da 17:08 UTCresolved

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

1. 20 Gwengolo 2020 da 23:43 UTCidentified

   Kinsta is aware of an issue affecting the US East 4 datacenter that is causing site outages. They are working to restore the affected websites. https://status.kinsta.com/incidents/f3tyyl0vm8sr

2. 21 Gwengolo 2020 da 02:54 UTCmonitoring

   At this time all websites are back online however the datacenter is still being monitor for stability.

3. 21 Gwengolo 2020 da 09:46 UTCresolved

   This incident has been resolved.

1. 11 Eost 2020 da 18:30 UTCinvestigating

   Some customers with websites located within the Northern Virginia (US East 4) datacenter are currently offline. This appears to be an issue with a particular Google datacenter. Will report back as new information is known.

2. 11 Eost 2020 da 18:41 UTCidentified

   This issue has been narrowed down to an individual LXD within the Northern Virginia (US East 4) datacenter. Kinsta is aware of the issue and is working to restore. https://status.kinsta.com/incidents/qc639q78n6fg

3. 11 Eost 2020 da 20:35 UTCidentified

   Still no ETA on when affected websites will be restored. Kinsta is working with Google Support which is taking longer then usual for this type of issue. This outage is isolated to a individual hardware failure within a Google datacenter.

4. 12 Eost 2020 da 01:54 UTCidentified

   Update from Kinsta: The ongoing issue is due to an apparent hardware failure at Google Cloud. We've been working with Google Cloud Support seeking resolution but at this time an ETA on restoration of the affected virtual machine is unavailable from Google Cloud. Due to the ongoing uncertainty regarding when the hardware failure will be resolved, we've made the decision to restore the affected machine from our most recent backup. Backup restoration is in process now. We will continue working with Google to seek the retrieval of all data leading up to the point where the hardware failure occurred and we will provide additional information as soon as possible.

5. 12 Eost 2020 da 07:11 UTCmonitoring

   From Kinsta, At approximately 2:20 PM EST, 11 August 2020, one of our Google Cloud virtual machines went offline due to an apparent hardware failure. We worked on this issue with Google Cloud Support for multiple hours without success. Eventually, we determined that our best course of action was to restore the affected sites using our most recent backup. We create backups of all of our virtual machines every four hours. In this case, the most recent backup was approximately three hours old at the time that the incident began. As a result, the backup we have restored does not contain any changes made to affected sites after 11:07 AM EST, 11 August 2020. As of 11:22 PM EST 11 August 2020, all LIVE sites which were affected by this incident have been restored from that backup. Our Engineering team is continuing to work on restoring affected STAGING sites. At this time, we are focused on the recovery of website data between the 11:07 AM and 2:20 PM EST. We will keep you updated on our progress as it pertains to recovering this data. We are deeply disappointed by this extended outage. Thank you for your patience with us during this event. We will continue to keep you updated regarding this incident until we are confident it has been fully resolved. Thank you for being a valued Kinsta customer.

6. 12 Eost 2020 da 07:53 UTCresolved

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

1. 24 Gouere 2020 da 12:06 UTCidentified

   Starting 30 minutes ago, customers hosted at the South Carolina (US East 1) data center are experiencing outages. Kinsta is aware and is working to resolve. See more details here: https://status.kinsta.com/incidents/8qzy95tr7knd.

2. 24 Gouere 2020 da 13:23 UTCresolved

   All customer sites have been restored.

1. 21 Mae 2020 da 19:14 UTCidentified

   A few customer websites are currently offline due to an outage at Iowa data center. Kinsta is working to restore affected websites.

2. 21 Mae 2020 da 20:49 UTCresolved

   All affected sites have been restored.

1. 31 Here 2019 da 12:58 UTCidentified

   A number of websites hosted at Kinsta's Iowa datacenter are currently offline. This is a known ongoing issue: https://status.kinsta.com/incidents/9phncbhccc6w. They are working to restore the affected websites.

2. 31 Here 2019 da 16:44 UTCresolved

   Kinsts is reporting the issue has been resolved.

1. 8 Here 2019 da 16:12 UTCidentified

   A number of customers that are hosted with Kinsta at the Northern Virginia (US East 4) location have just gone offline. Kinsta is working to restore the affected websites.

2. 8 Here 2019 da 16:39 UTCidentified

   Kinsta engineers are actively working to restore the affected websites: https://status.kinsta.com/incidents/7379hfj1mrk3. At this time I do not have an ETA for when it will be resolved.

3. 8 Here 2019 da 17:15 UTCresolved

   All websites have been restored.

1. 2 Mezheven 2019 da 21:26 UTCinvestigating

   Beginning an hour ago a major outage affecting Google infrastructure is affecting most of customer websites. Both Kinsta and Google are working to restore the affected regions. See more details on the incident here: https://status.kinsta.com/incidents/0mc8tyyywlj6.

2. 2 Mezheven 2019 da 21:38 UTCidentified

   Google believes they have identified the root cause and is expecting services to return to normal here shortly: https://status.cloud.google.com/incident/compute/19003.

3. 2 Mezheven 2019 da 23:14 UTCidentified

   At this time most websites have been restored. The remaining offline sites are expected to be restored shortly.

4. 3 Mezheven 2019 da 02:05 UTCresolved

   Last remaining websites have been fully restored.

1. 30 Ebrel 2019 da 18:32 UTCinvestigating

   A number of websites located on the Northern Virginia (US East 4) datacenter are currently offline resulting in 502/504 errors. Kinsta is investigating. Appears to be an outage with the datacenter.

2. 30 Ebrel 2019 da 18:36 UTCidentified

   Most websites are already restored. The remaining should be back within the next few minutes.

3. 30 Ebrel 2019 da 18:45 UTCidentified

   The host machine has been restored and all sites are back up and running.

4. 30 Ebrel 2019 da 18:51 UTCresolved

   This incident has been resolved.

5. 30 Ebrel 2019 da 18:51 UTCpostmortem

   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.