Sources reviewed 20 Oct 2026. Event dates remain attached to the original evidence.
Riverlane’s April 2026 performance note reports a mean latency of 16.32 microseconds using replayed experimental data and a QPU/control emulator. This is a decoder-system experiment, with an explicit boundary separating it from operation on a connected live quantum processor.
That boundary makes the result more useful, because it tells readers exactly which uncertainty remains. Recorded syndromes can test whether a decoder keeps pace with an incoming stream; they cannot reproduce every consequence of a physical machine responding to the decoder. The average is only one part of the story. A small number of late decisions can matter if an algorithm must wait for them, so a mature comparison should include a latency distribution and the conditions that create its slow tail. Equally, a faster answer has limited value if its error estimate becomes worse. The strongest next evidence would show decoding quality, throughput and response timing together, with a reproducible input set. Riverlane’s card should track those coupled properties and identify the transition from a controlled replay to sustained physical feedback as its next milestone.
For a reader evaluating Riverlane, the practical question is whether demonstrated decoding speed survives connection to a continuously operating experiment. A useful next evidence check is specific: request a live syndrome stream with cycle timestamps, decoder backlog and the fraction of deadlines missed. A replay or emulator result can understate the interruptions, wiring delays and burst errors of a live control loop. These are proposed tests for judging a later update, not claims that the company has already passed them.
Security status: No public security verified in reviewed material; directory/watch profile only
Facts, comparisons and next evidence
At a glance
- label
- Quantum role
- value
- Error-correction decoding
- label
- Evidence date
- value
- 2026-04-09
- label
- Assessment action
- value
- Evidence enrichment
Dated milestones
- date
- 2026-04-09
- Date scope
- source publication date; unknown if undated
- event
- Real-time decoder evidence released
- status
- Published primary evidence; retain the narrower maturity statement
- what it does not establish
- A replay or emulator result can understate the interruptions, wiring delays and burst errors of a live control loop.
Quantum role
- layer
- Error-correction decoding
- Question
- Whether demonstrated decoding speed survives connection to a continuously operating experiment.
Questions for comparison
- Latency distribution, not just mean
- Logical decoding quality at stated noise
- Live versus replayed syndrome stream
Related approaches
- name
- Qblox
- relationship
- Proposed comparison of relevant dimensions; not a claim of equivalent products or a ranking
- dimensions
- Latency distribution, not just mean
- Logical decoding quality at stated noise
- Live versus replayed syndrome stream
- name
- SEEQC
- relationship
- Proposed comparison of relevant dimensions; not a claim of equivalent products or a ranking
- dimensions
- Latency distribution, not just mean
- Logical decoding quality at stated noise
- Live versus replayed syndrome stream
Limits and missing evidence
- A replay or emulator result can understate the interruptions, wiring delays and burst errors of a live control loop.
- Sustained live-QPU feedback evidence
- Tail latency and buffer occupancy
- Matched decoding-accuracy benchmark
What would change this assessment
- trigger
- Request a live syndrome stream with cycle timestamps, decoder backlog and the fraction of deadlines missed.
- Evidence needed
- Dated primary technical report, product specification or customer/issuer disclosure directly answering the test.
- Test
- Identify the configuration, time boundary and measured outcome; retain unsuccessful attempts and stated limitations.
- Limit
- A replay or emulator result can understate the interruptions, wiring delays and burst errors of a live control loop.
A starting question
- question
- Why does “real time” need a start and an end?
- answer
- A timing number can cover only decoding, or it can include measurement transfer and the next control action. Both can be valid measurements, but they answer different questions. The boundaries must be stated before comparing them.
Original sources and scope
- Riverlane real-time QEC system performance ↗Source dated 9 Apr 2026
Reported latency uses replayed experimental data and a QPU/control emulator; not a live QPU. The source itself cautions against like-for-like comparison with Google.