Video API Latency
Benchmark Comparison:
The 2026 Definitive Guide

The Master Comparison Table

This table compares every video API vendor we could find published performance data for. We distinguish between different types of latency measurements because they are not equivalent. An API response time measures control plane speed. Protocol-level latency measures data plane speed. End-to-end latency includes network transit, encoding, and decoding.

V100 Detailed Benchmark Numbers

V100 is the only vendor in this comparison that publishes per-operation protocol-level latency. Here is the complete breakdown, now including gateway-level numbers from the March 2026 optimization pass:

Gateway Benchmarks (March 2026)

Protocol-Level Benchmarks (Graviton4)

Throughput Numbers

Categories Where V100 Has No Published Data

Credibility requires acknowledging gaps. Here are the benchmark categories where V100 does not yet have published numbers, and where competitors may have an advantage:

Understanding the Different Types of Latency

Video API latency is not a single number. It is a stack of measurements, each important for different reasons:

1. Protocol-Level Latency (V100: 263.1ns)

The time for the server to process a single STUN/TURN operation from packet arrival to response ready. This determines server-side processing overhead, jitter contribution, and how many concurrent operations a single server can handle. Only V100 publishes this number.

2. API Latency (Twilio: ~50ms)

The time for an HTTP REST API call to complete. This measures control plane responsiveness — how fast you can create rooms, add participants, or query status. Important for developer experience but does not directly impact media quality during a call.

3. Join Time (Daily: <100ms)

The time from calling "join" in the SDK to the first media flowing. This includes signaling, ICE negotiation, DTLS handshake, and codec initialization. It is what users experience when they click "Join Meeting" and wait for video to appear.

4. End-to-End Latency (Agora: ~200ms)

The total time from one participant's camera capturing a frame to another participant's screen displaying it. This includes capture, encoding, network transit, server relay, decoding, and rendering. It is the most user-visible metric but includes many components outside the server's control.

5. Tail Latency (V100 now publishes this)

The 99th or 99.9th percentile latency. Average latency is less useful for real-time media because a few slow operations cause visible glitches. V100 now publishes tail latency: p99 at 50 concurrent: 13.4ms. No other video API vendor we surveyed publishes equivalent tail latency numbers.

Architecture Comparison

Methodology: How V100 Benchmarks Are Produced

Every V100 number in this post comes from the same benchmark methodology:

1. Hardware: AWS c8g.16xlarge (Graviton4, 64 vCPUs, ARM Neoverse V2)
2. Framework: Criterion.rs with 5-second warmup, minimum 100 iterations, 95% confidence intervals
3. Isolation: Dedicated instance, no co-located workloads, performance CPU governor
4. Reproducibility: Benchmarks are part of the CI pipeline and run on every release
5. Honesty: We report median values with confidence intervals, not cherry-picked best runs

We use Graviton4 (ARM) specifically because it does not have turbo boost. x86 processors dynamically adjust clock frequency, which makes nanosecond benchmarks non-deterministic unless frequency is pinned. Graviton4 provides consistent, predictable performance that matches production conditions.

How to Use This Page

If you are evaluating video infrastructure for your product, here is how to read this data:

• If protocol-level performance is your priority (high-scale, latency-sensitive, many concurrent operations): V100's numbers are unmatched by any published competitor data.
• If global edge coverage matters most (users worldwide, diverse network conditions): Agora and Twilio have more published evidence of global deployment.
• If developer experience and ecosystem matter most (fast integration, many SDKs, large community): Twilio and Daily have mature ecosystems. LiveKit has a strong open-source community.
• If you need VOD and streaming alongside conferencing: Mux specializes in video-on-demand and streaming infrastructure.
• If post-quantum security is a requirement: V100 is the only vendor with published post-quantum crypto tests (17/17 passing).
• If you want open source you can self-host: LiveKit and coturn are fully open source. V100's TURN crate is partially open.

Future Updates

This page will be updated as new benchmark data becomes available from any vendor. Planned additions from V100:

• DONE: p99 tail latency numbers (13.4ms @ 50 concurrent, gateway benchmark)
• DONE: Gateway throughput (220,661 RPS on Apple Silicon, 0.01ms server processing)
• p999 tail latency numbers
• Multi-region benchmark results
• Mobile SDK end-to-end latency
• Large-scale concurrent participant benchmarks (100+, 1000+)
• Simulcast/SVC layer switching latency

If you represent a vendor listed in this comparison and would like to submit corrected or additional benchmark data, contact engineering@v100.ai. We will verify the methodology and update the table.

For deeper dives into V100's performance, read Inside V100's 263ns Pipeline Tick, Fastest WebRTC Server 2026, or Rust vs C++ for Video Servers.