Greenhost Outage History

Greenhost is up right now

Greenhost had 12 outages in the last 2 years totaling 5408h 29m of downtime, averaging 0.5 incidents per month.

There were 12 Greenhost outages since November 22, 2024 totaling 5408h 29m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.greenhost.net

Minor September 24, 2026

Serious Wordpress vulnerability published, update advised

Detected by Pingoru
Sep 24, 2026, 03:37 PM UTC
Resolved
Sep 24, 2026, 03:37 PM UTC
Duration
–
Timeline · 1 update
  1. resolved Sep 24, 2026, 03:37 PM UTC

    A new Wordpress vulnerability has recently been published. Although it is unlikely this vulnerability can be (ab)used on our hosting packages, we still recommend updating any Wordpress installations you may have. More information about this bug can be found on: https://securityaffairs.com/199564/hacking/cve-2026-87902-how-close-is-your-wordpress-to-remote-code-execution.html Technical details are in: https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-7hp8-65ch-5whp

Read the full incident report →

Minor August 28, 2026

Outage on small number of Hosting packages

Detected by Pingoru
Aug 28, 2026, 07:00 AM UTC
Resolved
Aug 28, 2026, 07:00 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Aug 28, 2026, 07:00 AM UTC

    Due to failures in one of our proxy servers and in our monitoring, there was a partial outage on a limited number of hosting packages. As a result, some websites may not have been available over HTTPS. This issue started around 7 CEST, and all systems were restored around 9:00 CEST.

Read the full incident report →

Minor July 19, 2026

Mitigation of WordPress vulnerabilities

Detected by Pingoru
Jul 19, 2026, 12:35 PM UTC
Resolved
Oct 21, 2026, 03:52 AM UTC
Duration
93d 15h
Timeline · 3 updates
  1. investigating Jul 19, 2026, 12:35 PM UTC

    Two vulnerabilities allowing remote code execution have been recently identified in WordPress. Given their severity, we have taken measures to prevent our webhosting customers' website from being exploited. This might break some websites features; namely requests whose path contains `wp-json/batch/v1` or `rest_route=/batch/v1` will return a 403 error code. If you run WordPress on your website, please upgrade to version 6.9.5 or 7.0.2 as soon as possible. This link provides more information on the vulnerability itself: https://thehackernews.com/2026/07/new-wp2shell-wordpress-core-flaw-lets.html

  2. monitoring Jul 20, 2026, 11:09 AM UTC

    At this moment, we are investigating the impact this vulnerability had on our customer's websites. Yesterday (19-07), the vulnerability has been sealed through a temporary measure on our side, but a number of Wordpress installations has been vulnerable for some time. We will inform the affected customers with by e-mail later today. If you did not receive an e-mail by tomorrow morning, we do not believe your account to be at risk. However, we still advise to make sure your Wordpress is up-to-date with the latest version. If you are running Wordpress on a VPS, we can not verify if your Wordpress has been vulnerable.

  3. monitoring Jul 24, 2026, 01:01 PM UTC

    Further research has shown that attackers only reached our servers after 18-07-2026, 00:00. We also learned from many customers that auto-updates for their website already took place in the evening of 17-07. If the update took place before attackers reached our platform, this means your website has not been vulnerable. If you check your Wordpress logs and you find that auto-updates to WordPress version 7.02 indeed already took place on 17-7 in the evening, chances of your site being hacked are minimal.

Read the full incident report →

Minor June 19, 2026

Phishing attack this morning

Detected by Pingoru
Jun 19, 2026, 11:00 AM UTC
Resolved
Oct 21, 2026, 03:54 AM UTC
Duration
123d 16h
Timeline · 3 updates
  1. investigating Jun 19, 2026, 11:00 AM UTC

    We’re currently investigating reports of a phishing attempt. A large number of e-mails has been sent in our name, with a subject containing: "Nieuwe domeininstellingen versie 19.02 beschikbaar" These message are not sent by us. Please delete without opening.

  2. identified Jun 19, 2026, 12:25 PM UTC

    We have found that the phishing link refers to a website impersonating our login site. We have contacted both the host of that page, and the provider where the e-mails originated from.

  3. monitoring Jun 19, 2026, 01:50 PM UTC

    We identified the e-mailboxes hosted with us that received these e-mails. We will be sending them a separate message in the coming hour. If your e-mail is not hosted with us, you may also have received the phishing e-mail. The advice remains to delete the email without opening. If you did open the email and provided login credentials, please contact us, so we can advise you further.

Read the full incident report →

Minor February 16, 2026

Microsoft refuses e-mails sent from our platform

Detected by Pingoru
Feb 16, 2026, 09:21 AM UTC
Resolved
Feb 23, 2026, 09:20 AM UTC
Duration
6d 23h
Timeline · 6 updates
  1. investigating Feb 16, 2026, 09:21 AM UTC

    We’re experiencing a service outage with the mail platform. Microsoft is refusing e-mails sent from our platform. This includes e-mails sent to @hotmail.com, @outlook.com and @live.com e-mail addresses. Our team is currently working to restore the service. We apologize for any inconvenience.

  2. identified Feb 16, 2026, 01:01 PM UTC

    update 14:00 We have been working throughout the morning to sort this problem out. Microsoft is telling us that they see no reason why emails from our platform would not arrive, yet we still see e-mails being refused. We will continue trying to solve this as soon as possible.

  3. identified Feb 16, 2026, 02:11 PM UTC

    We have reached out to Microsoft several times this morning, as their mailservers claim that our servers are on their internal blocklist. We have asked Microsoft to remove us from this blocklist, but here they respond that we are not on their blocklist. In the meantime, e-mails are still being refused. Our further request to Microsoft to investigate this has of yet not been answered to. We will keep communicating with them, and keep you updated. In the meantime, we will be sending e-mails through a different method to evade the blocklist. A downside of this method is that there is a higher likelyhood of messages arriving in the recipients spamfolder. We will therefore revert to normal operations as soon as possible.

  4. monitoring Feb 16, 2026, 02:21 PM UTC

    update 15:18 The new method appears to work: We see new messages sent to Microsoft e-mail addresses successfully delivered to and accepted by Microsoft servers. Keep in mind that these messages may end up in the spam-folder of the recipients.

  5. resolved Feb 16, 2026, 04:35 PM UTC

    Update 17:32 Our workaround appears to be successful. We will keep watching the situation closely.

  6. resolved Feb 23, 2026, 09:20 AM UTC

    The workaround has been reverted. We are now sending e-mails to Microsoft customers through our regular platform again.

Read the full incident report →

Minor February 9, 2026

Some shared hosting affected by storage layer issue [fixed]

Detected by Pingoru
Feb 09, 2026, 06:51 AM UTC
Resolved
Feb 09, 2026, 06:51 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Feb 09, 2026, 06:51 AM UTC

    Due to an issue with a (bridge) server between our storage layer and shared web hosting platform, about ~20% of the websites hosted on our platform experienced issues between 07.05 and 07.12. The issue is solved, we are still investigating the root cause.

Read the full incident report →

Minor November 24, 2025

Shared hosting outage 24-11 solved

Detected by Pingoru
Nov 24, 2025, 10:26 PM UTC
Resolved
Nov 24, 2025, 10:26 PM UTC
Duration
–
Timeline · 1 update
  1. resolved Nov 24, 2025, 10:26 PM UTC

    Last night we experienced a minor service outage on our storage platform. As a result, a small part of our hosting customers may have experienced a few minutes of downtime. The issue was solved within 10 minutes.

Read the full incident report →

Minor May 7, 2025

Network issue

Detected by Pingoru
May 07, 2025, 11:53 PM UTC
Resolved
May 07, 2025, 11:53 PM UTC
Duration
–
Timeline · 1 update
  1. resolved May 07, 2025, 11:53 PM UTC

    Due to a network maintenance we have had unexpected degraded network connectivity from 1:05 until 1:42 CEST. The issue is now solved.

Read the full incident report →

Minor April 11, 2025

Backups unavailable [fixed]

Detected by Pingoru
Apr 11, 2025, 12:11 AM UTC
Resolved
Apr 11, 2025, 12:11 AM UTC
Duration
–
Timeline · 1 update
  1. resolved Apr 11, 2025, 12:11 AM UTC

    Due to network issues, the connection to our backup location is not functional. As a result, backups are currently not available. We are working with our network suppliers to find a solution. [Update 02:19 CEST] The underlying issue is unannounced maintenance on a (dedicated) fiber connection. The maintenance should be completed before 6.00 AM. [Update 06:00 CEST] The services are back online. It is possible backups not all backups of last night completed due lack of connectivity during the maintenance.

Read the full incident report →

Minor November 22, 2024

Mail platform outage (SOLVED)

Detected by Pingoru
Nov 22, 2024, 01:27 PM UTC
Resolved
Nov 22, 2024, 01:40 PM UTC
Duration
13m
Timeline · 2 updates
  1. investigating Nov 22, 2024, 01:27 PM UTC

    We’re experiencing a service outage with the mail platform. As a result it may not be possible to access all mailboxes at this point. Our team is currently working to restore the service. We apologize for any inconvenience.

  2. resolved Nov 22, 2024, 01:40 PM UTC

    All services should be accessible again

Read the full incident report →