Skip to content

Fastly BYOIP Integration Overview

BYOIP SUPPORTER
ASN 54113
IPv4 support
IPv6 support
LOA support
ROA support
Process Semi-automatic
Locations supported
Other: Ghana, South Africa, China, India, Japan, Malaysia, Philippines, Singapore, South Korea, Thailand, United Arab Emirates, Austria, Belgium, Bulgaria, Denmark, Finland, France, Germany, Ireland, Italy, Netherlands, Norway, Portugal, Spain, Sweden, United Kingdom, Canada, Mexico, United States, Argentina, Brazil, Chile, Colombia, Peru, Australia, New Zealand

Searching for the best IP providers? Fastly’s Subscriber Provided Prefix (SPP) product enables enterprise-grade BYOIP automation, IP reputation screening, and seamless integration with HTTP/HTTPS services. Below you’ll find Fastly setup documentation, BYOIP requirements, reviews, pricing, and benefits to help you securely onboard and manage your custom IP ranges.

Provider Details

FieldInformation
Provider NameFastly
WebsiteFastly Website
ASN(s)54113
Regions SupportedGlobal HTTP Anycast by default; regional announcements (North America & Europe) available on request.
Support ContactFastly Support
Tech Article & DateSubscriber Provided Prefix – Last updated May 6, 2024
BYOIP ScopeSubscriber Provided Prefix (SPP) for enterprise customers bringing their own IPv4/IPv6 ranges for production HTTP/HTTPS services, announced from AS54113.
Supported VersionsIPv4 and IPv6
Supported ServicesFull-Site Delivery (CDN), Streaming Delivery, DDoS Protection & Mitigation, Origin Connect, and other HTTP/HTTPS workloads pinned via Dedicated IP / IP-to-Service Pinning.

Technical Requirements

RequirementDetails
Prefix SizeIPv4: /24 minimum (larger blocks supported)
IPv6: /48 minimum (larger blocks supported)
ASN Ownership RequiredOptional – Fastly originates prefixes via AS54113; customer ASN is not required as long as you own the IP space.
IRR or RADb ObjectPrefixes must be registered with an RIR; the LOA must reference the registry and object identifier for the prefix. IRR/RADb route objects follow normal routing best practice but are not documented as a strict Fastly requirement.
ROA or LOAFastly-issued Letter of Authorization (LOA) is mandatory and must include IP blocks, registry/object ID, and admin/technical/abuse contacts. ROAs/RPKI are not explicitly required in Fastly documentation but may be used by the IP holder.
RIR LimitationsPrefixes must not be originated by any ASN when Fastly begins announcing them, should be dormant for approximately 3 months before use, and must not overlap with address space used by your origin servers.

Step-by-Step BYOIP Process

1. Prerequisites

  • Confirm Enterprise Support and IP-to-Service Pinning Setup are in place, your RIR-registered /24 or larger IPv4 and /48 or larger IPv6 prefixes are unannounced, dormant for roughly three months, and suitable for production use.

2. Provide LOA

  • Submit Fastly's Letter of Authorization with registry name, object identifier, IP prefixes, and current administrative, technical, and abuse contacts.

3. Prefix Announcement

  • Fastly validates reputation and documentation, then announces your ranges from AS54113 via HTTP Anycast globally or scoped to the North America and Europe region as requested.

4. Service Integration

  • Configure Dedicated IP and IP-to-Service Pinning so selected IPs terminate HTTP and HTTPS on your Fastly services (CDN, Origin Connect, DDoS, etc.) and update DNS to point application domains at the pinned addresses.

5. Lead Time

  • Plan at least 45 days lead time for initial Subscriber Provided Prefix activation and similar notice if you later withdraw or re-home prefixes.

Cost and Limitations

ItemDetails
FeesSetup fee plus a monthly rate that typically includes two anycast prefix configurations (one IPv4 and one IPv6). Additional or larger prefixes are available at higher monthly charges.
Bundled or StandaloneDelivered as the Subscriber Provided Prefix add-on for Fastly’s platform; requires Enterprise Support and IP-to-Service Pinning and is used alongside core HTTP/HTTPS services (Full-Site Delivery, Streaming Delivery, Origin Connect, DDoS Protection).
Traffic/Peering RestrictionsSupports HTTP/HTTPS only; no termination for non-HTTP/HTTPS protocols and no general BGP transit or peering service.
Other LimitationsFastly retains exclusive announcement rights for onboarded prefixes; they cannot be announced elsewhere and must not overlap with origin IP space. Prefixes should be dormant prior to use, may be de-aggregated during DDoS mitigation, and any unpinned IPs return TCP reset or HTTP 500 responses. Additional prefixes beyond the initial order require separate SPP purchases.

Automation & Developer Access

  • API Access: Subscriber Provided Prefix (SPP) API plus DNS and TLS configuration APIs for managing SPP IP pools, supported TLS and HTTP versions, and IPv4/IPv6 dual-stack hostnames.
  • Terraform/SDK: Manage Fastly services and IP configurations via the Fastly Terraform provider and REST API; SPP onboarding still starts through Fastly sales and support before being automated with APIs where appropriate.

Abuse & Reputation Management

  • IP Reputation Monitoring: Fastly scans provided prefixes against common IP reputation databases before announcement and requires neutral or positive reputation.
  • Blacklist and Abuse Handling: Fastly enforces reputation thresholds at onboarding; ongoing blacklist removal and abuse remediation remains the IP holder's responsibility with RBLs and other third parties.

Fastly BYOIP Documentation
Fastly IP Addresses & BYOIP Product Page
IPXO Setup Guide

FAQ

BYOIP, or Bring Your Own IP, is a service that enables organizations to bring their own public IP addresses—whether owned outright or leased from an IP provider—into a service provider’s network infrastructure. Instead of relying on IP addresses assigned by the provider, BYOIP allows businesses to retain control over their IP resources. This ensures continuity, particularly for organizations with established IP-based reputations, branding, or dependencies on specific address blocks. IP providers can assist in streamlining this process, making it easy to integrate your IPs into the desired network environment.

BYOIP offers several compelling advantages. By using your own IPs, you can maintain continuity in your network’s identity, reduce the risk of disruptions to email deliverability or service recognition, and avoid reputational concerns associated with shared IPs. Additionally, BYOIP provides enhanced flexibility and control over your IP resources.

BYOIP is ideal for organizations that either own public IP addresses or lease them from a trusted IP provider with explicit BYOIP support. This includes enterprises, cloud providers, content delivery networks (CDNs), and businesses with compliance requirements or IP reputation needs. Working with a reputable IP provider ensures that leased IPs can be seamlessly integrated into another provider’s infrastructure without ownership concerns.

You must either legally own the IP addresses or have explicit authorization from a leasing IP provider to route and manage them. IP providers who offer BYOIP-ready IP addresses simplify this process, providing documentation and support to ensure compliance with regional internet registry (RIR) policies and service provider requirements. This collaboration ensures smooth implementation without any legal or operational issues.

To use BYOIP, you’ll typically need to present documentation verifying your authority over the IP block. This can include official records from a regional internet registry (RIR) such as ARIN, RIPE NCC, or APNIC. If you are leasing IPs, the IP provider should supply proof of their ownership and grant you permission for BYOIP. Providers that specialize in IP leasing often handle this paperwork for you, reducing administrative burden and ensuring compliance.

Yes, BYOIP is designed to be a secure and reliable solution. Reputable service providers and IP providers implement robust safeguards to prevent unauthorized use or hijacking of IP addresses. Security measures include BGP filtering, route validation, and advanced protocols like Resource Public Key Infrastructure (RPKI). By collaborating with a trusted IP provider, businesses can benefit from additional layers of protection, ensuring that only authorized traffic is routed through their IP blocks.

The setup process for BYOIP varies by provider, typically taking anywhere from a few hours to a few days. Factors include the complexity of your network, the verification process for IP ownership or authorization, and the time needed for global BGP route propagation. IP providers often expedite the preparation and validation stages, ensuring a smooth and timely integration into the desired infrastructure.

Absolutely. Many providers, in partnership with IP providers, support routing IPs across multiple data centers or geographic regions. This feature optimizes performance for global businesses by reducing latency and improving service availability. When working with an IP provider, you can also ensure that your leased or owned IPs are aligned with your geographic requirements for compliance and efficiency.

If you choose to discontinue BYOIP with a provider, your IP addresses will be released from their network, and routing will cease. You can then reallocate these IPs for use with a different service provider or project.