If you’re a RIPE member and have your own IP prefix(es), you can bring your own IP addresses and we’ll announce them from our AS number. The service is available in Bucharest and London. In the following months it will also be available in Dallas and Fremont.
We can announce IPv4 and IPv6 for you.
This service is free if charge. Data traffic will be charged at usual rates.
You get the same benefits as in the previously opened locations (Amsterdam and Bucharest):
- blazing fast full SSD local storage
- brand new powerful Intel Xeon powered servers
- generous traffic included
- our fast and friendly 24/7 support for network, hardware and Fleio self-service portal
The virtual machines cost starts at one cent and half per hour for 2GB of RAM.
And some useful add-ons are available for the virtual machines:
- Windows license for less than a cent per hour
- affordable cPanel/WHM and DirectAdmin licenses
- affordable extra IPv4 addresses
The new platform will soon be available in London too.
This is a long, looong awaited feature:
Windows virtual machines are now available!
You can get a Windows Server 2016 Standard virtual machine with 2 GB of RAM for 2 cents per hour.
The Windows instances have the same, fast local SSD storage.
The current locations available are Amsterdam and Bucharest with more to come soon.
Today we are launching our new OpenStack based platform powered by Fleio.
We’ve updated all our OpenVZ nodes to fix the dirty cow vulnerability that was (re)discovered recently.
With this update another kernel issue was fixed and Ubuntu 16.04 is now available in all our locations.
After doubling the amount of guaranteed memory last November, we’re now increasing the monthly traffic with up to 100%:
- Starter package: increased monthly traffic from 1 TB to 2 TB
- Small package: from 2 TB to 3 TB
- Medium package: kept the 4 TB (sorry)
- Large: from 6 TB to 8 TB
The change applies for the current month as well.
We’ve doubled the amount of guaranteed memory for all virtual machines. This is already active for existing machines and no restart is required. We have also removed the “burst memory”, which is now guaranteed.
All other package characteristics have remained the same, including price.
If you happen to encounter any issue caused by the upgrade open a support ticket.
Today we started to see our packet counter monitors triggering all over the place. At a closer look we’ve noticed a common pattern: scripts flooding from customers’ virtual machines running Kloxo.
A zero-day exploit has been identified in Kloxo control panel today. Here’s a discussion related to this.
We decided a few hours ago to proactively fix this inside ALL machines running Kloxo:
- identify offending script that was uploaded and
chmod 0the directory
- stop the kloxo daemon
- email each and every (!) customer about this exploit and explaining the actions we took
Ionut and Ovidiu have just completed these steps and we managed to stop this pest, for now.
We don’t normally run commands inside customers’ virtual machines, but we decided that it’s the best action we can take in the interest of everyone involved. And by everyone, I mean everyone: compromised machine’s owner, other IntoVPS customers, IntoVPS employees and stakeholders, internet community.
Here’s the email we’ve sent:
Subject: IntoVPS – Kloxo installation compromised for server
You are receiving this notification because you are running Kloxo panel management on your VPS named XXXXXXX.
It seems that Kloxo installations are compromised with a randomly-named PHP file placed into /home/kloxo/httpd/default/, which is the ‘default’ site accessible by IP address and that kloxo appear to be spawning a large number of httpd processes. Further investigation shows they’re all sending out volumes of traffic as part of a ddos.
Here is an example of a compromised file uploaded in /home/kloxo/httpd/default: http://disclosed.info/?7c12a1a4560b7664#5fpnfdknf4EfBcGqLjeV9/vAY1RXEKkLC3+fqm16c6E=
At this moment there isn’t any fix published for Kloxo and as a workaround for this particular issue, we are going to change the permission of that folder to 0 with the following command:
chmod 0 /home/kloxo/httpd/default/
chmod 0 /home/admin/*/cgi-bin
Also is it better for now to stop kloxo daemon until a proper fix is released.
We also noticed the same particular file being uploaded in the cgi-bin folders of the website managed by admin users. I strongly advice to check this as well and remove or change permission of those files that contains the same patern as soon as possible.
If you have any questions, please let us know.