Skip to content
HARDWARE · HARDWARE IN PRACTICE

IBM Made Its Quantum Chip Faster by Making It Wait Less

Nighthawk r2 attacks the pause between runs. Its three headline numbers describe different things, and should stay that way.

Published Updated Source report Sources checked
My reading list
Gold-colored refrigeration stages and wiring of an IBM Quantum System One at IBM's Yorktown Heights research center.
IBM Quantum System One at the Thomas J. Watson Research Center in Yorktown Heights, New York, photographed in 2024. Context image for IBM quantum hardware—not Nighthawk r2 or a verified Nighthawk installation.Photo: Onri Jay Benally / OJB Quantum · CC BY 4.0Full image credit

Sometimes the way to make a computer faster is to stop making it wait.

IBM’s Nighthawk r2, announced on August 31, 2026, targets the pause between quantum circuit runs. Its 120 programmable each have a dedicated reset element that helps return them to a known starting state before the next run.[1]

That matters because a quantum experiment is rarely one calculation followed by one definitive answer. Researchers often repeat circuits many times to estimate a result. Time spent preparing for the next repetition adds up.[1][2]

IBM reports more than 100,000 circuit executions per second, compared with roughly 4,000 on its Heron fleet: up to 25 times the circuit throughput in the company’s comparison. This is a repetition-rate claim, not a promise that every application finishes 25 times faster.[1]

The eye-catching 25-nanosecond number needs a separate explanation. It is the qubit’s effective energy-relaxation time while active reset is enabled, not the duration of a complete reset or a whole circuit. IBM says the idle gap between runs can fall to as little as one microsecond.[1]

Three distinct IBM Nighthawk r2 metrics: about 25 nanoseconds energy relaxation during active reset, as little as one microsecond idle gap, and more than 100,000 circuit executions per second under reported conditions.
Three separate Nighthawk r2 measurements reported by IBM: about 25 ns effective energy-relaxation time during active reset, as little as 1 microsecond idle time between runs and more than 100,000 circuit executions per second under the reported conditions. These are not three ways to state a whole-application runtime.Original editorial graphic supplied by QubitWire in LLL.pdf. Facts are attributed to the linked primary sources; this is not photography. QubitWire · View full-size graphic · Original QubitWire editorial graphicFull image credit

That distinction is worth keeping even in a headline graphic. A physical relaxation time, the delay between repetitions and completed circuits per second are three different measurements. Combining them into a single “quantum speed” number hides what the engineering actually changed.[1][2]

Faster repetition could make measurement-heavy research and experiments more practical. But useful performance still depends on the circuit, control system, error rates and the rest of the workflow. IBM’s reported retention of Heron-class matters because faster unreliable results would not solve the problem.[1][2]

Nighthawk r2 is a reminder to look beyond the most photogenic number on a specification sheet. Adding qubits is one route forward. Removing avoidable waiting is another. The real test is how quickly the whole system can produce an answer worth using.

Keep your reading trail

Your Updates →

Evidence & context

3 linked sources

IBM-reported hardware measurements. Energy-relaxation time, idle gap and circuit throughput are distinct; the comparison is workload-dependent and does not establish universal application or classical-computing advantage.

How to read the evidence and dates

An announcement records what an organization stated. An experiment reports an observation. A simulation or resource estimate depends on its assumptions. QubitWire’s analysis connects these sources; the labels are not quality scores.

Published is the article’s first QubitWire publication. Updated marks a substantive content change. Sources checked records a review of the underlying evidence. An older paper can support a new explanation, and another press release about the same work is not independent replication.

For material corrections, check the article’s context note and source trail. A routine formatting or link change does not create a new scientific result.

QubitWire take

A shorter pause can matter as much as a bigger processor.

Sources

  1. IBM Quantum — IBM Quantum Nighthawk r2: more circuits, faster

    Company hardware announcement. 2026-08-31.

  2. IBM Quantum — How to measure the performance of a quantum computer

    Company methodology explainer. 2026.

  3. IBM Quantum Compute Service changelog
READ NEXT

Continue exploring

All Hardware stories
  1. Related reading

    Quantum’s Hidden Cost Is Doing the Same Job Again and Again

    An IBM preprint explores how to reduce the measurement burden behind cleaner answers. Its 63-fold figure needs a careful label.

    Published · Source report · Sources checked
  2. Related reading

    Quantum Computers Can Make Mistakes While They Wait

    Qubits can accumulate errors while they wait. A surface-code experiment shows why the pauses between operations deserve more attention.

    Published · Sources checked
THE QUANTUM BRIEFING

A clearer signal.
Read the latest edition.

A little perspective on a fast-moving field.

Read the on-site briefing →

Read selected quantum coverage in the on-site briefing, or register your interest below.