Managed Kubernetes now available in Open Beta. Test out the new service yourself at your Control Panel.
Managed Kubernetes now available in Open Beta. Test out the new service yourself at your Control Panel.
Data transfer is an integral part of cloud computing and all our Simple plans include a generous amount of transfer capacity within the monthly pricing. Nevertheless, the needs of fast-growing businesses can quickly exhaust the monthly transfer quota of their front-end cloud server while other servers on their account never come even close. We recognise the unbalanced use of transfer quotas which is why on the 1st of October 2020 we will be bringing Network Transfer Pool to all public cloud users!
Earlier this year, we lowered the excess data transfer pricing considerably to reduce the cost of outbound transfer to just $0.01 per GB when going beyond the included quotas. However, Network Transfer Pool is going to make even that an unlikely situation by allowing your UpCloud services to share their quotas!
Network Transfer Pool, as the name suggests, combines all transfer quotas included in all UpCloud public cloud products and services you use into a single account-wide transfer pool. This includes all traffic quotas across all data centres covering all current Cloud Servers as well as any future products that contain quotas for outgoing transfer. All metered network transfer is then first subtracted from the pool at a maximum expected hourly rate before any excess billing. Higher bursts of network usage exceeding the hourly transfer quota are billed at the standard transfer rate of $0.01 per GB.
The pooling is based on the goal to enable users to take full advantage of their allotted transfer quota but distributed evenly across the month to ensure fair playing field to all users. In practice, the summed up quota is divided by the hours in a calendar month for an hourly transfer quota for all your UpCloud services. The hourly transfer quota is regularly updated according to the changes in deployed services and is calculated at the beginning of every hour according to the currently allotted quotas.
Example of the new Network Transfer Pool:
All of your cloud services which include transfer quota share the combined Transfer Pool and the calculated hourly quota allowing greater flexibility in service configurations. No longer will the transfer quotas of your database and other backend servers be left unutilised while the frontend or load balancers exceed their individual quotas. And as always, all transfers within SDN Private Networks and the Utility network remain unlimited and free of charge.
Learn more in our network documentation.
The new Network Transfer Pool comes into effect at 00:00 UTC on the 1st of October 2020 when ready!
Last month, we announced our plans to bring new freedoms with the introduction of Network Transfer Pool and have been happy to see the enthusiasm and positivity for the announcement. However, we also received feedback from users concerned over fluctuating and seasonal network usage which might cause more excess charges under the new model. To […]
Announcements
The Internet has widely enabled great strives in technology, but progress doesn’t happen by itself. Truly groundbreaking developments take considerable time and effort. We’ve been preluding about our plans and efforts in developing SDN for some time now but the wait is now over! SDN is launching today! The new SDN architecture enables a lot of new […]
Announcements
For most of us, 2020 was an unexpectedly challenging year. The ongoing global pandemic has significantly changed lives around the world. Luckily, we at UpCloud have been able to continue operations to provide you, our users, with many new features and services throughout the year and by extent tried to make your year a little […]
Product Updates
Vision and culture
Anon
Thanks, a lot!
WVH
Sounds good. Have you considered a hard limit that puts users on a slower connection for the rest of the month or some other way to control costs for personal projects where budget surprises are more problematic?
Taylor
Ok you are trying to do something by utilizing the backend server quotas but at the same time ruining monthly quota concept for users with peaks during the day. Let’s say someone has peak hours thru 09:00 to 15:00 and not much of a traffic at other times. Normally even if this person could be just fine this month with monthly cap only, will be fined for his peak hours next month in October. The very beginning of this concept that you have the limit for the hour is so wrong because if you are below limit you can’t accrue any bandwidth to the next hour but if you are above the limit you will be slapped with excess usage. So wrong! Don’t do that!
Anon
I am really disappointed to see that this feature is postponed.
Why can’t you just implement it the same way as competitors there you have just monthly network transfer pool, which adds total amount of bandwidth from each node?
Hopefully this won’t get postponed to the oblivion.