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
Best 2Q fidelity: Success rate of the chip's single best pair of qubits. The best pair flatters the chip; the typical one matters more.
Showing every device ever recorded.
Show current devices only
| Rank | Maker | Device | Best 2Q fidelity | Source / licence | Measured |
|---|---|---|---|---|---|
| #1 | ibm | ibm_berlin | 0.9995 fails about 1 in 1,920 | IBM · Apache-2.0 | 2026-04-17 |
| #2 | ibm | ibm_boston | 0.9993 fails about 1 in 1,530 | IBM · Apache-2.0 | 2026-04-17 |
| #3 | ibm | ibm_aachen | 0.9993 fails about 1 in 1,450 | IBM · Apache-2.0 | 2026-04-17 |
| #4 | ibm | ibm_pittsburgh | 0.9992 fails about 1 in 1,270 | IBM · Apache-2.0 | 2026-04-17 |
| #5 | ibm | ibm_phoenix | 0.9992 fails about 1 in 1,220 | IBM · Apache-2.0 | 2026-11-10 |
| #6 | ibm | ibm_chicago | 0.9992 fails about 1 in 1,200 | IBM · Apache-2.0 | 2026-11-10 |
| #7 | ibm | ibm_kingston | 0.9991 fails about 1 in 1,150 | IBM · Apache-2.0 | 2026-04-15 |
| #8 | ibm | ibm_marrakesh | 0.999 fails about 1 in 970 | IBM · Apache-2.0 | 2025-02-26 |
| #9 | ibm | ibm_miami | 0.9989 fails about 1 in 950 | IBM · Apache-2.0 | 2026-04-17 |
| #10 | ibm | ibm_prague | 0.9985 fails about 1 in 690 | IBM · Apache-2.0 | 2023-01-12 |
| #11 | ibm | ibm_torino | 0.9985 fails about 1 in 670 | IBM · Apache-2.0 | 2025-02-26 |
| #12 | ibm | ibm_fez | 0.9983 fails about 1 in 580 | IBM · Apache-2.0 | 2025-02-26 |
| #13 | ibm | ibm_osaka | 0.9973 fails about 1 in 380 | IBM · Apache-2.0 | 2024-02-28 |
| #14 | ibm | ibm_brussels | 0.9969 fails about 1 in 320 | IBM · Apache-2.0 | 2026-04-17 |
| #15 | ibm | ibm_kyiv | 0.9969 fails about 1 in 320 | IBM · Apache-2.0 | 2025-02-26 |
| #16 | ibm | ibm_quebec | 0.9969 fails about 1 in 320 | IBM · Apache-2.0 | 2025-02-26 |
| #17 | ibm | ibm_strasbourg | 0.9968 fails about 1 in 310 | IBM · Apache-2.0 | 2026-04-17 |
| #18 | ibm | ibm_sherbrooke | 0.9965 fails about 1 in 290 | IBM · Apache-2.0 | 2025-02-26 |
| #19 | ibm | ibm_geneva | 0.9964 fails about 1 in 270 | IBM · Apache-2.0 | 2022-06-24 |
| #20 | ibm | ibm_peekskill | 0.9963 fails about 1 in 270 | IBM · Apache-2.0 | 2024-02-28 |
| #21 | ibm | ibm_brisbane | 0.9963 fails about 1 in 270 | IBM · Apache-2.0 | 2025-02-26 |
| #22 | ibm | ibm_hanoi | 0.9962 fails about 1 in 260 | IBM · Apache-2.0 | 2025-02-26 |
| #23 | ibm | ibm_auckland | 0.996 fails about 1 in 250 | IBM · Apache-2.0 | 2022-08-06 |
| #24 | ibm | ibm_kawasaki | 0.9959 fails about 1 in 240 | IBM · Apache-2.0 | 2025-02-26 |
| #25 | ibm | ibm_algiers | 0.9955 fails about 1 in 220 | IBM · Apache-2.0 | 2024-02-28 |
| #26 | ibm | ibmq_mumbai | 0.9953 fails about 1 in 210 | IBM · Apache-2.0 | 2021-03-13 |
| #27 | ibm | ibm_cairo | 0.9953 fails about 1 in 210 | IBM · Apache-2.0 | 2024-04-10 |
| #28 | ibm | ibm_perth | 0.9952 fails about 1 in 210 | IBM · Apache-2.0 | 2024-05-27 |
| #29 | ibm | ibmq_kolkata | 0.995 fails about 1 in 200 | IBM · Apache-2.0 | 2021-12-09 |
| #30 | ibm | ibmq_santiago | 0.9948 fails about 1 in 190 | IBM · Apache-2.0 | 2021-03-15 |
| #31 | ibm | ibm_washington | 0.9948 fails about 1 in 190 | IBM · Apache-2.0 | 2022-04-12 |
| #32 | ibm | ibmq_ourense | 0.9945 fails about 1 in 180 | IBM · Apache-2.0 | 2021-01-20 |
| #33 | ibm | ibm_cusco | 0.9945 fails about 1 in 180 | IBM · Apache-2.0 | 2025-02-26 |
| #34 | ibm | ibmq_sydney | 0.9944 fails about 1 in 180 | IBM · Apache-2.0 | 2021-03-15 |
| #35 | ibm | ibmq_montreal | 0.9944 fails about 1 in 180 | IBM · Apache-2.0 | 2021-03-15 |
| #36 | ibm | ibmq_manila | 0.9943 fails about 1 in 180 | IBM · Apache-2.0 | 2024-05-27 |
| #37 | ibm | ibmq_toronto | 0.9943 fails about 1 in 180 | IBM · Apache-2.0 | 2021-03-15 |
| #38 | ibm | ibmq_lima | 0.994 fails about 1 in 170 | IBM · Apache-2.0 | 2021-03-15 |
| #39 | ibm | ibmq_jakarta | 0.9939 fails about 1 in 160 | IBM · Apache-2.0 | 2024-05-27 |
| #40 | ibm | ibmq_boeblingen | 0.9939 fails about 1 in 160 | IBM · Apache-2.0 | 2021-02-04 |
| #41 | ibm | ibmq_brooklyn | 0.9936 fails about 1 in 160 | IBM · Apache-2.0 | 2021-07-26 |
| #42 | ibm | ibmq_vigo | 0.9934 fails about 1 in 150 | IBM · Apache-2.0 | 2021-01-20 |
| #43 | ibm | ibmq_rome | 0.9934 fails about 1 in 150 | IBM · Apache-2.0 | 2021-03-15 |
| #44 | ibm | ibm_oslo | 0.9933 fails about 1 in 150 | IBM · Apache-2.0 | 2022-07-17 |
| #45 | ibm | ibmq_guadalupe | 0.9932 fails about 1 in 150 | IBM · Apache-2.0 | 2021-04-20 |
| #46 | ibm | ibm_nairobi | 0.9932 fails about 1 in 150 | IBM · Apache-2.0 | 2024-05-27 |
| #47 | ibm | ibmq_valencia | 0.9927 fails about 1 in 140 | IBM · Apache-2.0 | 2021-01-20 |
| #48 | ibm | ibmq_manhattan | 0.9925 fails about 1 in 130 | IBM · Apache-2.0 | 2021-03-15 |
| #49 | ibm | ibmq_casablanca | 0.9925 fails about 1 in 130 | IBM · Apache-2.0 | 2021-03-15 |
| #50 | ibm | ibmq_paris | 0.9924 fails about 1 in 130 | IBM · Apache-2.0 | 2021-03-15 |
| #51 | ibm | ibmq_singapore | 0.9923 fails about 1 in 130 | IBM · Apache-2.0 | 2020-08-07 |
| #52 | ibm | ibmq_athens | 0.992 fails about 1 in 130 | IBM · Apache-2.0 | 2021-03-15 |
| #53 | ibm | ibm_lagos | 0.9917 fails about 1 in 120 | IBM · Apache-2.0 | 2024-05-27 |
| #54 | ibm | ibmq_london | 0.9916 fails about 1 in 120 | IBM · Apache-2.0 | 2020-08-10 |
| #55 | ibm | ibmq_bogota | 0.9914 fails about 1 in 120 | IBM · Apache-2.0 | 2021-03-15 |
| #56 | ibm | ibmq_burlington | 0.9909 fails about 1 in 110 | IBM · Apache-2.0 | 2020-06-11 |
| #57 | ibm | ibmq_belem | 0.9893 fails about 1 in 94 | IBM · Apache-2.0 | 2021-03-15 |
| #58 | ibm | ibmq_almaden | 0.9889 fails about 1 in 90 | IBM · Apache-2.0 | 2020-08-10 |
| #59 | ibm | ibmq_essex | 0.9889 fails about 1 in 90 | IBM · Apache-2.0 | 2020-08-10 |
| #60 | ibm | ibmq_poughkeepsie | 0.9878 fails about 1 in 82 | IBM · Apache-2.0 | 2020-02-29 |
| #61 | ibm | ibmq_quito | 0.9867 fails about 1 in 75 | IBM · Apache-2.0 | 2021-03-15 |
| #62 | ibm | ibmq_johannesburg | 0.9865 fails about 1 in 74 | IBM · Apache-2.0 | 2020-08-09 |
| #63 | ibm | ibmq_cambridge | 0.9861 fails about 1 in 72 | IBM · Apache-2.0 | 2020-07-16 |
| #64 | ibm | ibmq_16_melbourne | 0.9853 fails about 1 in 68 | IBM · Apache-2.0 | 2021-03-15 |
| #65 | ibm | ibmqx2 | 0.9841 fails about 1 in 63 | IBM · Apache-2.0 | 2021-03-15 |
| #66 | ibm | ibmq_20_tokyo | 0.9835 fails about 1 in 61 | IBM · Apache-2.0 | 2019-08-29 |
| #67 | ibm | ibmq_rochester | 0.9809 fails about 1 in 52 | IBM · Apache-2.0 | 2020-07-16 |
| #68 | ibm | ibmqx4 | 0.9762 fails about 1 in 42 | IBM · Apache-2.0 | 2019-08-23 |
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.