Company snapshot

CategoryIORiverTelefónica
Statusactivedefunct
Founded
Headquarters
Website
Docs

Overview

IORiver is a MultiCDN platform that enables businesses to manage multiple CDN局

System: Content Delivery Networks (CDNs) simultaneously, ensuring high availability and performance without the complexity of managing each CDN separately. Founded in 2024 by former Akamai engineers Edward Tsinovoi and Michael Hakimi, IORiver is based in Tel Aviv, Israel, and serves industries like SaaS, online retail, streaming media, and finance. The platform handles over 100 petabytes of traffic monthly, offering a unified interface for configuring edge services like WAF, rate limiting, and edge computing across multiple providers. It integrates with major CDNs such as Cloudflare, Akamai, Fastly, Edgio, and Amazon CloudFront. IORiver focuses on simplifying MultiCDN adoption for businesses needing global content delivery with minimal operational overhead.

Telefónica, a Spanish multinational telecommunications company founded in 1924, operated a content delivery network (CDN) as part of its broader telecom services. The CDN focused on delivering content across Europe and Latin America, leveraging its extensive network infrastructure. It served enterprises, media companies, and telecom partners but ceased CDN operations as part of a strategic pivot away from certain business units. As of 2025, Telefónica’s CDN is defunct, with the company focusing on core telecom, IoT, and AI services.

Network & Architecture

IORiver does not operate its own CDN infrastructure but orchestrates traffic across multiple third-party CDNs, including Akamai, Cloudflare, Fastly, Edgio, Amazon CloudFront, G-Core, and Microsoft Azure. Its Virtual Edge solution routes traffic to optimal CDN providers based on geolocation, traffic type, or cost, achieving 99.999% availability. The platform supports global content delivery with no specific POP count disclosed, relying on the combined footprints of integrated CDNs. It uses a Multi-DNS approach for resilient routing, avoiding single points of failure. Regional strengths depend on the chosen CDN providers, with flexibility to include local CDNs for markets like India or China.

Feature comparison

FeatureIORiverTelefónica
waf
bot_mitigation
ddos
rate_limit
http3_quic
tls13
tiered_cache
origin_shield
instant_purge
stale_while_revalidate
stale_if_error
image_optimization
video_vod
video_live
drm
hls_dash_packaging
websockets
signed_urls
edge_compute
functions
kv_storage
api_first
realtime_logs
log_push
terraform

Legend: ✓ = Supported, ✗ = Not supported, — = Not listed

Pricing

IORiver operates on a pay-as-you-go (PAYG) model, with pricing based on traffic volume and bundled services like WAF and analytics. No public per-GB pricing is available, and costs vary depending on the mix of CDN providers used. IORiver negotiates wholesale agreements with CDNs to reduce costs, but specific pricing details are not disclosed on their website. Potential users should contact IORiver directly for quotes. No free tier or trial details are publicly listed.

Integrations & DevEx

IORiver supports Terraform for infrastructure-as-code, enabling automated configuration of multi-CDN setups. It offers REST, Python, and Go APIs for programmatic control, integrating seamlessly with CI/CD pipelines. Real-time logs and analytics via GlobalView provide insights into traffic patterns and performance. Migration tools simplify switching CDNs by importing configurations and testing providers with minimal traffic initially. The platform supports integration with major CDNs like Akamai, Cloudflare, and Amazon CloudFront, reducing setup complexity.

When it fits

  • When it fits

  • Businesses using multiple CDNs to optimize global performance, reliability, or cost, especially in SaaS, retail, or streaming.
  • Teams seeking a unified interface to manage complex multi-CDN setups without in-house tools.
  • Organizations needing advanced edge services like WAF, DDoS protection, or edge computing across vendors.
  • When it doesn’t

  • Small businesses or startups needing a single, simple CDN with minimal configuration overhead.
  • Companies locked into a single CDN provider due to long-term contracts or specific feature dependencies.
  • Users requiring transparent per-GB pricing without custom quotes or negotiations.

When it doesn’t

History & Notes

Telefónica’s CDN leveraged its telecom backbone, offering low-latency delivery in Europe and Latin America. The service supported instant cache purging and API-driven configurations, as noted in historical reports. The decision to sunset the CDN aligns with Telefónica’s broader strategy to exit non-core markets and invest in 5G, IoT, and cloud security. No conflicting reports suggest a revival of the CDN.