Double Paid Traffic

Double Paid Traffic

Hetzner Online stands for high-performance and high capacity Internet. In the last few years, our network infrastructure has expanded little by little in order to provide our customers with optimal performance. Currently, about two-thirds of our network traffic is directly exchanged with cost-neutral peerings of various partners.Among them are privat peerings with large network operators.
For this reason, we have been increasingly concerned with DSL and cable providers who have no open peering policy themselves but are also not connected to other Tier-1 carriers with sufficient capacities. During the peak traffic period of 7 pm to 10 pm in particular, the concerned DSL and cable providers hit their capacity limits and thereby impede the fluent data stream between individual networks. This has lead to increasing complaints from the providers' customers because the customers cannot access their servers with the level of performance that they are used to having from Hetzner Online.
These customers already paid for comprehensive and quick access to the Internet with their monthly DSL and cable fees. However, providers are no longer satisfied with just this source of profit. They now also want to collect revenue by charging large content providers fees for access to their network. For this reason, interfaces are being operated at their highest capacity -- to make paid access to the DSL and cable providers' networks attractive for content providers. The end consumer is then forced to pay double for unlimited access to the Internet. We at Hetzner Online do not support such policies and declare our support for full net neutrality.
Please look at the following links for additional information:
But because some of our customers are reliant on high-performance connections to Deutsche Telekom AG's (DTAG) network, we are offering these customers the opportunity to book double-paid traffic via an additional uplink to DTAG.
This option costs € 4.20 a month for all of our servers. With this add-on, we will connect an uplink to DTAG via Core-Backbone for the assigned IP address. The included traffic is similar to the respective traffic limits of eachTraffic/en server category. An additional € 3.50 will be charged for each TB of traffic that exceeds the traffic limit. No Flexi-Pack is needed for the activation of the double-paid traffic.

Booking double-paid traffic

Set-up time: roughly 1 workday
You can order double-paid traffic for your server by sending a support request from your administration interface (Robot/konsoleH).

For Dedicated Root Servers and vServers

Go to "Main functions" -> "Servers". Then click on the specific server. And then on "Support". Under "Request Type" choose "Product Advice".

For Managed Servers

Go to "Administration" -> "Support" -> "Support Request" -> and under "Category" choose "Managed Server". Then enter your Tariff/Product/Invoice number. And then under Options click on Technical Request.

For Colocation Racks

Go to "Main functions" -> "Servers". Then click on the specific colocation rack. And then on "Support". Under "Request Type" choose "Product Advice".
Make sure to clearly state that you would like to order the DTAG uplink in the text field of the request and that you agree to pay the additional € 4.20 a month. The add-on will be called "Double Paid Traffic" on your bill.
Customers with colocation racks should also state that they agree to the additional traffic overage charge of € 3.50/TB.
Customers who have dedicated servers or vServers and who pay traffic overage charges should also clearly state that they agree to the increased traffic overage charge of € 3.50/TB.
It is not possible to provide the DTAG uplink for individual IPs (if the dedicated server or rack has several IPs and/or subnets). The option can only be applied to all IPs/subnets of the dedicated root servers or colocation racks together.

What about dedicated root servers with failover-IPs/subnets?

It's easiest to explain with an example:
Server A has a failover-IP and the DTAG uplink.
Server B does not have a failover-IP and does not have a DTAG uplink.
If that customer switches the failover-IP to server B, then the option for the DTAG uplink no longer applies. Therefore, if the failover-IP is switched to server B, traffic from that server with a destination within DTAG's net (the target IP is in the DTAG net) will NOT go directly via Core-Backbone in the DTAG net (at least, we cannot guarantee that); rather it will go via other routes (currently NTT or GTT).

Cancellation of double-paid traffic:

This option can be canceled with a due date to the end of any billing period by sending a support request via the respective administration interfaces (Robot/konsoleH).

Comments

Post a Comment

Popular posts from this blog

Adding behavior to a Java class Person  is looking good so far, but it can use some additional behavior to make it more interesting. Creating behavior means adding methods. This section looks more closely at  accessor methods — namely, the getters and setters you've already seen in action. Accessor methods To encapsulate a class's data from other objects, you declare its variables to be  private  and then provide accessor methods. As you have seen, a getter is an accessor method for retrieving the value of an attribute; a setter is an accessor method for modifying that value. The naming of accessors follows a strict convention known as the JavaBeans pattern, whereby any attribute  Foo  has a getter called  getFoo()  and a setter called setFoo() . The JavaBeans pattern is so common that support for it is built into the Eclipse IDE. You've even already seen it in action — when you generated getters and setters for  Person  in the...
Keep reading