Hurricane Electric BYOIP Integration Overview
Worth Knowing
Classified as an IP transit provider. Tier descriptions can differ between IPv4 and IPv6. Country tags are IP transit service endpoints from the official page, not every network PoP. RPKI-invalid route rejection is not a customer ROA requirement.
Searching for the best IP providers? Hurricane Electric provides IPv4 and IPv6 IP transit with BGP for customer networks on its AS6939 backbone. Customer-prefix routing is the transit service itself. BGP is included; the transit port is priced individually. A customer ASN is how the published transit product works, but this page does not treat that as a proof that managed announcement is impossible under every contract.
Classified here as an IP transit provider. Tier descriptions can differ between IPv4 and IPv6, so this page does not apply a blanket tier label.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Hurricane Electric |
| Website | he.net |
| ASN(s) | AS6939. Customer BGP is part of the transit product. |
| Regions Supported | IP transit service endpoints listed on the official page on 6 October 2026, not every network PoP: Argentina, Australia, Austria, Belgium, Brazil, Bulgaria, Cambodia, Canada, Chile, Colombia, Croatia, Czech Republic, Denmark, Djibouti, Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary, Ireland, Italy, Japan, Kenya, Latvia, Lithuania, Luxembourg, Malaysia, Mexico, Netherlands, New Zealand, Nigeria, North Macedonia, Norway, Philippines, Poland, Portugal, Romania, Serbia, Singapore, Slovakia, Slovenia, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, Thailand, Turkey, Ukraine, United Arab Emirates, United Kingdom, United States. |
| Tech Article & Date | Hurricane Electric IP Transit - checked 6 October 2026 |
| BYOIP Scope | Customer prefixes carried on HE IP transit with BGP. IPv4 and IPv6 are both offered on the transit connection. |
| Supported Versions | IPv4: yes. IPv6: yes. |
| Supported Services | IP transit |
Caveats and Gotchas
- Sales and provisioning are provider-assisted. The public page is a transit quote, not a self-serve prefix import.
- HE rejects RPKI-invalid routes on its network. That filtering is not the same as a rule that every customer must publish a ROA.
- LOA handling, minimum prefix sizes and turnaround are not published on the transit page.
- The country list is service endpoints from the transit page. It is not a claim that every HE exchange or private peering point sells this product.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | Not published on the transit page. |
| ASN Ownership Required | Customer BGP is supported. A universal ban on managed announcement is not established by a current customer policy on this page. |
| LOA | Not published. |
| RPKI ROA | Not documented as mandatory. Invalid-route rejection is separate from a customer ROA requirement. |
Step-by-Step BYOIP Process
Step 1
Request an IP transit quote and name the facility.
Onboarding is manual.
Step 2
Agree the port and the prefixes you will announce to AS6939.
Step 3
Bring up BGP.
IPv4 and IPv6 transit are offered on the same connection.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Transit is priced individually. BGP is included. This is not a free BYOIP service that omits the transit cost. The public quote form starts from USD 200 per month. |
Related Resources
Published 11 September 2026 · Updated 6 October 2026
More BYOIP supporters
All BYOIP supporters- Akamai Prolexic BYOIP Integration Overview
- F5 Distributed Cloud DDoS Mitigation BYOIP Integration Overview
- Imperva DDoS Protection for Networks BYOIP Integration Overview
- Radware Cloud DDoS Protection BYOIP Integration Overview
- NETSCOUT Arbor Cloud BYOIP Integration Overview
- Link11 BYOIP Integration Overview