Skip to content

quicX Interoperability Status

This document records the latest baseline interoperability results of quicX against the major QUIC implementations and is the canonical version to cite externally.

Live interactive matrix — the newest round auto-published by weekly CI: https://caozhiyi.cc/interop/. This document is the curated baseline snapshot with root-cause analysis.

For test methodology, commands, and environment, see guide/interop_runbook.md.

ItemValue
Run modeupstream quic-interop-runner full matrix (quic-network-simulator / ns-3 topology)
Peers under test17 third-party implementations (14 bidirectional + nginx / haproxy server-only + chrome client-only)
Scenarios under test24 (22 protocol-conformance + 2 performance measurements)
Total cases768 (PASS 625 / FAIL 48 / UNSUPPORTED 95), including a quicX ↔ quicX self-check
Overall effective pass rate92.87% (625 / 673, excluding UNSUPPORTED)
RFC conformance pass rate93.62% (572 / 611; client mode 294/312 = 94.23%, server mode 278/299 = 92.98%)
Performance pass rate85.48% (53 / 62)

  • ✅ Across the full 24-scenario × 17-peer matrix plus a quicX ↔ quicX self-check (768 cases, run on 2026-10-10), quicX achieves an overall effective pass rate of 92.87%, up 2.27pp from the previous round (90.60%).
  • ✅ 12 scenarios at 100%: handshake, transfer, longrtt, chacha20, retry, http3, blackhole, ecn, transferloss, transfercorruption, ipv6, plus goodput (30/30, avg 9.17 Mbps, peak bandwidth utilization 95.5%).
  • ✅ Server mode recovered markedly (86.28% → 92.98%): amplificationlimit (6/14 → 13/14), rebind-addr (10/14 → 14/14), rebind-port (10/14 → 13/14), and handshakeloss (10/13 → 12/13) returned to passing broadly; client-mode amplificationlimit (14/16 → 15/16) and handshakeloss (14/15 → 15/15) also improved.
  • ⚠️ Main regression this round: crosstraffic 27/30 → 21/30 (client mode 14/16 → 8/16; ngtcp2 / go-x-net / quic-go / quiche / aioquic / nginx missed the threshold).
  • ⚠️ Current weak spots: connectionmigration (7/19, 36.8%), rebind-addr (22/30, 73.3%), rebind-port (23/30, 76.7%), server-mode keyupdate (8/10) and zerortt (10/12).

  • Source: one full-matrix run of the upstream quic-interop-runner (result files quicx_as_client_full.json / quicx_as_server_full.json, log dirs logs_full_{client,server}_20261010_142617).
  • Environment: Linux host, Docker + ns-3 network simulation (leftnet ↔ sim ↔ rightnet); quicX runs from locally built interop_{server,client} binaries.
  • Coverage: 24 scenarios × (16 server-side peers + 15 client-side peers + a quicX ↔ quicX self-check) = 768 combinations; the self-check passed 21/21 in the server direction.
  • Delta vs. previous baseline: the previous round used the same caliber without the self-check (744 cases, 90.60% effective). This round is up 2.27pp, driven mainly by server-mode recovery of amplificationlimit, rebind-addr, rebind-port, and handshakeloss; client-mode amplificationlimit and handshakeloss improved, and connectionmigration edged up (6/19 → 7/19). The regression concentrates in client-mode crosstraffic (14/16 → 8/16). The upstream matrix does not include multiconnect / versionnegotiation.
MarkMeaning
✅SUCCEEDED
❌FAILED (test failure / throughput below threshold)
➖UNSUPPORTED — peer or scenario unsupported
—N/A — combination not run (peer does not ship that role)
MetricValue
Total cases768
✅ Passed625
❌ Failed48
➖ Unsupported95
Effective pass rate (excl. Unsupported)625 / 673 ≈ 92.87%
RFC conformance pass rate572 / 611 ≈ 93.62% (client 294/312 = 94.23%; server 278/299 = 92.98%)
Performance pass rate53 / 62 ≈ 85.48% (goodput 30/30; crosstraffic 21/30)
Pass rate incl. Unsupported625 / 768 ≈ 81.4%
Test scenarioShort nameClient-mode pass rateServer-mode pass rateCombined effective pass rateDescription
handshakeH16/16 (100.0%)14/14 (100.0%)30/30 (100.0%)Handshake completes successfully.
transferDC16/16 (100.0%)14/14 (100.0%)30/30 (100.0%)Stream data is being sent and received correctly. Connection close completes with a zero error code.
longrttLR16/16 (100.0%)14/14 (100.0%)30/30 (100.0%)Handshake completes when RTT is long.
chacha20C2014/14 (100.0%)10/10 (100.0%)24/24 (100.0%)Handshake completes using ChaCha20.
multiplexingM16/16 (100.0%)13/14 (92.9%)29/30 (96.7%)Thousands of files are transferred over a single connection, and server increased stream limits to accomodate client requests.
retryS14/14 (100.0%)12/12 (100.0%)26/26 (100.0%)Server sends a Retry, and a subsequent connection using the Retry token completes successfully.
resumptionR14/15 (93.3%)12/12 (100.0%)26/27 (96.3%)Connection is established using TLS Session Resumption.
zerorttZ14/14 (100.0%)10/12 (83.3%)24/26 (92.3%)0-RTT data is being sent and acted on.
http3314/14 (100.0%)13/13 (100.0%)27/27 (100.0%)An H3 transaction succeeded.
blackholeB16/16 (100.0%)14/14 (100.0%)30/30 (100.0%)Transfer succeeds despite underlying network blacking out for a few seconds.
keyupdateU16/16 (100.0%)8/10 (80.0%)24/26 (92.3%)One of the two endpoints updates keys and the peer responds correctly.
ecnE6/6 (100.0%)6/6 (100.0%)12/12 (100.0%)Handshake completes successfully.
amplificationlimitA15/16 (93.8%)13/14 (92.9%)28/30 (93.3%)The server obeys the 3x amplification limit.
handshakelossL115/15 (100.0%)12/13 (92.3%)27/28 (96.4%)Handshake completes under extreme packet loss.
transferlossL216/16 (100.0%)14/14 (100.0%)30/30 (100.0%)Transfer completes under moderate packet loss.
handshakecorruptionC115/15 (100.0%)11/13 (84.6%)26/28 (92.9%)Handshake completes under extreme packet corruption.
transfercorruptionC216/16 (100.0%)14/14 (100.0%)30/30 (100.0%)Transfer completes under moderate packet corruption.
ipv6616/16 (100.0%)14/14 (100.0%)30/30 (100.0%)A transfer across an IPv6-only network succeeded.
v2V28/8 (100.0%)7/8 (87.5%)15/16 (93.8%)Server should select QUIC v2 in compatible version negotiation.
rebind-portBP10/16 (62.5%)13/14 (92.9%)23/30 (76.7%)Transfer completes under frequent port rebindings on the client side.
rebind-addrBA8/16 (50.0%)14/14 (100.0%)22/30 (73.3%)Transfer completes under frequent IP address and port rebindings on the client side.
connectionmigrationCM3/5 (60.0%)4/14 (28.6%)7/19 (36.8%)A transfer succeeded during which the client performed an active migration.
goodputG16/16 (100.0%)14/14 (100.0%)30/30 (100.0%)Measures connection goodput over a 10Mbps link.
crosstrafficC8/16 (50.0%)13/14 (92.9%)21/30 (70.0%)Measures goodput over a 10Mbps link when competing with a TCP (cubic) connection.

RankImplementationClient mode (initiator)Server mode (responder)Protocol-feature pass rateCombined effective pass rateStatus
1neqo24/24 (100.0%)23/24 (95.8%)43/44 (97.7%)47/48 (97.9%)🌟 Excellent
2picoquic24/24 (100.0%)23/24 (95.8%)43/44 (97.7%)47/48 (97.9%)🌟 Excellent
3lsquic23/24 (95.8%)23/23 (100.0%)42/43 (97.7%)46/47 (97.9%)🌟 Excellent
4aioquic21/22 (95.5%)22/23 (95.7%)40/41 (97.6%)43/45 (95.6%)🌟 Excellent
5msquic21/21 (100.0%)20/22 (90.9%)37/39 (94.9%)41/43 (95.3%)🌟 Excellent
6quic-go20/21 (95.2%)20/22 (90.9%)37/39 (94.9%)40/43 (93.0%)🌟 Excellent
7xquic21/21 (100.0%)19/22 (86.4%)37/39 (94.9%)40/43 (93.0%)🌟 Excellent
8ngtcp220/24 (83.3%)24/24 (100.0%)41/44 (93.2%)44/48 (91.7%)🌟 Excellent
9quinn22/22 (100.0%)21/24 (87.5%)39/42 (92.9%)43/46 (93.5%)🌟 Excellent
10s2n-quic20/22 (90.9%)19/20 (95.0%)35/38 (92.1%)39/42 (92.9%)🌟 Excellent
11quiche18/21 (85.7%)19/20 (95.0%)34/37 (91.9%)37/41 (90.2%)🌟 Excellent
12kwik19/22 (86.4%)21/23 (91.3%)37/41 (90.2%)40/45 (88.9%)🌟 Excellent
13haproxy20/22 (90.9%)N/A18/20 (90.0%)20/22 (90.9%)🌟 Excellent
14nginx18/21 (85.7%)N/A17/19 (89.5%)18/21 (85.7%)👍 Good
15go-x-net11/14 (78.6%)14/15 (93.3%)22/25 (88.0%)25/29 (86.2%)👍 Good
16mvfst16/19 (84.2%)14/18 (77.8%)27/33 (81.8%)30/37 (81.1%)👍 Good
17chromeN/A1/1 (100.0%)1/1 (100.0%)1/1 (100.0%)🌟 Excellent

Note: “client mode” means quicX as the client connecting to the peer’s server; “server mode” means the peer as the client connecting to quicX’s server. The “protocol-feature pass rate” excludes the goodput / crosstraffic performance scenarios.


Description: Handshake completes successfully.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅✅——✅➖

Description: Stream data is being sent and received correctly. Connection close completes with a zero error code.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅✅——✅➖

Description: Handshake completes when RTT is long.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅✅——✅➖

Description: Handshake completes using ChaCha20.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖✅✅✅✅✅✅➖✅✅✅✅✅✅✅—
quicX as Server✅➖✅➖➖✅✅✅➖✅✅✅✅——✅➖

Description: Thousands of files are transferred over a single connection, and server increased stream limits to accomodate client requests.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅❌——✅➖

Description: Server sends a Retry, and a subsequent connection using the Retry token completes successfully.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖✅✅✅✅✅✅➖✅✅✅✅✅✅✅—
quicX as Server✅➖✅✅✅✅✅✅➖✅✅✅✅——✅➖

Description: Connection is established using TLS Session Resumption.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖✅✅✅✅❌✅✅✅✅✅✅✅✅✅—
quicX as Server✅➖✅✅✅✅✅✅➖✅✅✅✅——✅➖

Description: 0-RTT data is being sent and acted on.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖✅➖✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅➖✅➖✅✅✅✅❌✅❌✅✅——✅➖

Description: An H3 transaction succeeded.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖✅✅✅✅✅✅✅✅➖✅✅✅✅✅—
quicX as Server✅➖✅✅✅✅✅✅✅✅➖✅✅——✅✅

Description: Transfer succeeds despite underlying network blacking out for a few seconds.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅✅——✅➖

Description: One of the two endpoints updates keys and the peer responds correctly.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅➖➖✅➖✅➖✅✅❌✅——❌➖

Description: Handshake completes successfully.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖➖✅➖✅✅➖➖➖➖✅➖➖➖✅—
quicX as Server✅➖➖✅➖✅✅➖➖➖➖✅➖——✅➖

Description: The server obeys the 3x amplification limit.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅❌✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅❌✅✅✅✅✅——✅➖

Description: Handshake completes under extreme packet loss.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅➖✅✅✅✅✅✅❌✅✅✅✅——✅➖

Description: Transfer completes under moderate packet loss.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅✅——✅➖

Description: Handshake completes under extreme packet corruption.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅➖❌✅✅✅✅✅❌✅✅✅✅——✅➖

Description: Transfer completes under moderate packet corruption.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅✅——✅➖

Description: A transfer across an IPv6-only network succeeded.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅✅——✅➖

Description: Server should select QUIC v2 in compatible version negotiation.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅➖➖➖➖✅✅✅➖✅✅✅➖➖✅➖—
quicX as Server✅➖➖➖➖✅✅✅➖✅✅✅➖——❌➖

Description: Transfer completes under frequent port rebindings on the client side.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client❌❌✅✅❌✅✅❌✅✅✅✅✅❌❌✅—
quicX as Server✅✅✅✅✅❌✅✅✅✅✅✅✅——✅➖

Description: Transfer completes under frequent IP address and port rebindings on the client side.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client❌❌✅❌❌✅✅❌❌✅✅✅✅❌❌✅—
quicX as Server✅✅✅✅✅✅✅✅✅✅✅✅✅——✅➖

Description: A transfer succeeded during which the client performed an active migration.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client❌➖➖❌➖✅✅➖➖➖➖✅➖➖➖➖—
quicX as Server✅❌❌❌❌✅✅❌❌❌❌✅❌——❌➖

Description: Measures connection goodput over a 10Mbps link.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client✅
9.31 Mbps
✅
8.07 Mbps
✅
9.51 Mbps
✅
9.26 Mbps
✅
9.45 Mbps
✅
8.41 Mbps
✅
9.55 Mbps
✅
8.76 Mbps
✅
9.35 Mbps
✅
8.64 Mbps
✅
8.59 Mbps
✅
9.27 Mbps
✅
9.36 Mbps
✅
9.47 Mbps
✅
9.15 Mbps
✅
8.76 Mbps
—
quicX as Server✅
9.38 Mbps
✅
9.42 Mbps
✅
9.49 Mbps
✅
8.80 Mbps
✅
9.34 Mbps
✅
9.19 Mbps
✅
9.44 Mbps
✅
9.36 Mbps
✅
9.43 Mbps
✅
9.36 Mbps
✅
9.48 Mbps
✅
9.09 Mbps
✅
9.34 Mbps
——✅
9.15 Mbps
➖
Section titled “📊 Measured throughput ranking (10 Mbps link, average: 9.17 Mbps)”
RankPeerRoleStatusDetail (with jitter)ThroughputUtilization
1lsquicquicX as Client✅9549 (± 11) kbps9.55 Mbps95.5%
2quic-goquicX as Client✅9506 (± 1) kbps9.51 Mbps95.1%
3quic-goquicX as Server✅9492 (± 15) kbps9.49 Mbps94.9%
4msquicquicX as Server✅9481 (± 12) kbps9.48 Mbps94.8%
5nginxquicX as Client✅9471 (± 1) kbps9.47 Mbps94.7%
6quichequicX as Client✅9447 (± 4) kbps9.45 Mbps94.5%
7lsquicquicX as Server✅9438 (± 6) kbps9.44 Mbps94.4%
8mvfstquicX as Server✅9429 (± 25) kbps9.43 Mbps94.3%
9go-x-netquicX as Server✅9416 (± 11) kbps9.42 Mbps94.2%
10ngtcp2quicX as Server✅9376 (± 13) kbps9.38 Mbps93.8%
11xquicquicX as Client✅9362 (± 5) kbps9.36 Mbps93.6%
12aioquicquicX as Server✅9361 (± 17) kbps9.36 Mbps93.6%
13kwikquicX as Server✅9358 (± 21) kbps9.36 Mbps93.6%
14mvfstquicX as Client✅9354 (± 29) kbps9.35 Mbps93.5%
15xquicquicX as Server✅9341 (± 91) kbps9.34 Mbps93.4%
16quichequicX as Server✅9337 (± 12) kbps9.34 Mbps93.4%
17ngtcp2quicX as Client✅9307 (± 91) kbps9.31 Mbps93.1%
18picoquicquicX as Client✅9273 (± 51) kbps9.27 Mbps92.7%
19s2n-quicquicX as Client✅9264 (± 37) kbps9.26 Mbps92.6%
20neqoquicX as Server✅9194 (± 18) kbps9.19 Mbps91.9%
21quinnquicX as Server✅9149 (± 18) kbps9.15 Mbps91.5%
22haproxyquicX as Client✅9147 (± 15) kbps9.15 Mbps91.5%
23picoquicquicX as Server✅9093 (± 31) kbps9.09 Mbps90.9%
24s2n-quicquicX as Server✅8803 (± 74) kbps8.80 Mbps88.0%
25quinnquicX as Client✅8761 (± 6) kbps8.76 Mbps87.6%
26kwikquicX as Client✅8756 (± 30) kbps8.76 Mbps87.6%
27aioquicquicX as Client✅8640 (± 21) kbps8.64 Mbps86.4%
28msquicquicX as Client✅8586 (± 42) kbps8.59 Mbps85.9%
29neqoquicX as Client✅8409 (± 28) kbps8.41 Mbps84.1%
30go-x-netquicX as Client✅8069 (± 14) kbps8.07 Mbps80.7%

💡 Performance analysis: quicX excels on the 10 Mbps bottleneck link — all 30 measured combinations in both directions (client mode 16/16, server mode 14/14) pass at 100%, with peak bandwidth utilization of 95.5% (lsquic: 9.55 Mbps) and a global average effective rate of 9.17 Mbps.

Description: Measures goodput over a 10Mbps link when competing with a TCP (cubic) connection.

Role \ Peerngtcp2go-x-netquic-gos2n-quicquicheneqolsquickwikmvfstaioquicmsquicpicoquicxquicnginxhaproxyquinnchrome
quicX as Client❌❌❌✅
4.84 Mbps
❌✅
4.04 Mbps
✅
8.36 Mbps
❌❌❌✅
3.28 Mbps
✅
7.20 Mbps
✅
8.57 Mbps
❌✅
4.75 Mbps
✅
3.03 Mbps
—
quicX as Server✅
4.13 Mbps
✅
4.81 Mbps
✅
4.95 Mbps
✅
4.66 Mbps
✅
5.46 Mbps
✅
4.70 Mbps
✅
5.15 Mbps
✅
5.69 Mbps
✅
6.16 Mbps
✅
7.19 Mbps
✅
6.45 Mbps
✅
4.87 Mbps
❌——✅
5.33 Mbps
➖
RankPeerRoleStatusDetail (with jitter)ThroughputNote
1xquicquicX as Client✅8570 (± 51) kbps8.57 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 85.7%)
2lsquicquicX as Client✅8361 (± 158) kbps8.36 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 83.6%)
3picoquicquicX as Client✅7203 (± 264) kbps7.20 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 72.0%)
4aioquicquicX as Server✅7194 (± 451) kbps7.19 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 71.9%)
5msquicquicX as Server✅6445 (± 446) kbps6.45 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 64.5%)
6mvfstquicX as Server✅6164 (± 223) kbps6.16 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 61.6%)
7kwikquicX as Server✅5687 (± 230) kbps5.69 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 56.9%)
8quichequicX as Server✅5460 (± 556) kbps5.46 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 54.6%)
9quinnquicX as Server✅5328 (± 596) kbps5.33 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 53.3%)
10lsquicquicX as Server✅5150 (± 204) kbps5.15 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 51.5%)
11quic-goquicX as Server✅4953 (± 544) kbps4.95 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 49.5%)
12picoquicquicX as Server✅4865 (± 293) kbps4.87 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 48.6%)
13s2n-quicquicX as Client✅4845 (± 191) kbps4.84 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 48.4%)
14go-x-netquicX as Server✅4812 (± 59) kbps4.81 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 48.1%)
15haproxyquicX as Client✅4746 (± 158) kbps4.75 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 47.5%)
16neqoquicX as Server✅4701 (± 496) kbps4.70 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 47.0%)
17s2n-quicquicX as Server✅4661 (± 332) kbps4.66 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 46.6%)
18ngtcp2quicX as Server✅4127 (± 588) kbps4.13 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 41.3%)
19neqoquicX as Client✅4041 (± 172) kbps4.04 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 40.4%)
20msquicquicX as Client✅3282 (± 78) kbps3.28 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 32.8%)
21quinnquicX as Client✅3030 (± 339) kbps3.03 MbpsFair bandwidth share on the 10 Mbps competing link (utilization 30.3%)
-ngtcp2, go-x-net, quic-go, quiche, kwik, mvfst, aioquic, nginxquicX as Client❌——Throughput below the interop-runner threshold under TCP Cubic competition
-xquicquicX as Server❌——Throughput below the interop-runner threshold under TCP Cubic competition

💡 Competition analysis: as the server, quicX shows steady congestion resilience and bandwidth contention — 13/14 (92.9%) of peer clients meet the threshold (best: aioquic 7.19 Mbps, msquic 6.45 Mbps, mvfst 6.16 Mbps), with only xquic missing it. As the client, 8/16 (50.0%) meet the threshold (best contention efficiency: xquic 8.57 Mbps, lsquic 8.36 Mbps, picoquic 7.20 Mbps); ngtcp2, go-x-net, quic-go, quiche, kwik, mvfst, aioquic, and nginx miss the threshold. Overall TCP Cubic competition pass rate is 70.0% (21/30) — client-mode competition resilience is the main weak spot of this round.