Web Hosting Packages

Basic: Upgraded from 500 MB to 1 GB
Prof: Upgraded from 1 GB to 2 GB
Large: Upgraded from 2.5 GB to 5 GB
XtraLarge: Upgraded from 10 GB to 20 GB

Reseller Hosting

Reseller 1: Upgraded from 5 GB to 10 GB
Reseller 2: Upgraded from 20 GB to 40 GB
Reseller 3: Upgraded from 100 GB to 150 GB

Cutting-Edge Technology & Ultimate Reliability

Our infrastructure has evolved to keep your business ahead. We started with traditional 10k SAS hard drives, upgraded to enterprise-grade SSDs, and today, our environment is powered by ultra-fast, datacenter-grade NVMe SSDs for maximum performance.Your peace of mind is our top priority. That is why we include Triple Datacenter Hosting as a standard feature. By replicating your data across three separate regional datacenters, we guarantee that your website and data remain fully available—even in the unlikely event of a localized outage.More speed, twice the space, and maximum uptime. Thank you for choosing us as your digital partner!

The published CVE describes a bug that allows a user with root or administrator privileges within a VPS to escape to the underlying host machine. This means that a VPS customer—either intentionally or unintentionally (for instance, as a result of compromised root access)—could gain access to the host, with all the associated security risks.

Proof-of-Concept Published

On Monday, July 6, 2026, at 18:00 (6:00 PM), the security researcher who originally reported the vulnerability published a proof-of-concept. This demonstration shows how a VPS can escape and cause the host machine to crash. An animated image (GIF) of this demonstration is available via the corresponding GitHub project: https://github.com/V4bel/Januscape

Patch Background

The underlying bug was already patched by Linux kernel developers on June 16, 2026. However, due to the extensive testing procedures of various Linux distributions, this patch was only widely rolled out in most cases over the past few days. Our distribution vendor made the patch available on July 7, 2026, at 16:46 (4:46 PM).

Our Response

Following a brief internal testing phase, we initiated the updates for our VM clusters in Amsterdam, Doetinchem, and Twente on July 7, 2026, at 17:45 (5:45 PM). This emergency maintenance was successfully completed at 23:00 (11:00 PM) that same evening.

Thanks to our ability to live-migrate VMs within the cluster, we were able to apply this update without any noticeable downtime. For most VMs, the impact was limited to just 100 to 200 milliseconds, spread across a migration process of approximately one minute.

Sources and References

    CVE-2026-53359 Detail Page (NVD): https://nvd.nist.gov/vuln/detail/CVE-2026-53359

    Original Report and Proof-of-Concept (Openwall oss-security mailing list): https://www.openwall.com/lists/oss-security/2026/07/06/7

    Proof-of-Concept Demonstration (GitHub, including GIF): https://github.com/V4bel/Januscape

Do you have any questions regarding this maintenance or its impact on your services? Please feel free to contact our support department.

For email, we recommend always using the SSL version of the mail server. Port 587 becomes 465, port 110 becomes 995, and port 143 becomes 993. Please note that you must also change the security method in your email program from None or TLS to SSL.

To restore FTP functionality, you can use the KPN guide below. We've outlined the steps here:

• Log in to your Experia Box modem.
• Go to the Security section.
• Change the firewall security level from the default setting Medium to Custom.
• Set the main switch next to Block Everything to Allow Everything.
• Change the TCP 20–21 FTP slider from On to Off (move it to the left).
• You will now have the same settings as the Medium firewall security level, with the only difference being that the outgoing FTP block has been removed.

Full guide:
https://community.kpn.com/kennisbank-modem-instellingen-171/modems-met-kpn-software-firewall-instellingen-614868

If you have any further questions or need additional assistance, please don't hesitate to contact us.

Traditionally, bots (like search engine crawlers) operate quietly in the background. They work step-by-step, limit their requests to a few per second, and back off if your server gets too busy. Today, the landscape has changed. With countless AI bots active simultaneously, some scrapers have become extremely invasive. They flood your server with multiple concurrent requests without any regard for your server's capacity or response time. When dozens of different AI companies do this at once, the impact multiplies. This sudden surge in traffic spikes your data usage, strains your infrastructure, and can cause your website to slow down or even crash.

Fortunately, you don’t have to let bots ruin your website's performance. IceHosting offers two powerful ways to regain control. The first is robots.txt, a file that gives instructions to visiting bots. However, rogue AI bots frequently ignore these guidelines. The second, more robust solution is .htaccess, which completely blocks bots based on their unique user-agent identification. With .htaccess, you can even set custom rules to restrict access to specific actions or pages. Want to secure your server? Reach out to our support team today for expert guidance!

Here is a practical example of how to block aggressive AI bots using your .htaccess file:

# BLOCK AI BOTS 
 
RewriteEngine On 
RewriteBase / 
RewriteCond %{HTTP_USER_AGENT} ^.*(GPTBot|ChatGPT-User|ClaudeBot|Claude-Web|anthropic-ai|CCBot|Google-Extended|PerplexityBot|Bytespider|Diffbot|FacebookBot|Meta-ExternalAgent|Amazonbot|cohere-ai|YouBot|Omgilibot|ImagesiftBot|Applebot-Extended|SemrushBot).*$ [NC] 
RewriteRule .* - [F,L] 

Keep in mind: The AI Trade-off

Blocking AI bots protects your resources, but it comes with a strategic catch. If you block all bots, your business won't be included in future AI datasets. This hurts your Generative Engine Optimization (GEO), meaning AI tools like ChatGPT won't find information about your brand, making them less likely to mention or recommend you to users. That is why we recommend implementing these blocks only if your server is actively struggling with bot traffic.