Since Tuesday evening, February 24th, at 8 PM, we've been experiencing slower email delivery to Microsoft mail servers. This is impacting both consumer mailboxes (outlook.com, live.com, hotmail, msn, and other free mailboxes) and Microsoft 365 email services.

The outage is occurring at Microsoft. Several European mail server administrators have reported this on Microsoft's forums:
https://learn.microsoft.com/en-us/answers/questions/5786144/all-sending-ips-temporarily-rate-limited-(451-4-7?page=2#answers

We've contacted Microsoft support, but there's no resolution yet.

We'll continue to monitor this.

Update February 27 - 9:00 AM: We've seen a slight improvement in email delivery since this morning. The email queue has shrunk this morning, but there are still a lot of emails in the queue, resulting in slower delivery to Microsoft mail servers.

Update February 27 - 3:00 PM: All emails have been delivered from the queue.  We will keep monitoring this in the next days.

On Wednesday, December 17th, between 10:00 PM and 11:00 PM, we will be performing maintenance on the network in our two Brussels data centers. During this maintenance period, there will be a brief interruption of 15-30 seconds, during which the internet connection will be lost. Websites en online applications that are hosted in Brussels will be unavailable for this short time.

The maintenance is necessary to optimize the network.

We will monitor all services during and after the maintenance and will be in constant contact with the data center team.

There was a short network issue in the datacenter in Brussels with the connection to the internet.

The issue has now been resolved by switching traffic to an alternative provider.

We are still investigating the root cause and are following up.

We're currently experiencing a delay in the delivery of emails from Microsoft's free email services to addresses ending in @hotmail.com, @hotmail.be, @outlook.com, or @msn.com.

A support case has been opened with Microsoft to investigate and resolve the issue.

Update 11:00 AM: There's no update from Microsoft yet, but we're seeing more emails being delivered and that emails in the queue are gradually being delivered. However, it may take several hours for all emails in the queue to be processed.

Update 1:00 PM: All new emails are being delivered immediately to their recipients on Hotmail, MSN, and Outlook.com. We're also seeing the queue shrink. At the current rate, it could take several hours for all emails in the queue to be delivered.

Update 3:30 PM: We haven't received any feedback from Microsoft about a solution. The email queue is slowly shrinking, though.

There is currently an issue in the Brussels data center, causing several servers and websites to be inaccessible. We are currently investigating the problem. Initial analysis indicates an interruption in DSTNY's network. DSTNY engineers are helping to investigate the problem. We will post regular updates here as more information becomes available.

Timeline

Update 11:05 AM: DSTNY engineers are helping to investigate the problem.
Update 11:15 AM: DSTNY has confirmed a network issue due to a broadcast storm, making parts of the DSTNY network inaccessible.
Update 11:35 AM: Most parts of the network are now fully accessible again, but the main impact is still on the shared hosting servers.
Update 12h10 : Gradually more servers are coming back online.
Update 1:00 PM: Most servers are now available again. Engineers continue working to get the last few servers working properly again.
Update 2:10 PM: All servers are now available again. We are still conducting further checks to ensure everything is working properly.

On September 12th, we will move the reseller hosting servers to a new hardware platform. The migration will take place between 4:00 AM and 7:00 AM. There will be some downtime for the websites and databases hosted on the servers during the migration.

We are migrating the servers for three reasons:

• A new storage platform that is faster and more secure due to additional redundancy.
• Older servers will be replaced with new, faster hardware.
• We are switching management software from onapp to proxmox. At proxmox, we are primarily focused on the future and see many more developments and technical possibilities.

We will be moving these servers:

• plesk01 (approximately 30 minutes of downtime)
• plesk02 (approximately 30 minutes of downtime)
• reseller03 (approximately 30 minutes of downtime)

The servers will be exported one by one on onapp and then imported into proxmox. All technical settings, IP addresses, firewall rules, etc., will be transferred. There will be approximately 30 minutes of downtime per server.

We will perform the migration between 4:00 AM and 7:00 AM to minimize disruption to visitors. A temporary, neutral maintenance page will be displayed during the migration.

Between September 8th and 10th, we will be moving some shared hosting servers to a new hardware platform. The migration will take place between 4:00 AM and 7:00 AM. There will be downtime for the websites and databases hosted on the servers during the migration.

We are migrating the servers for three reasons:

• A new storage platform that is faster and more secure due to additional redundancy.
• Older servers will be replaced with new, faster hardware.
• We are switching management software from OnApp to Proxmox. At Proxmox, we are primarily focused on the future and see many more developments and technical possibilities.

On September 8th, between 4:00 AM and 7:00 AM, we will be moving these servers:

• Apache21 (approximately 30 minutes of downtime)
• MySQL15 (approximately 30 minutes of downtime)
• MySQL17 (approximately 30 minutes of downtime)
• MySQL05 (approximately 30 minutes of downtime)
• MySQL01 (approximately 30 minutes of downtime)

On September 9th, between 4:00 AM and 7:00 AM, we will be moving these servers:

• Apache27 (approximately 30 minutes of downtime)
• Apache28 (approximately 30 minutes of downtime)
• Apache20 (approximately 30 minutes of downtime)
• MySQL03 (approximately 30 minutes of downtime)

On September 10th, between 4:00 AM and 7:00 AM, we will be moving these servers:

• Shared-IIS01 (approximately 30 minutes of downtime)
• Shared-MSSQL01 (approximately 30 minutes of downtime) (30 minutes of downtime)
• Reseller04 (approximately 30 minutes of downtime)
• Spamexperts001 (approximately 30 minutes of downtime)

The servers are exported one by one on onapp and then imported into proxmox. All technical settings, IP addresses, firewall rules, etc., are transferred. This will result in a downtime of approximately 30 minutes per server.

We have already migrated over 200 servers. This process is largely automated.
We perform the migration between 4:00 AM and 7:00 AM to minimize disruption to visitors. A temporary, neutral maintenance page will be displayed during the migration.

On Monday, September 8th, we will be performing maintenance on the mail server mail06.cloudemail.be between 9:00 PM and 10:00 PM (CET). During the maintenance, there will be a brief downtime for the mail service for mailboxes connected to the server mail06. This means you will temporarily be unable to receive or send emails. Your email program may display an error message during the maintenance. If you are still receiving errors after 10:00 PM, please shut down your email program completely and restart it.

No emails will be lost during the maintenance. Emails that arrive during the maintenance will be temporarily stored on the spam filter servers. After the maintenance, these emails will be automatically delivered to your mailbox.

The maintenance is necessary to expand the server's capacity.

We are aware of an issue with some of the cloud servers in our Brussels data center.
We are investigating the problem and will provide a solution as soon as possible.

Update 1:54 PM: We are rebooting the affected servers one by one, after which the services should be available again.
Update 2:20 PM: All servers have been rebooted and services are back online. We continue to monitor.

On Tuesday June 24th between 4:00 and 7:00 in the morning we will move the reseller01 server to a new hardware server and a new storage platform. This will cause a downtime of approximately 30 minutes on the websites hosted on these servers between 4:00 and 7:00 in the morning.

The migration is being performed to place the reseller01 server on modern state-of-the-art hardware, which will make websites, webshops and online applications hosted on this server work faster and more reliably.

On Monday 16 June from 21h we will transfer the mail servers mail03 and mail04 to new hardware. This may cause a temporary interruption where you will not be able to connect to your mailbox via webmail or an email program on your computer and smartphone. No emails will be lost during the maintenance. Emails that arrive during the maintenance will be delivered to your mailbox immediately after the maintenance.

We expect the move to be completed by 23h.

Update 21h00 : maintenance has started.

Update 21h30 : the migration for mail04 is finished. we are now starting with mail03.

update 22h00 : mail03 is now also finished. All tests are going well. We see new mails coming in and out smoothly. the control panel is also working well. we will continue to monitor, but for now everything looks good.

Since this morning, some customers are experiencing connection problems when sending emails via cloudemail.be.

We are seeing a very large number of login attempts coming to our mail servers for non-existent email addresses. These login attempts come from thousands of different locations and from different countries. Due to this abundance of login attempts, legitimate customers are temporarily unable to connect for short periods of time and therefore cannot send emails.

Update 10:30: We are currently blocking all login attempts from outside the Benelux. Customers outside the Benelux can still use the webmail at https://cloudemail.be.

Update 12:30: We are gradually and controlledly unblocking other countries and networks. Connections are now possible again from France, Germany and Great Britain.

Update 16:30: The DDoS attack is still ongoing. We will continue to monitor this.

Update 6/6: The DDoS attack is still ongoing. We will continue to monitor this, but currently only individual IP addresses have been blocked from locations where the attack is being carried out. There are also no more known problems for users.

Update 7/6: The DDoS attack is still ongoing.

Update 8/6: The DDoS attack is still ongoing. We will continue to monitor this, but there should be no disruption to customers.

Update 8/6 - 17h: The DDoS attack has stopped since 14h. We no longer see any abnormal traffic on the mail servers. We will of course continue to monitor this. In the meantime, we have developed a plan that will allow us to act even faster in the future to block the attack and minimize the disruption to users.

Since Saturday, March 1, we have seen a delayed delivery of emails to icloud.com and me.com addresses. The delay in the delivery of the emails can be up to several hours.

Update 03/03/2025: We have contacted Apple, the operator of icloud.com and me.com, but without result so far.

Update 06/03/2025: We have received a response from Apple, in which they indicate that delivery should now run more smoothly. We do indeed see that more emails are being delivered for icloud.com and me.com mailboxes and that the number of emails in the queue is decreasing.

We will follow this up further.

Some of our customers are reporting that they are getting an error message when sending emails via cloudemail.be: 554 5.7. 1 Service unavailable; Client host [185.179. 91. 150] blocked using sbl.spamhaus.org; Error: open resolver;

We are investigating this further and will implement a solution as soon as possible.

16h20 : The problem is limited to 2 nodes in the cloudemail-cluster: mail05 and mail06. We are investigating and monitoring. 
16h45 : The problem has been identified and the configuration of the mailserver mail05 and mail06 has been modfied. We are currently monitoring to see if this has resolved.
17h00 : All email are processed correctly now.

There is a network problem in the datacenter in Brussels since 21h05, causing a large number of servers to be slower or temporarily inaccessible. The datacenter team is investigating the cause. Then preliminary analysis shows that the cause is a DDoS attack.

Timeline

21h05 : our monitoring notices that there is a problem with the different servers and websites.
21h15 : escalation to the datacenter engineers.
21h45 : engineers are still investigating the issue.
22h15 : We still see sites being temporarily inaccessible for short periods of time. we escallated the issue to the management of the datacenter.
22h45 : the attack is still ongoing. network engineers are working towards a solution.
23h00 : our monitoring indicates that the issue is resolved, but we have no confirmation from the engineers at the datacenter atm.
23h10 : engineers in the datacenter confirm that the issue is resolved.

On Tuesday, September 10th, between 10 AM and 12 PM, urgent maintenance will be carried out on one of the hardware nodes (HV12) in our private cloud environment in Brussels.

It has been determined that one of the fiber optics cards on this hardware node is defective, resulting in reduced redundancy. During the maintenance, this card will be replaced.

These fiber optics cards are configured redundantly. All necessary precautions are being taken to ensure that replacing the card will not impact the operation of the cloud servers on HV12.

Customers who have a cloud server on HV12 have received individual communication.

The following shared hosting servers are hosted on HV12:

• no-one-cs97-reseller04
• no-one-cs66-reseller03
• cs-one-mysql15
• cs-one-mysql01
• cs-one-cloudemail04
• cs-one-apache20
• cs-one-apache09

We are doing everything possible to minimize disruption during the maintenance.

A problem has occurred on the storage system in the Amsterdam data center, causing the disks of the cloud servers to be set to read-only.

This has impacted some customers with a Cloud Server hosted in the Amsterdam data center and customers who have their website on apache14 and apache15.

We have escalated the problem to the data center administrator.

Update 13h51 : A first analysis by the datacenter team shows that the problem is related to a hardware problem.

Update 14h28 : The impacted servers will be rebooted one by one, after which the services will be available again.

Update 15h50 : Most servers are back online again. For those that are still down, we expect them to be online again soon.

Update 16h : All servers are back online.

There is currently an issue where a small number of customers are experiencing a timeout when sending and receiving emails. We are investigating the problem and will correct it as soon as possible.

10h30 : The issue has been identified and a correction has been applied. Within 30 minutes the problem should be resolved for all customers.

On Thursday 07/03/2024 between 07:30 and 09:00 CET, there will be maintenance by DNS Belgium on the .be registration platform. This will cause a downtime of approximately 2 times 30 minutes. During that time it will be impossible to check if a .be domainname is available for registration, start a new domainname registration or start a transfer, change nameservers, change contacts,...

There is currently an issue in the datacenter in Brussels, affecting the hypervisors HV-09 and HV-08. Due to this 50 of our (virtual) servers are down.

All servers and services are checked and should be available again.

Timeline

• 20h : all servers are running. All services should be up again.
• 19h35 : We are booting all cloud servers.
• 19h20 : The startup procedure is still running.
• 18h50 : The hardware is beïng restarted in the datacenter. Due to the complexity may take more that 30 minutes. We will provide an update in 30 minutes.
• 18h30 : The datacenter engineers are still looking for a solution.
• 18h00 : An engineer is currently assessing the situation in the datacenter.
• 17h15 : The problem is escalated to the datacenter. After initial investigation there seems to be al general issue in datacenter.
• 17h05 : Our monitoring detects that there is an issue in the datacenter in Brussels. 

Since Sunday morning at 3 am, there is an error when activating email on new domain names. The error occurs after an update of the spam filter software on one of the nodes (node1) of the spam filter cluster. Due to the update, the control panel of the spam filter software and the API are not available. This prevents any changes from being made to the spam filters.

The error has been escalated to the software vendor.

There is no problem with the delivery of both incoming and outgoing mails, but as a precaution we have removed node1 from the cluster. The delivery of the emails is now running via the 5 other nodes in the cluster.

We try to solve the problem as soon as possible.

UPDATE 18h50 : The softwarevendor applied a patch. The API and control panel are available again.

Our monitoring detected a hw failure on hardware machine HV11. This causes downtime for cloud servers of customers.

We are migrating the cloud servers to other hardware machines.

Update 18h: all cloud servers have been migrated and are started. All issues have been resolved.

On friday 28th of april, we will be conducting maintenance on the network in the Amsterdam datacenter between 1 AM and 7 AM.

The maintenance is needed to improve the networking inside the datacenter. We aim to minimize the impact for the servers, but there may be a connectivity disruption for about 2 minutes per cloud server.

Our monitoring noticed network issues in our datacenter in Amsterdam. Some servers and services are slower or the connection to the internet is unavailable due to a DDoS attack.
Alle servers are available again.

Timeline

• 13h23: our monitoring detects that some servers in our datacenter in Amsterdam are unavailable.
• 13h29: the problem is escalated to the datacenter.
• 13h45: we are still working to resolve the issue.
• 13h55: Most servers are reachable again, but the situation is not stable at this time.
• 14h15: Most servers and services are available again, but there may be intermittent issues. We keep monitoring the situation.
• 15h05: All servers are available again, except for 1 server (apache17.websrv.be). We are trying to resolve this issue as soon as possible.
• 18h30: we are still working to resolve the issue with apache17. This server is currenlty only available over IPv6.
• 20h30: we are still following up with the staff in the datacenter. 
• 23h: The webserver apache17 is now reachable from the internet. There may be short interuptions.
• 8h20: The webserver apache17 is now also available. We will keep monitoring.

On october 17th there will be a firmware upgrade on the blade enclosures in the Zaventem datacenters. These enclosures hold the blades HV08, HV09, HV10 and HV11. The upgrades ensure the stability, security and performance of the hardware platform.

There is no downtime expected. Users may notice a (very) short network hiccup. We will do everthing to make sure that there is no impact on our services, by performing this maintenance at night.

At 12h03 our monitoring detected an issue with some virtual machines on the hardware node HV10.

During a first investigation there is an indication that a hardware failure is causing the issue. In the datacenter there was an attempt to do a reboot of the hardware machine, but that attempt failed. The hardware vendor - HPE - will also start an intervention soon.

All services are operational again

We will send a a full post incident report to customers with cloud servers that were impacted by this incident.

History

Update 13h50 : we are still investigating.

Update 14h30 : HPE has sent technicians to the datacenter to resolve the hardware problem.

Update 15h25 : De software of the virtualisation software is developing a work-around, so we can move the virtual machines. 

Update 15h45 : We are migraring the virtual machines one-by-one to other hardware. The first machines are back online.

Update 16h20 : Most servers are migrated to other hardware nodes and are running.

Update 16h45 : All virtual servers have been migrated to other hardware nodes.

Update 20h00 : The hardware node HV10 is not repaired by an engineer of HPE. All tests are succesfull and HV10 is re-integrated in the cloud cluster. We will be moving some non-critical servers to HV10. We will be monitoring this very closely.

On wednesday august 17th, between 4 am and 8 am, we will install software updates for the operating system and system software, in order to keep your files, emails and data on our servers safe. These updates will solve (critical) software vulnerabilities and optimize the performace of the server system.

The maintenance will be performed on all linux webhosting servers (apache01 to apache16), the database servers (mysql01 to mysql09), the cloudemail.be-environment and the nameservers (ns1 to ns5).

During the maintenance period there may be short service disruptions. We will try to minimize the nuissance to a minimum.

We will be upgrading our 3PAR systems in the Diegem data centre with recommended patches.

All cloud servers and shared servers in the Brussels datacenters use the 3PAR SAN. During this maintenance there will be less redundancy. We do not expect that there will be impact on the availability and performance of the servers, as the 3PAR SAN’s are highly redundant.

We will be upgrading our 3PAR systems in the data centre in Zaventem with recommended patches.

All cloud servers and shared servers in the Brussels datacenters use the 3PAR SAN. During this maintenance there will be less redundancy. We do not expect that there will be impact on the availability and performance of the servers, as the 3PAR SAN’s are highly redundant.

DNS Belgium plan to do maintenance on Tuesday 21/06/2022 for the .be registration platform.

This will cause a downtime on these services during the maintenance window :

• Check if a .be domain is available
• registration or transfer of .be domains names
• changes in the contacts or nameserver configuration

During this time window there will be no zone-file updates. Changes will be queued and processed after maintenance ends.

The nameserver of DNS Belgium are not impacted by this maintenance, so all .be domain names will remain active during the maintenance.

This week we will perform firmware upgrades on hypervisors HV04, HV06, HV10 and HV11 to keep them secure and fast-performing.

In order to upgrade the hypervisors we well empty the hypervisors one-by-one via a livemigrate of the cloud servers to another hypervisor. There will be no downtime for the cloud servers and the hosted services on them, however there may be a performance loss for a few minutes during the livemigration. The migration of the cloud servers will be performed outside peak-utilisation hours as much as possible.

• HV04 will be upgraded on friday april 8th, starting at 9h.
• HV06 will be upgraded on tuesday april 12th, starting at 9h.
• HV10 will be upgraded on wednesday april 13th, starting at 9h.
• HV11 will be upgraded on thursday april 14th, starting at 9h.

After the upgrades and tests, the cloud servers will be replaced on the upgrades hypervisors.

On tuesday april 12th, between 4 am and 6 am, we will install software updates for the operating system and system software, in order to keep your files, emails and data on our servers safe. These updates will solve (critical) software vulnerabilities and optimize the performace of the server system.

The maintenance will be performed on all linux webhosting servers (apache01 to apache16), the database servers (mysql01 to mysql09), the cloudemail.be-environment and the nameservers (ns1 to ns5).

During the maintenance period there may be short service disruptions. We will try to minimize the nuissance to a minimum.

Recently we have faced network issues in the core network in the Stuart datacenters and these issues have been investigated together with our vendor. The conclusion is that we were facing a bug in the switches that causes conflicts with virtual & physical port numbers. These bugs with be fixed in a future releases.

In the meanwhile Stuart will implement a workaround to mitigate this bug and avoid further issues. On a later moment when a bug fix is released by the vendor, we will patch our core switches.

In the maintenance performed today we will make some physical changes with the related configuration changes as a workaround to avoid the bug to trigger in the future. There should be no impact, unless the bug triggers while fixing. In case we see impact on the network during this maintenance, we will fix this immediately.

Our monitoring picked up on a networking issue in the datacenter in Sint-Lambrechts-Woluwe. This causes some servers to be unreachable from the internet. A preliminary analysis indicated that the issues originate from the core-routers in the datacenter.

Engineers in the datacenter are investigating the issue and working on a solution.

• 9h41 : Most servers are available again. A limited number of servers show issues.
• 12h03 : All issues are not fully resolved. There is still a small number of servers that has issues with connecting to the network. Engineers keep working on a definitive solution.
• 15h25 : There are still some issues with the network. A small number of Windows servers has issues with connecting to the network. Shared hosting servers and the email-servers are fully functional. Engineers keep working on a definitive solution.
• 18h08 : Engineers keep working on a definitive solution.
• 20h01 : Engineers keep working on a definitive solution.
• 21h22 : All servers are reachable now. 
• 22h30 : Some servers are offline.
• 23h11 : all servers are reachable again.

At 20h55 our monitoring system detected a network issue in the datacenters in Nossegem and Sint-Lambrechts-Woluwe. This causes servers to react slower of they have become completely unavailable.

The problem has been escalated to the datacenter where engineers are working to resolve the issue as fast as possible.

21h57 : most servers are available again, but we still see some instability on the network.

22h36 : all servers are available again. We continue to monitor.

This week we will perform firmware upgrades on hypervisors HV07, HV08 and HV09 to keep them secure and fast-performing.

In order to upgrade the hypervisors we well empty the hypervisors one-by-one via a livemigrate of the cloud servers to another hypervisor. There will be no downtime for the cloud servers and the hosted services on them, however there may be a performance loss during the livemigration. The migration of the cloud servers will be performed outside peak-utilisation hours as much as possible.

• HV07 will be upgraded on tuesday  januari 11th, starting at 10h.
• HV08 will be upgraded on wednesday januari 12th, starting at 10h.
• HV09 will be upgraded on thursday januari 13th, starting at 10h.

After the upgrades and tests, the cloud servers will be replaced on the upgrades hypervisors.

To maximize the reliability and performance of our shared hosting environment, we will move some of our shared hosting servers to a new storage environment.

The move will take place in the night of sunday october 17th and monday october 18th, starting at midnight CET. There will be a downtime for the websites hosted on our servers. The downtime will be 30 tot 60 minutes per server, depending in the size of the disks in the virtual machines. We expect all machines to be moved by 6h.

These servers will be moved:

• cs-one-apache06.websrv.be
• cs-one-apache07.websrv.be
• cs-one-apache08.websrv.be
• cs-one-apache10.websrv.be
• cs-one-apache11-su
• cs-one-apache12-sj
• cs-one-mssql03.websrv.be
• cs-one-webfarm-lb01

On October 7th between 4AM and 7AM we will install a security patch for apache servers that are currently running Apache v 2.4.49. This patch should fix the security flaw CVE-2021-41773 (https://httpd.apache.org/security/vulnerabilities_24.html#CVE-2021-41773)

There might be a short service disruption of a few minutes at the moment the apache-server is restarted.

On tuesday september 28th, between 4h and 6h in the morning, we will update our shared hosting environment with the latest security patches and the latest updated versions of the operating system and software components (like apache, mysql, varnish,...). To activate the new sotware versions a restart of the servers is neccessary. Websites hosted on these servers can be unavailable during the maintenance windows for a few minutes.

This maintenance is performed every two months and is necessary to keep all services secure, fix issues, roll out new features and optimize performance.

On Wednesday September 8th, between 23h and 3h, there will be a migration to a new networkinfrastructure in the datacenters of Nossegem and Sint-Lambrechts-Woluwe of the hypervisors HV8, HV9, HV10 en HV11.
Because the migration will also impact the storage network, we will - as an abundance of caution - shut down the cloud servers. After the migration the servers will be booted. This is to avoid possible corruption of the disks of the cloud servers.
There will be a downtime of 30 to 60 minutes.
We will notify all customers with impacted cloud servers with an individual communication.

Update 1h30 : the maintenance has been completed succesfully.

Currently we experience a DDoS attack on our nameservers. This may cause domain names to be unavailable.

We are blocking traffic to our nameservers from several countries. Traffic from Belgium, The Nethernlands, Luxemburg, France and Germany is allowed.

UPDATE 23h30: At this time traffic to most other countries (and the US) is possible again.

On july 1th we will perform a maintenance on our reseller servers (reseller01 and reseller02). During maintenance, the operating system and server software will be updated with security updates. After the installation, the servers will be rebooted. 

During the maintenance period there will be several minutes downtime of the websites and databases hosted within the reseller servers.

Maintenance is carried out between 4 a.m. and 6 a.m., so that disruption to you and your customers is limited. Thanks to maintenance, the hosted website and databases remain secure and fast.

On june 29th we will perform a maintenance on out Linux shared hosting servers (apache01 to apache14, mysql01 to mysql07). During maintenance, the operating system and server software will be updated with security updates. After the installation, the servers will be rebooted. 

During the maintenance period there will be several minutes downtime of the websites and databases hosted within the shared hosting environment.

Maintenance is carried out between 4 a.m. and 6 a.m., so that disruption to you and your customers is limited. Thanks to maintenance, the hosted website and databases remain secure and fast.

Since 10h43 we notice a problem in our network with higher packetloss for some international peering connections. Some websites may load slower than usual or expirience short interuptions for a small percentage of users. For users on local networks like Telenet or Proximus, there is no slowness.
We and our datacenter partner, are investigating the issue.

Update 12h : The issue has been resolved.
 

This afternoon a firedetector generated a false alert and activated the extinguisher system in the datacenter in Nossegem (Brussels). As a result and inert gas was released in the datacenter.
The release of the extinguishing gas triggered several harddisks to go into a safety mode. This has been detected for the os disks of 2 of the hypervisors (hv08 and hv09) in our private cloud infrastructure.
We want to fix this issues as soon as possible to guarantee the stability of our services. That is why we will perform an emergency maintenance this evening between 23h CET and 2h CET. During this maintenance we will shut down the cloud servers on hv08 and hv09 and boot them on another hypervisor.
Due to the shut down and reboot of the cloud servers there will be a downtime of a few minutes per cloud server.

Update 0h00 : Het maintenance has been completed succesfully. All servers are available again.

Due to a problem on the SAN there were 62 cloud servers with disks with read-only status. All servers are fully operational since 9h56 (Brussels time).
The issue is related to the same issue there was last week thursday may 27th.

History

• 8h11 : Disks of 62 servers go into read-only mode due an issue
• 9h56 : All 62 servers have been rebooted, have had a disk check and the services are checked.

Cause

HPE has confirmed that the issues is caused by a softwareproblem in their SAN. The problem is related to the garbage collection, which causes the disks on the SAN to fill up and no more data can be written to the SAN. This causes the disks of the cloud servers to go into read-only mode.
HPE has created a patch for this issue and is testing it. As soon as the patch become available, we will roll it out during a maintenance window.

Actions

Until the patch of HPE is available, we monitor the impacted LUN since thursday may 27th. At the time there is not enough storage available, we add addition storage to the LUN. This morning the LUN ran out of available space because of a high amount of "garbage" information that was suddenly added, because of intensive I/O actions. We are investigating how we can avoid this. 

We will also look at additional actions that we can take while waiting for the patch.

On May 27 at 9h46 a problem was detected with the storage system that caused disks to go read-only on some servers. As a result, information could no longer be written to databases and files. Some applications were inaccessible or gave error messages. After a reboot and disk check the servers were available again.
The problem occurred 4 times throughout the day.
There was impact on up to 62 servers. The problem was limited to 1 storage lun in the data center in Nossegem.
At 18h47 a workaround was implemented. Since then the situation is stable.

History

• 9h46 : Our monitoring system reports that the disks of dozens of servers have gone into a read-only mode. We immediately started investigating the issue and escalated it to the data center.
• 10h03 : After an initial analysis, it seems to be a temporary issue. We test with some test machines whether they reboot correctly.
• 10h11: We are restarting all impacted servers one by one, after which they will become operational again.
• 11h07 : All servers have now been rebooted and the disk checked. We are checking all services on the servers.
• 11h30: All servers have been checked and all services are available again.
• 14h06 : The problem occurs again. We commence restarting all machines.
• 15h30 : All machines have started up again and are checked.
• 16h05: The problem re-occurs. We are restarting all machines.
• 17h10: All machines have been restarted.
• 17h37: The disks go back to read-only. We start over with booting up and checking the servers.
• 17h40 : The root cause has been found. The necessary logs are collected to pass to the SAN vendor so that a definitive solution can be implemented.
• 18h47: A workaround has been implemented.

In the night of april 9th between 3:00 AM and 5:00 AM we will perform urgent maintenance tasks on the database server mysql03.websrv.be
During this maintenance, there will be an service disruption for the websites that use databases on the server mysql03.websrv.be. This may take about 30 minutes.
The intervention will also be performed on the replica-server mysql04.websrv.be. For this server there will be no impact on the hosted websites.

The maintenance is performed to impact the stability and performance of the databases.
 

In the night of februari 10th at 3:00 AM we will perform a maintenance tasks on the database server mysql01.websrv.be
During this maintenance, there will be an service disruption for the websites that use databases on the server mysql01.websrv.be. This may take 30 minutes.
The intervention will also be performed on teh replica-server mysql02.websrv.be. For this server there will be no impact on the hosted websites.

The maintenance is performed to impact the stability and performance of the databases.

On Saturday 31 October, we will perform maintenance on the nomeo control panel mijn.nomeo.be. As a result, there can be brief interruptions throughout the day when ordering, managing and setting up products and services. Please be patient and try again at a later time. There is no impact on the functioning of domain names, websites and servers.

During the maintenance our support teams will be available to answer your questions.

Maintenance is performed to improve performance, safety and stability.

On monday March 23rd between 20h and 23h there will be a maintenance on the Nomeo-website and mijn.nomeo.be. There will be no access to mijn.nomeo.be and it will not be possible to place new orders.

On March 10h we will perform a maintenance on hardware machines HV04 and HV06.

There will be no impact on the cloud servers that are hosted on these machines. We will migrate the cloud servers to other hardware nodes.

On March 3rd, between noon and 6 pm, we will upgrade our monitoring platform based on Zabbix. The upgrade itself will take approximately 30 minutes.

During the upgrade it will not be possible to log in to zabbix and there will be no new measured values temporarily.

The upgrade of Zabbix will ensure that the monitoring platform remains safe and efficient.

Op 22 januari, in de ochtend tussen 4 uur en 6 uur, zal er een onderhoud plaats vinden op de webbuilder editor server. Tijdens deze periode kan de webbuilder gedurende enkele minuten onbereikbaar zijn, waardoor je de website niet kan aanpassen.

De websites die gebouwd zijn met Webbuilder blijven tijdens het onderhouden wel bereikbaar.

Op 17 december om 20h zal er een firmware upgrade gebeuren van de hypervisor HV05. Die upgrade is een onderdeel van normaal, preventief onderhoud. Het lost fouten in de firmware op en is nodig om de stabiliteit en veiligheid te blijven garanderen.

Voorafgaand aan het onderhoud zullen we alle virtuele machines op HV05 verhuizen naar andere hypervisors, zodat er geen impact is voor de toepassingen en websites die we hosten.