Gcore BYOIP BYOIP Integration Overview
Location
This page outlines the technical and procedural information for integrating Bring Your Own IP (BYOIP) with Gcore CDN (and, where relevant, Gcore’s DDoS/Super Transit network services). Gcore supports two main BYOIP models for CDN: (1) provider-announced BYOIP, where your IPv4 subnet (typically /24 or larger) is originated from Gcore’s ASNs and anycasted across their global CDN, and (2) customer-ASN (BYOASN), where you retain control of BGP announcements with your own ASN while still leveraging Gcore’s CDN and edge infrastructure.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Gcore |
| Website | Gcore CDN BYOIP feature | Bring Your Own IP (BYOIP/BYOASN) docs | Dedicated IP | Gcore CDN documentation |
| ASN(s) |
Global Gcore network is advertised from multiple ASNs, including (non-exhaustive): – AS199524 – G-Core Labs S.A. (hosting / CDN / network) – AS202422 – G-Core Labs S.A. (additional network footprint) BYOIP announcements may use one or more of these ASNs depending on region and service design. |
| Regions Supported |
Gcore advertises a global edge network with 180–210+ PoPs across six continents. BYOIP for CDN is designed for global anycast coverage across these PoPs. Representative coverage includes: – North America: US (multiple cities), Canada, Mexico – Europe: UK, Ireland, Germany, France, Netherlands, Spain, Italy, Switzerland, Poland, Nordics, Eastern Europe – APAC & Oceania: Singapore, Hong Kong, Japan, South Korea, Australia, New Zealand – LATAM: Brazil, Chile, Argentina, Colombia and others – MEA & Africa: UAE, Saudi Arabia, South Africa and other regional PoPs Exact PoP list and routing footprint for your BYOIP deployment are confirmed during solution design. |
| Support Contact | Contact Sales (BYOIP / CDN) | Gcore Help Center | 24/7 Technical Support (chat/ticket) | Email: sales@gcore.com, support@gcore.com |
| Tech Article & Date |
Bring Your Own IP to Gcore CDN – premium BYOIP feature (marketing page; describes /24 example, global anycast, provider-announced and BYOASN options). BYOIP/BYOASN docs (high-level feature description). CDN Dedicated IP and BYOIP update (blog; dedicated IP + BYOIP for CDN). |
| BYOIP Scope |
Gcore’s CDN-focused BYOIP feature supports two main patterns: 1) Provider-announced BYOIP (Gcore ASN): You supply a public IPv4 subnet (e.g. /24) that you own. Gcore validates ownership and announces this prefix from their ASNs across the Gcore CDN anycast network. CDN edge IPs seen by end-users and origin/SaaS allowlists are from your IP space rather than Gcore’s. 2) BYOASN / customer-ASN BYOIP: You bring your own ASN and keep BGP announcements under your ASN while integrating with Gcore’s CDN/edge network (design specifics agreed with Gcore). This model targets customers needing maximum control and strict routing/compliance policies. BYOIP is positioned as a premium add-on for customers with security, compliance, branding, or IP-reputation requirements. |
| Supported Versions |
IPv4: Public IPv4 prefixes are the primary and explicitly documented case (e.g. /24 subnets for global announcement). IPv6: Gcore operates IPv6 across parts of its edge / cloud network, but public BYOIP materials focus on IPv4 for CDN BYOIP. Treat BYO-IPv6 as “not publicly documented – require confirmation” at this time. |
| Supported Services |
BYOIP is currently described as a CDN feature, integrated with: – Gcore CDN (HTTP/HTTPS content delivery) – Anycast edge IPs used for CDN resource hosts and origin connections In some designs, BYOIP can intersect with DDoS protection / Super Transit and IP transit where Gcore announces your prefixes and scrubs/forwards traffic, but the primary documented use case is CDN egress and allowlisting. |
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size |
Gcore’s BYOIP page cites providing your own IP subnet “such as a /24 range” for global announcement. In practice: – Minimum (IPv4): Typically /24 for global routing and anycast (industry standard; confirm with Gcore if smaller or aggregated blocks are acceptable). – Larger prefixes (/23, /22, …) can be partially used; you may choose which addresses in the block to map to CDN resources. No explicit IPv6 prefix requirements are documented for CDN BYOIP as of now. |
| ASN Ownership Required |
Not required for provider-announced BYOIP: Gcore announces your subnet(s) from their ASNs and handles global routing. Required for BYOASN scenarios: if you want your own ASN to be the origin for your BYOIP prefixes, you must already control an ASN and BGP setup; Gcore coordinates routing and CDN integration for that case. |
| IRR / Route Objects |
The public docs do not spell out IRR details, but standard practice applies when a provider originates your space: – Your prefix must be correctly registered with an RIR (RIPE/ARIN/APNIC/etc.). – Route/route6 objects and upstream IRR data must be consistent with the intended origin ASN (Gcore ASN for provider-announced, your ASN for BYOASN). Gcore will typically validate ownership and routing policy before accepting the prefix into their network; any required IRR updates are handled by the customer. |
| ROA or LOA |
Gcore does not publicly publish a detailed ROA/LOA checklist for BYOIP, but in practice: – ROA: RPKI ROAs should be created or updated so that the correct origin ASN (Gcore ASN or your ASN) is authorized for the prefix; highly recommended for global routing robustness. – LOA: A Letter of Authorization is typically required when Gcore announces your space from their ASN, proving that they are allowed to originate and use your IPs on their CDN network. Exact documentation is finalized during onboarding with Sales/Network Engineering. |
| RIR Limitations |
Prefixes must be globally routable public IP space, registered under a recognized RIR with clear WHOIS/RDAP records. There are no public RIR-specific exclusions, but: – Space that is hijacked, disputed, or widely blocklisted will generally not be accepted. – For regulatory-sensitive regions (finance, government), Gcore may apply additional due-diligence checks. |
Step-by-Step BYOIP Process
Estimated Setup Time: Typically from a few business days to a couple of weeks, depending on RIR validation, BGP routing setup, and DNS / SaaS allowlist changes.
Tested By Us: Not yet
A) Provider-announced BYOIP (Gcore originates your subnet from its ASNs)
B) BYOASN / customer-ASN BYOIP (you originate; Gcore integrates)
References: Gcore CDN BYOIP feature, BYOIP/BYOASN docs, Dedicated IP, Super Transit docs, DDoS Protection overview.
Cost and Limitations
| Item | Details |
|---|---|
| Fees |
Gcore positions CDN BYOIP as a premium add-on with manual setup support rather than a self-service toggle. Pricing is not publicly listed and depends on: – Number/size of prefixes and regions – Traffic volumes and CDN features (e.g. DDoS, WAAP, Super Transit) Commercial terms are defined with Gcore Sales / Account Management. |
| Bundled or Standalone |
BYOIP is not a standalone transit offering. It is tightly integrated with: – Gcore CDN (primary use case) – Optionally Gcore DDoS / Super Transit and network protection for certain architectures You consume it as part of a broader CDN/security deployment rather than buying “raw” IP transit. |
| Traffic/Peering Restrictions |
– BYOIP traffic always traverses Gcore’s edge network and obeys CDN/cache and security policies you configure. – Gcore retains control over internal traffic engineering, peering, and backbone routing; you cannot arbitrarily dictate all paths, though advanced customers may coordinate BGP policy and communities. – IP ranges must not be widely blocklisted or associated with abusive traffic; Gcore may require cleanup before accepting them into the platform. |
| Other Limitations |
– BYOIP currently focuses on IPv4 and CDN egress; BYO-IPv6 and deep cloud integration are possible but not formally described in public docs and should be validated with Gcore. – Feature availability, SLAs, and routing behavior may differ between regions/PoPs. – Some complex regulatory/compliance scenarios (e.g. very strict data-residency) require custom design and may not be supported everywhere. |
Automation & Developer Access
Abuse & Reputation Management
Related Resources
Gcore Homepage
Gcore CDN Product Page
Bring Your Own IP to Gcore CDN
BYOIP/BYOASN Documentation
Dedicated IP for CDN
Super Transit (BGP-based protection and acceleration)
DDoS Protection Documentation
Gcore API Overview
Terraform Provider: G-Core/gcore
Gcore Help Center