Path Network BYOIP Integration Overview

Worth Knowing
Address-family support is documented for tunnels, but accepted prefix lengths are not established and are omitted. Locations are the status-page footprint only.

Searching for the best IP providers? Path Network provides remote DDoS protection for customers who have public IP space and their own public ASN. Routing requirements include route objects and ROAs for every submitted prefix. You configure the tunnel and receive protected traffic at a published service location. This record is not Tempest Hosting.

Provider Details

FieldInformation
Provider NamePath Network
Websitepath.net
ASN(s)AS396998. Your own public ASN is required. An AS-SET is required when you carry downstream ASNs.
Regions SupportedStatus-page footprint for remote DDoS protection, not a guarantee of eligibility or capacity: United States (New York, Chicago, Dallas, Los Angeles, Silicon Valley, Phoenix, Miami, Kansas City, Salt Lake City), Netherlands (Amsterdam), Poland (Warsaw), United Kingdom (London), Germany (Frankfurt), Spain (Madrid), Bulgaria (Sofia), Singapore, Japan (Tokyo), Australia (Sydney).
Tech Article & DateTechnical requirements - checked 7 October 2026
BYOIP ScopeRemote DDoS Protection for customer public IP space.
Supported VersionsBoth address families appear in the tunneling documentation. Accepted customer-prefix lengths are not established. This page does not fill /24 or /48 from convention.

Caveats and Gotchas

  • The country list is the operational footprint on Path's status page. It is not a promise that every site can take your prefix.
  • Route objects and ROAs are required for every prefix. An LOA requirement was not established in the reviewed technical article.
  • A published FastNetMon integration can automate diversion after you are a customer. It is not automatic onboarding.
  • A case study's setup time is not a service-wide SLA. Prefer the June 2024 technical requirements over older ROA wording.

Technical Requirements

RequirementDetails
Prefix SizeNot established. Confirm the accepted lengths with Path.
ASN Ownership RequiredYes. A public customer ASN is explicitly required.
IRR and ROARoute objects and RPKI ROAs for all prefixes.
Return pathGRE and IPIP for IPv4. IP6TNL for IPv6.

Step-by-Step BYOIP Process

Step 1
Initial setup is provider-assisted.

Submit the public prefixes with route objects and ROAs, and your public ASN.

Step 2
Configure GRE or IPIP for IPv4, or IP6TNL for IPv6, on the tunneling equipment Path supports.
Step 3
Pricing is a quote.

No public fixed price was verified in the reviewed primary sources.

Path Network technical requirements
Path Network status page
Path Network IRR and prefix guidance

Published 7 October 2026

More BYOIP supporters

All BYOIP supporters

FAQ