Quantum Hardware Leaderboard
Compare quantum devices on one measurement at a time, from the public corpus . Each row shows that device's latest measurement, its date and its source. Vendor-reported rows are manufacturer claims, not independently reproduced here. For the long-run picture, see the tracker. How the corpus works →
Best 2Q fidelity
2Q gate fidelity
Median 2Q error
Median T1 (µs)
Median T2 (µs)
Median readout error
Algorithmic qubits (#AQ)
Quantum Volume
CLOPS
EPLG (error/layer)
Bell-state effective qubits
QFT accuracy
QAOA approx. ratio
Qubits
Median 2Q error: How often a typical two-qubit operation on this chip fails, from the vendor's own calibration.
Showing devices with a measurement in the last two years (48 older hidden).
Include older devices
| Rank | Maker | Device | Median 2Q error | Source / licence | Measured |
|---|---|---|---|---|---|
| #1 | ibm | ibm_boston | 0.0013 fails about 1 in 780 | IBM · Apache-2.0 | 2026-04-17 |
| #2 | ibm | ibm_aachen | 0.0014 fails about 1 in 700 | IBM · Apache-2.0 | 2026-04-17 |
| #3 | ibm | ibm_pittsburgh | 0.0016 fails about 1 in 640 | IBM · Apache-2.0 | 2026-04-17 |
| #4 | ibm | ibm_kingston | 0.0017 fails about 1 in 580 | IBM · Apache-2.0 | 2026-04-15 |
| #5 | ibm | ibm_phoenix | 0.0019 fails about 1 in 530 | IBM · Apache-2.0 | 2026-11-10 |
| #6 | ibm | ibm_berlin | 0.0021 fails about 1 in 470 | IBM · Apache-2.0 | 2026-04-17 |
| #7 | ibm | ibm_chicago | 0.0023 fails about 1 in 430 | IBM · Apache-2.0 | 2026-11-10 |
| #8 | ibm | ibm_miami | 0.0029 fails about 1 in 340 | IBM · Apache-2.0 | 2026-04-17 |
| #9 | ibm | ibm_marrakesh | 0.0032 fails about 1 in 320 | IBM · Apache-2.0 | 2025-02-26 |
| #10 | ibm | ibm_fez | 0.0038 fails about 1 in 260 | IBM · Apache-2.0 | 2025-02-26 |
| #11 | ibm | ibm_torino | 0.0041 fails about 1 in 250 | IBM · Apache-2.0 | 2025-02-26 |
| #12 | ibm | ibm_hanoi | 0.0063 fails about 1 in 160 | IBM · Apache-2.0 | 2025-02-26 |
| #13 | ibm | ibm_sherbrooke | 0.0075 fails about 1 in 130 | IBM · Apache-2.0 | 2025-02-26 |
| #14 | ibm | ibm_brisbane | 0.0077 fails about 1 in 130 | IBM · Apache-2.0 | 2025-02-26 |
| #15 | ibm | ibm_kawasaki | 0.0081 fails about 1 in 120 | IBM · Apache-2.0 | 2025-02-26 |
| #16 | ibm | ibm_strasbourg | 0.0082 fails about 1 in 120 | IBM · Apache-2.0 | 2026-04-17 |
| #17 | ibm | ibm_quebec | 0.0084 fails about 1 in 120 | IBM · Apache-2.0 | 2025-02-26 |
| #18 | ibm | ibm_brussels | 0.0086 fails about 1 in 120 | IBM · Apache-2.0 | 2026-04-17 |
| #19 | ibm | ibm_kyiv | 0.0115 fails about 1 in 87 | IBM · Apache-2.0 | 2025-02-26 |
| #20 | ibm | ibm_cusco | 0.0217 fails about 1 in 46 | IBM · Apache-2.0 | 2025-02-26 |
Sources & attribution.
IBM rows are real device calibration snapshots published in Qiskit's fake backends (Apache-2.0), each with its true date.
Metriq rows are community benchmark runs from metriq.info (CC-BY-4.0).
Vendor-reported rows are specifications published by the manufacturer and are shown as claims, with the source link recorded in each snapshot's provenance.
Metrics differ in what they measure and how they're obtained, so compare within a metric and mind the source badge.