Edge IP Binding (EIPB) lets you deliver traffic from a small, static set of IP addresses in an ​Akamai​ scalable manner.

You can implement EIPB to accomplish the following:

• Support zero-rated billing. Are you looking to offer specific traffic at no cost to end users, or prevent specific delivery from counting against a data cap? More on this below.

• Identify content provider traffic based on the source IP. This helps when you can't perform deep packet inspection.

• Provide a single or a limited number of source IP addresses. This would help if your infrastructure systems are too complex and need a single, or very limited number of source IPs.

• Eliminate frequent updates to IP address ranges. This applies if your business support or operations support systems can't handle frequent updates.

• Provide simplicity and scale. This can help remove the need for additional domains or additional IPs.

In addition to "EIPB," Edge IP Binding is also sometimes referred to as "EIP" or "EIPBinding."

Zero-rated billing environments

Zero-rated billing (ZRB) involves a third party, such as a mobile carrier that establishes a partnership with you to offer their traffic at no cost to your end users; or to prevent counting it against a data capacity threshold ("data cap"). Since identifying this type of traffic can be difficult, the solution is to provide you, as an ​Akamai​ customer, a quantity of fixed IP addresses that can be used exclusively for these purposes. This is what EIPB does.

📘

If your delivery scenario only includes non-ZRB traffic, avoid serving it through EIPB.

How to enable EIPB

You add EIPB in Property Manager by enabling it in a property hostname to edge hostname association ("edge hostname") in your property configuration. However, there are other considerations and requirements, all of which are covered in the Edge IP Binding documentation.

📘

Make sure you review Before you begin in the Edge IP Binding documentation.

Other EIPB services

In addition to standard EIPB, you can apply additional services for use:

• ASN Split for EIPB. Does your environment require delivery of both ZRB and non-ZRB traffic? If so, you can implement "ASN Split" along with EIPB in a single Property Manager configuration to distribute all of your content. Instruction on use can be found in the Edge IP Binding user documentation.

• HSAF for EIPB. EIPB works with a limited set of IP addresses to distribute your content, and this can be limiting in large footprint environments. Traditional large footprint scenarios don't work well with EIPB. To help, we offer Hash Serial and Forward (HSAF) for EIPB. See the Edge IP Binding user documentation for more information.