IBM’s Quantum Advantage Is Real, and Still Mostly Useless | Qubit #49
IBM’s latest quantum result is real progress, not noise, but the commercial interpretation is being inflated beyond recognition. A 120-qubit Nighthawk r2 processor reportedly generated one million samples in 19 seconds for a task estimated to require roughly 110 years on Frontier, implying a classical speedup of about 1.8 trillion times. That is the kind of result quantum computing needs: a reproducible experiment on commercially accessible hardware, with the circuits, samples, and analysis code released for independent checking.
It is also exactly the kind of result that investors should treat with suspicion before treating it as a business milestone. The task was designed to expose the weakness of a particular class of classical simulation methods. The 110-year estimate is not a statement that all classical computers, using all possible algorithms, would need a century. It rests on a specific tensor-network simulation approach, assumptions about memory, and a benchmark selected because quantum hardware handles it unusually well. IBM has demonstrated a serious computational separation on a contrived workload. It has not demonstrated faster drug discovery, better portfolio optimization, cheaper logistics, or a useful replacement for a high-performance computing cluster.
That distinction matters because “quantum advantage” has quietly acquired two meanings. In the scientific sense, IBM’s result may qualify: a quantum processor performs a defined sampling task beyond practical classical reach. In the enterprise sense, it does not. The output still needs to be connected to a problem customers pay to solve, and the machine still needs to deliver reliable answers rather than merely hard-to-simulate ones. The headline is a win for quantum information science. It is not yet a revenue forecast.
The important signal is not the 1.8 trillion figure. Large speedup multipliers are easy to manufacture once the classical comparator is chosen narrowly. The stronger signal is that IBM ran the experiment on a cloud-accessible processor rather than on a laboratory system with no operational path to users. That lowers the distance between demonstration and deployment, even if it does not eliminate it.
The weak point is the workload itself. Sampling circuits of this kind are valuable because they stress classical simulation, but they do not automatically produce an economically meaningful answer. A customer does not buy a probability distribution merely because a supercomputer struggles to reproduce it. The customer buys a decision, a prediction, a molecule, a schedule, or a financial outcome with a measurable advantage over existing methods.
This is where qubit counts mislead. IBM’s 120 physical qubits are not 120 reliable computational qubits. Each physical qubit is noisy, and every gate introduces some probability of error. A circuit can be too deep for useful information to survive even when the chip has an impressive headline count. For this benchmark, the objective is not necessarily to preserve a long algorithmic computation with fault-tolerant accuracy. It is to generate samples whose statistical properties are difficult for classical methods to mimic. Those are different engineering targets.
Error correction is the dividing line. Google’s separate announcement, claiming roughly a 40-fold reduction in errors on its Willow chip through magic-state cultivation, addresses a more consequential problem, but the phrase “40-fold reduction” needs careful handling. Magic states are an essential resource for universal fault-tolerant quantum computing, and improving their quality can reduce the overhead required for error correction. But reducing the error of a resource state is not the same as operating a full machine with millions of logical operations at an acceptable failure rate.
The practical metric executives should request is logical error per operation at scale, not the best physical error rate in a controlled experiment. They should also ask how many physical qubits are consumed per logical qubit, how much classical decoding is required, how long the logical qubits remain coherent, and whether the workload survives realistic input and output costs. Vendors that answer only with physical qubit counts are discussing capacity without discussing usable computation.
IBM deserves credit for choosing a benchmark that exposes a genuine boundary between quantum sampling and classical simulation. But the experiment also illustrates the industry’s recurring trick: prove that a classical machine cannot efficiently reproduce a quantum output, then imply that the output must therefore be useful. That implication is false. Hard to simulate is not the same as valuable to compute.
The more interesting competitive question is therefore not IBM versus Google on headline advantage. It is whether either company can turn these isolated demonstrations into a stack where error-corrected computation is cheaper, faster, or more accurate than a classical alternative for a customer’s actual workflow. Google currently has the cleaner error-correction narrative. IBM has the stronger commercial distribution story, with cloud access and a broader enterprise ecosystem. Neither has closed the gap between laboratory capability and repeatable economic utility.
This result moves the timeline for scientific quantum advantage forward, but it does not materially move the timeline for enterprise quantum advantage. The former is already here in narrow forms. The latter still depends on fault-tolerant systems capable of long computations with predictable logical error rates.
For executives, the implication is not to launch a quantum application program around IBM’s benchmark. It is to prepare the data, algorithms, vendor contracts, and cryptographic migration plans that will matter if useful machines arrive. Quantum readiness is mostly classical work performed before the quantum hardware is ready: identifying optimization problems with exploitable structure, creating high-quality simulation baselines, and replacing vulnerable public-key cryptography.
The security timeline deserves more urgency than the computing timeline. A recent briefing to World Trade Organization officials warned that current encryption could face a quantum threat within roughly five years, while also highlighting the “harvest now, decrypt later” risk, in which encrypted data is collected today for future decryption. That forecast is aggressive, but the migration problem is real regardless of whether a useful cryptographically relevant machine arrives on schedule. Encryption upgrades take years because certificates, devices, vendors, protocols, and archived data all need to be inventoried and replaced.
The next meaningful milestone for IBM is not another impossible-to-simulate sampling result. It is a workload with three properties: an independently validated classical baseline, an output that changes a real business decision, and an end-to-end cost that remains competitive after error correction, compilation, queueing, and data movement. Without all three, “advantage” remains a physics result wearing a commercial costume.
Watch IBM’s logical-qubit and error-correction disclosures, Google’s resource overhead for magic-state cultivation, and whether either company publishes customer-relevant workloads rather than increasingly exotic benchmarks. Watch also for the quiet winners around the hardware, including control electronics, cryogenic systems, error-correction software, and post-quantum security vendors. Those businesses can monetize the transition before universal fault tolerance arrives.
IBM has shown that a commercial quantum processor can produce a result that classical hardware cannot practically reproduce under a defined simulation strategy. That is genuine progress. The mistake is calling it the beginning of the quantum economy. It is better understood as a boundary marker: quantum machines are becoming difficult to imitate, but they have not yet become useful enough to replace the machines we already own.