Fastly BYOIP Integration Overview
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
| Field | Information |
|---|---|
| Provider Name | Fastly |
| Website | Fastly Website |
| ASN(s) | 54113 |
| Regions Supported | Global HTTP Anycast by default; regional announcements (North America & Europe) available on request. |
| Support Contact | Fastly Support |
| Tech Article & Date | Subscriber Provided Prefix - Last updated May 6, 2024 |
| BYOIP Scope | Subscriber Provided Prefix (SPP) for enterprise customers bringing their own IPv4/IPv6 ranges for production HTTP/HTTPS services, announced from AS54113. |
| Supported Versions | IPv4 and IPv6 |
| Supported Services | Full-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
| Requirement | Details |
|---|---|
| Prefix Size | IPv4: /24 minimum (larger blocks supported) IPv6: /48 minimum (larger blocks supported) |
| ASN Ownership Required | Optional - Fastly originates prefixes via AS54113; customer ASN is not required as long as you own the IP space. |
| IRR or RADb Object | Prefixes 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 LOA | Fastly-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 Limitations | Prefixes 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
Prerequisites
Provide LOA
Prefix Announcement
Service Integration
Lead Time
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.
Step 0 of 0
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Setup 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 Standalone | Delivered 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 Restrictions | Supports HTTP/HTTPS only; no termination for non-HTTP/HTTPS protocols and no general BGP transit or peering service. |
| Other Limitations | Fastly 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.