Overview
SkyparkCDN announced in May 2017 that it had become part of G-Core Labs that March. The teams planned infrastructure integration and a common platform.
For an older account, check the current service and support arrangement with Gcore . Standalone SkyparkCDN availability remains unconfirmed.
Network
The historical announcement discussed integration and planned expansion. For a current deployment, ask which cities are serving traffic now.
For an existing account, ask the current operator for delivery locations, routing and residency. Use the separate Gcore profile when evaluating current Gcore services; no historical map is presented as active coverage.
Past features
Current SkyparkCDN protocol, security, API, purge and logging guarantees are unconfirmed. Test required cache, access and media behavior against the replacement service.
Before migrating, check cache-key behavior, authorization, TLS, purge operations and media delivery against the actual replacement service.
Service status
SkyparkCDN joined Gcore in 2017. Ask Gcore about support and the migration path for your account.
- Inventory hostnames, rules, certificates, APIs and logs.
- Test the replacement with representative objects and traffic.
- Run a reversible rollout with monitored origin load.
Check the current plan and supported features before moving traffic.
History timeline
- March 2017 — SkyparkCDN became part of G-Core Labs — Its May 2017 announcement described integration plans.
Budgeting for a replacement
Get a current quote for the successor service you will use. Use the calculator with current replacement-provider rates or a USD quote.
Compare request charges, regional delivery, minimums, support and migration overlap separately. Get current prices and included usage from the successor service.
Historical integrations
Confirm who operates the account and which console, APIs and credentials remain valid.
- Export delivery rules and domain configuration.
- Inventory purge jobs, log consumers and automation.
- Test origin authentication and signed-content behavior.
Ask the current support team for the documentation and automation options available with your account.