Gcore BYOIP Integration Overview
Searching for the best IP providers? Gcore supports customer IP space on CDN and on paid DDoS network protection. The two products do not share one onboarding path. CDN BYOIP is a paid add-on configured by request. DDoS protection starts with a portal submission, then a network-team review, then GRE and profile setup on your side.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Gcore |
| Website | gcore.com |
| ASN(s) | AS199524. CDN BYOIP can be provider-announced or brought with your own ASN (BYOASN). The DDoS form asks for an ASN. The origin and peering arrangement for that product are agreed during setup. |
| Tech Article & Date | CDN BYOIP and DDoS service activation - checked 7 October 2026 |
| BYOIP Scope | CDN BYOIP and BYOASN, plus paid remote DDoS protection of customer prefixes. Free Basic protection on Gcore-hosted resources is a different product. |
| Supported Versions | CDN: IPv4 /24 or larger, and IPv6 /48 or larger. DDoS: the submission guide documents an IPv4 form for lengths /8 through /24. IPv6 protection appears in product material. Confirm the IPv6 activation path with Gcore. |
CDN BYOIP
CDN BYOIP is a paid, manually configured add-on. You can have Gcore originate the prefix, or keep announcements under your own ASN. Current CDN documentation asks for RIR proof of prefix ownership, a letter of authorization for each prefix, IRR route or route6 objects, and a valid ROA.
DDoS protection
Paid DDoS network protection is a separate workflow. You submit network information and an LOA in the portal. Gcore's network team reviews the request. The review guide says decisions often arrive within 24 to 48 hours, and that interval is not a guaranteed provisioning SLA. After approval you configure the GRE endpoint and the protection profile.
The directory process flag for this record stays manual because that is the CDN path. The DDoS path is portal submission plus NOC review, then customer configuration. It is not the same as CDN onboarding, and it is not automatic.
Documentation examples on the network-submission page use private and documentation addresses. Those examples are not eligible public prefixes, and they are not copied here.
Caveats and Gotchas
- Free Basic mode on Gcore-hosted resources null-routes during an attack. That is not free remote scrubbing of a customer prefix.
- PAYG DDoS has no bandwidth commitment and can still incur charges. It is not a free service. CDN BYOIP remains a separate paid add-on.
- Do not carry the CDN ROA rule over to DDoS. The DDoS workflow explicitly requires an LOA. A ROA requirement for that workflow is not established here.
- Published DDoS plans include usage-based and committed-bandwidth options. Charges depend on clean-traffic usage, plan, currency, and billing term. Setup assistance and excess usage can add charges. This page does not publish a single EUR or USD price.
Step-by-Step BYOIP Process
open a request for the paid BYOIP or BYOASN add-on and return the ownership evidence, LOA, IRR objects, and ROA. Gcore configures it. This path is manual.
submit the prefix and ASN with an LOA in the portal. Wait for network-team approval. The 24 to 48 hour note is indicative only.
configure the GRE endpoint and the protection profile on your router.
Cost and Limitations
| Item | Details |
|---|---|
| Fees | Both products are paid. See Gcore's current security pricing page for DDoS plans. Do not treat one displayed amount as the price of every term or currency. |
| Other Limitations | DDoS return is a GRE endpoint. CDN coverage is global anycast. Exact PoPs for a prefix are confirmed during design. |
Related Resources
Published 24 November 2025 · Updated 7 October 2026