Qblox and Riverlane demonstrate real-time QEC loop with 11.886 μs round trip at code distance 9; correction performance not presented

Qblox and Riverlane demonstrated a real-time quantum error correctionquantum error correction量子誤り訂正 / Quantum Error Correction / QECA technique that distributes information across multiple physical qubits and detects and corrects errors without directly disturbing the quantum state.QI NoteSimply implementing it does not automatically provide practical fault tolerance. What matters is whether the logical error rate is improved relative to the physical error rate. (QEC) feedback loop on physical hardware that covers the full path from qubitqubitQubit / Quantum Bit / QubitThe basic unit of information in a quantum computer. It can represent not only 0 or 1 but also a quantum state that is a superposition of them.QI NoteHaving more qubits does not necessarily mean higher performance. Error rates, connectivity, coherence time, and the number of logical qubits are also important. readout through syndrome generation, decoding, and conditional correction. Using emulated measurement data rather than outputs from physical qubitsphysical qubitsPhysical Qubit / Physical QubitIndividual qubits that are physically created and manipulated on a quantum processor. They are also used to form logical qubits.QI NoteA large number of physical qubits does not by itself indicate practical computational capability. Error rates, connectivity, and the number of physical qubits required per logical qubit are also important., they recorded total round-trip latencies of 6.886 microseconds on Surface-17 and 11.886 microseconds on Surface-161.

Summary of the announcement

In the demonstration, Qblox’s quantum control system Cluster and Riverlane’s QEC system Deltaflow 2 were integrated using the open standard QECi, which connects control hardware and decoders. Qblox generated syndromes from measurement data and sent them to Deltaflow 2; Deltaflow returned correction commands to the control sequencer based on decode results. The experiment tested rotated planar surface codes with code distances 3, 5, 7, and 9, corresponding to Surface-17, Surface-49, Surface-97, and Surface-161 configurations. Total round-trip latency including readout integration time ranged from 6.886 microseconds for Surface-17 to 11.886 microseconds for Surface-161, with all configurations meeting the published short-term target of under 20 microseconds. Qblox-side latency increased from 1.114 microseconds to 1.220 microseconds as the number of physical qubits rose from 17 to 161, an increase of 106 nanoseconds. Deltaflow 2 processed 50,000 QEC cycles continuously. However, the demonstration used emulated qubit measurement data, not measurements from physical qubits, so it does not present QEC performance on real hardware.

Key points

• They implemented the complete hardware QEC feedback path: readout, syndrome generation, decoding, and conditional correction.
• Total round-trip latency was 6.886 microseconds for Surface-17 and 11.886 microseconds for Surface-161.
• Qblox-side latency rose by only 106 nanoseconds as the number of physical qubits increased from 17 to 161.
• Deltaflow 2 continuously processed 50,000 QEC cycles, keeping pace with syndrome-generation throughputthroughputThroughput / ThroughputA metric indicating the amount of work that can be processed per unit time. In quantum computing, it represents how quickly circuits or jobs can be repeatedly executed, among other things.QI NoteThe definition and units of throughput vary between companies and systems. When comparing, check not only the raw number of executions but also conditions such as circuit size, accuracy, and wait times..
• While supporting the full QECi specification, the demonstration used emulated measurement data rather than outputs from physical qubits.

Technical and commercial significance

Technically, the result is significant because the control system maintained nearly constant latency as code distance and physical-qubit count increased, and the complete QEC loop including decoder processing operated within 20 microseconds. The separation of control hardware and decoder shows that improvements to the decoder can be reflected in reduced total round-trip latency.

From a business perspective, a QECi-based architecture that connects different controllers and decoders could form an integration foundation that isn’t locked into a specific code or workflow. However, the announcement does not show whether the same performance holds with physical qubit outputs, multiple Cluster units, or at scales beyond code distance 9.

What to watch next

The next question is whether the correction loop can run with similar latency and stability when fed measurement data from physical qubits. Latency behavior for code distances beyond 9, latency when multiple Clusters are connected, and the decoder’s ability to keep up during long-duration operation are also important. Publication of interoperability results with codes other than the surface codesurface codeSurface Code / Surface Code / Surface Quantum Error-Correcting CodeA representative quantum error-correcting code that arranges qubits on a lattice and detects and corrects errors by repeatedly performing local measurements.QI NoteIt is regarded as promising because it is relatively easy to implement, but the required number of physical qubits varies greatly depending on error rates, code distance, and other factors. In company announcements, it is important to confirm the assumptions behind “how many physical qubits make one logical qubit.” or with other QECi-compatible decoders would help assess the standard’s generality.

✍️ Quantum Index Analysis

The most important caveat in this demonstration is that while the “speed” of the QECQEC量子誤り訂正 / Quantum Error Correction / QECA technique that distributes information across multiple physical qubits and detects and corrects errors without directly disturbing the quantum state.QI NoteSimply implementing it does not automatically provide practical fault tolerance. What matters is whether the logical error rate is improved relative to the physical error rate. loop is presented in detail, how “correctly” the loop actually corrected errors is not shown. Processing from syndrome generation through decoding and conditional correction in 11.886 microseconds at code distance 9 using emulated measurement data is meaningful as a real-time control baseline.

However, the announcement lacks metrics such as logical error rates before and after correction, decoding accuracy, and miscorrection rates. Consequently, it is not possible to judge whether the lower latency was achieved while maintaining sufficient correction performance. This is analogous to reporting AI inference speedups without showing whether accuracy was preserved. Fast response is not useful if the correctness of the results cannot also be confirmed.

Qblox reports that an update to Deltaflow 2 reduced Surface-17 round-trip latency from 8.308 microseconds to 6.886 microseconds—about a 17% improvement. Yet the announcement does not provide numbers showing whether decode performance was maintained before and after that optimization. While there is no evidence that the speedup sacrificed accuracy, the possibility cannot be ruled out based on the data presented.

Regarding the continuous processing of 50,000 QEC cycles, the claim mainly demonstrates throughputthroughputThroughput / ThroughputA metric indicating the amount of work that can be processed per unit time. In quantum computing, it represents how quickly circuits or jobs can be repeatedly executed, among other things.QI NoteThe definition and units of throughput vary between companies and systems. When comparing, check not only the raw number of executions but also conditions such as circuit size, accuracy, and wait times.—that the processing stack can keep up with the data generation rate. It does not indicate how much quantum information error was suppressed over those 50,000 cycles.

To evaluate this achievement as a QEC system, the next step—before a demonstration on physical qubitsphysical qubitsPhysical Qubit / Physical QubitIndividual qubits that are physically created and manipulated on a quantum processor. They are also used to form logical qubits.QI NoteA large number of physical qubits does not by itself indicate practical computational capability. Error rates, connectivity, and the number of physical qubits required per logical qubit are also important.—should be to show latency, decoding accuracy, and logical error rates together in the same emulated environment. Only when low latency and correction performance are both confirmed can the work be upgraded in assessment from a “fast feedback loop” to a “high-performance QEC system.”

NETWORKSee the industry network around Qblox →

Related articles

• Infleqtion supports operation of Japan’s first full-stack neutral-atom quantum computer “Shunkai”
• Yaqumo validates neutral-atom quantum computer hardware with Fujitsu, connecting STAR architecture to cloud infrastructure
• Xanadu and ASML collaborate on advanced lithography to reduce optical losses in photonic quantum chips

Sources

Read the announcement (Qblox)

Read the announcement (Riverlane)