Oracle extends Video Edge relay architecture to third-party CDNs and ISPs
Oracle is expanding its Oracle Video Edge architecture by allowing relay services to be deployed outside of Oracle Cloud Infrastructure across CDN and ISP partner networks. The distributed system leverages the Media Over QUIC protocol to coordinate delivery across multiple organizations to improve resiliency and reduce latency for live streaming.
Key Takeaways
- OVE now allows relay services to be deployed on external infrastructure, including CDN and ISP partner networks, rather than just OCI regions.
- The system uses the Media Over QUIC (MOQ) protocol to maintain a unified delivery platform across multiple independently operated organizations.
- Relay nodes function as a distributed architecture for real-time routing, session management, and telemetry coordinated by a centralized OCI foundation.
- The architecture supports interoperability with partner platforms natively running MOQ, even if they do not host specific OVE deployments.
Why It Matters
This move signals a shift from siloed delivery toward a coordinated, multi-network relay model necessary for sub-second live streaming at global scale. By extending relays to the ISP edge, Oracle addresses the throughput bottlenecks that often degrade high-concurrency live events. For the ecosystem, it validates Media Over QUIC as a viable cross-vendor standard for normalizing transport between encoders, relays, and players. Watch for IBC 2026 performance data to see if this distributed approach can consistently deliver 200-300ms latency without the high cost of traditional WebRTC infrastructure.
Additional Context
The expansion of Oracle Video Edge comes as the underlying Media Over QUIC (MOQ) protocol reaches critical milestones in standardization and browser support. Per Medium, May 2026, WebTransport — a key enabling technology for MOQ — reached 'Baseline' status in March 2026, meaning it is now supported across Chrome, Edge, Firefox, and Safari. This solves a long-standing 'Apple problem' where Safari's lack of native support forced developers to use less efficient fallbacks for ultra-low latency playback on iOS devices. Simultaneously, the IETF MOQ Working Group is moving toward a formal RFC, with Current drafts (draft-17) scheduled to expire in late 2026. While the protocol is already being used in production by vendors such as nanocosmos and WINK Streaming, the transition from draft to standard is expected by Q1 2027, per IETF milestone updates. These early adopters have reported operational expense savings of 40% to 60% compared to WebRTC SFU architectures when fanning out to 10,000 or more concurrent viewers. Regulatory pressure is also accelerating the demand for these high-capacity streaming solutions. In the UK, the Media Act of 2024 (and subsequent 2026 draft codes from Ofcom) has begun bringing major streaming services under the same standards as traditional broadcasters regarding accessibility and reliability. Furthermore, as the FCC considers allowing US broadcasters to set their own timelines for the ATSC 3.0 transition, the industry is increasingly looking to cloud-native delivery architectures that can mirror the scale and reliability of over-the-air signals without the associated spectrum limitations.
Read full article at blogs.oracle.com
Get this in your inbox → Subscribe
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source