Skip to content
My accountDeutsch

TechnologyReading time 8 min.

Billing traffic: included volume, overage and one rate for every destination

Outbound traffic is included up to the product's included volume, inbound traffic costs nothing. Anything above this is billed at a single rate per terabyte โ€“ regardless of the location where the system is running and where the data is going.

Managed by the Network department

A light grey patch panel from the front; fibre optic connectors are plugged into four dual ports, the orange cables run out of the picture in a flat curve.

At a glance

  • Outbound traffic is counted; inbound traffic and traffic between your systems in the private network are not billed.
  • Cloud instances and VPS come with an included volume per size; dedicated servers and individual GPU configurations have unlimited traffic.
  • Above the included volume, a single rate per terabyte applies for cloud instances and VPS, the same for every location and every destination, without zone tariffs and tiers.

What is counted and what is not

Outbound traffic is billed, i.e. what your systems send: delivered pages and files, responses from an application programming interface (API), data streams. Up to the included volume of the respective product โ€“ the quota โ€“ it is included in the price. Inbound traffic never costs anything, no matter how much you upload, import or receive.

The direction of the data is decisive, not who establishes the connection. If an external system retrieves a file from your server, this is outbound traffic from your server; if your server downloads packages or images from the internet, it is inbound. Traffic within a system, for example between containers on the same server, does not leave the network interface and does not appear in any network count.

Direction and billing of typical operations
ReferenceDirectionBilling
Visitor requests a page or fileoutboundcounts towards included volume
Customer uploads a fileinboundnot charged
Server downloads updates from the internetinboundnot charged
External system retrieves a backupoutboundcounts towards included volume
Replication to your own system in the private networkprivate networknot charged

Traffic between your systems via the private network is not billed, even if the systems are running in different locations; this traffic does not leave the ENTRONYX CLOUD network. For replication, backup and synchronisation between database nodes, the private network is therefore the route whose traffic does not appear on the invoice.

A separate rule applies when changing providers: a complete export of your data is not billed and does not count towards the quota.

How much traffic each product comes with

For cloud instances and VPS, the included volume depends on the size, not the location: the same size comes with the same amount at every location. The table shows the range per product family.

Included volume for outbound traffic per product family
Product familySeriesIncluded traffic
Shared vCPUNX, NP20 TB
Dedicated vCPUND20 to 80 TB
Memory-optimisedNM20 to 50 TB
Storage-optimisedNS40 to 60 TB
ARM, shared vCPUNA20 TB
GPUNG40 to 200 TB, 4 configurations unlimited
Dedicated serversCORE, FORGE, TITAN and VAULTunlimited

The VPS plans correspond to the sizes with shared vCPU, on x86 as well as on ARM, and each of them comes with 20 TB. If you choose a larger tier there, you are buying computing power, not additional traffic. In the other series, the volume increases with the size, up to 200 TB.

Dedicated servers have unlimited traffic in all series, as do the GPU configurations NG-RTX4000, NG-RTX6000, NG-RTX6000-512 and NG-RTX6000-768.

Unlimited means: there is no quota that can be exceeded; the limit is set by the connection. The smallest connection of a dedicated server, 1 Gbit/s, mathematically transfers 328.5 TB at full capacity over an average month of 730 hours. In practice, less remains because protocols occupy part of the bandwidth and hardly any load fills the line for a month. For loads with a high, consistent delivery volume, such as media archives or software distribution, a plan without a quota makes the costs independent of the volume.

What overage costs

Above the included volume, a single rate applies: โ‚ฌ1.09$1.26 net per terabyte. It is the same for every location and every destination, without zone tariffs and without tiers. Whether the data goes to users in the same country or another does not change the rate. This applies to cloud instances and VPS; dedicated servers have no quota, and storage services bill retrieval at their own rates, which this article does not cover.

Only the amount above the quota is billed, and it is linear: double the overage results in double the overage cost; there is no tier at which the rate changes. The calculation is a multiplication:

Overage cost = (outbound traffic โˆ’ included volume) ร— rate per terabyte

Example calculation: cloud instance above the included volume
Instance
NP3
Included traffic
20 TB
Outbound traffic per month
26 TB
Excess usage
6 TB
Rate per terabyte, net
โ‚ฌ1.09$1.26
Additional amount, net
โ‚ฌ6.54$7.56

The additional amount appears on the invoice of the following month, alongside the monthly price of the instance at a location in Germany of โ‚ฌ35.99$41.75 net. If an application is permanently well above the quota, compare the costs with a dedicated server: there is no quota there, the limit is set solely by the connection.

In the example, the additional consumption increases the monthly amount of the instance by 18%. Nevertheless, you should not only see your consumption on the invoice. The counters of the public network interface continuously show the outbound traffic of your systems; if you record the monthly value, you will notice an increase before reaching the quota.

How much data traffic your application generates

For an estimate, two values per item are sufficient: how often something is requested and how large it is during transmission. How often something is requested is shown by your web analytics or the server log; how large it is during transmission is in the server log. The basic formula applies equally to pages, files and interfaces:

Data traffic per month = requests per month ร— transmitted size per request

The transmitted size is decisive, not the stored size. Compression significantly reduces text, stylesheets and scripts during transmission, and what the browser loads from its cache is not transmitted again at all. Therefore, measure the page weight in the browser's developer tools, once with an empty cache and once with a full cache, and calculate with a value between the two.

Example calculation: online shop with download area, one month
500,000 page views ร— 1.8 MB
0.90 TB
4,000 downloads ร— 600 MB
2.40 TB
20,000,000 API responses ร— 12 kB
0.24 TB
Backup to an external destination, 30 days ร— 40 GB
1.20 TB
Outbound data traffic per month
4.74 TB

With 4.74 TB, the application remains below the smallest inclusive volume of a cloud instance of 20 TB; the downloads are the deciding factor, not the page views.

Calculated in decimal units, 1 TB are 1,000,000 MB. If the backup goes via the private network to your own system on the platform instead of an external destination, its item is dropped from the calculation. You should also project the estimate for the next twelve months: new content, more customers and larger files usually shift the requirement upwards.

Items that are often missing in estimates

  • Software updates and installation packages that your systems deliver to devices or customers.
  • Video and audio, calculated with the bitrate: a stream with 5 Mbit/s results in 2.25 GB per viewer in one hour. A presentation with 200 viewers, transmitted for 90 minutes at 3 Mbit/s, results in 405 GB.
  • Logs, metrics and backups that go to destinations outside the platform.
  • Requests by search engines and other automated clients that web analytics in the browser do not capture.

Rule of thumb

Plan the quota for the strongest month of the year, not for the average, and leave a reserve. Anything beyond that in a peak month costs โ‚ฌ1.09$1.26 net per terabyte.

What a CDN changes about data traffic

A CDN (Content Delivery Network) delivers content from nodes at the network edge and keeps copies of frequently requested files there. Your server then only delivers what these nodes do not yet hold or request anew. How much traffic is eliminated at the server depends on what proportion of the transmitted data volume comes from the copies โ€“ usually a large one for images and downloads, a small one for personal pages and API responses.

The CDN listed on the Network page is a separate service with its own price: calculated per delivered terabyte, according to a tier that drops with volume from โ‚ฌ9.90$11.48 to โ‚ฌ3.90$4.52 net per terabyte. Every tier is above the rate for additional consumption; the CDN therefore does not lower the costs for data traffic. It is worthwhile if content is to come from nodes close to the user or if your own server should not bear load peaks alone.

For planning, two quantities count with a CDN: everything the CDN delivers to users โ€“ from its copies as well as freshly fetched from the server โ€“, calculated according to its tier; and what your server continues to send itself: to the CDN, if it does not yet hold a file or requests it anew, and to everyone who requests it directly. You control how large the proportion of copies is via the cache directives of your application: files whose name changes with the content can carry a long validity and then stay in the CDN for a long time; responses marked as not cacheable are fetched anew every time. How it treats responses without cache directives is determined by its default setting.

Published on 8 November 2026. Prices and product values in this post are taken from the price list and reflect their current status.

Further reading

Read more

  • A power meter with two current clamps on a light background; one clamp encloses a thick black power cable running across the image.

    What the PUE value measures โ€“ and what it does not say

    TechnologyReading time 6 min.

    The PUE value compares the energy demand of a data centre to what the IT actually consumes. It thus answers a narrow question precisely โ€“ and many obvious questions not at all.

    Operations department

  • Three light grey servers in three sizes side by side on a light background: a small chassis, a flat 1U server and a 2U server with twelve drive bays.

    VPS, cloud instance or dedicated server: a decision guide

    PracticeReading time 6 min.

    The three architectures differ in who owns the processor core, how they are billed and how quickly a system is provisioned. This article categorises them based on the questions that matter before placing an order.

    Platform department

Questions for the department

Technical questions about a post are answered by the person responsible for the department โ€” in a conversation, not a presentation. For quotes and framework agreements, sales will lead the initial conversation.