Retired cloud QPUs
The following IBM® quantum processing units (QPUs) have been retired. For the full list of available QPUs, see the Compute resources page.
To retrieve jobs from a retired QPU, see these instructions.
Table of retired cloud QPUs
QPU name | Qubit count | Retirement date (Year - month - day) |
---|---|---|
ibm_sherbrooke | 127 | 2025-07-31 |
ibm_kyiv | 127 | 2025-04-18 |
ibm_nazca | 127 | 2024-12-04 |
ibm_kyoto | 127 | 2024-09-05 |
ibm_osaka | 127 | 2024-08-13 |
ibm_cusco | 127 | 2024-08-13 |
ibm_algiers | 27 | 2024-04-30 |
ibm_cairo | 27 | 2024-04-30 |
ibm_hanoi | 27 | 2024-04-30 |
ibmq_kolkata | 27 | 2024-04-01 |
ibmq_mumbai | 27 | 2024-04-01 |
ibm_ithaca | 65 | 2024-01-24 |
ibm_nairobi | 7 | 2023-11-28 |
ibm_lagos | 7 | 2023-11-28 |
ibm_perth | 7 | 2023-11-28 |
ibm_auckland | 27 | 2023-11-09 |
ibmq_guadalupe | 16 | 2023-10-27 |
ibmq_lima | 5 | 2023-09-26 |
ibmq_belem | 5 | 2023-09-26 |
ibmq_quito | 5 | 2023-09-26 |
ibmq_manila | 5 | 2023-09-26 |
ibmq_jakarta | 7 | 2023-09-26 |
ibm_seattle | 433 | 2023-09-07 |
ibm_washington | 127 | 2023-06-03 |
ibmq_oslo | 7 | 2023-05-04 |
ibmq_geneva | 27 | 2023-05-04 |
ibmq_montreal | 27 | 2023-04-11 |
ibmq_toronto | 27 | 2023-04-11 |
ibmq_armonk | 1 | 2022-07-07 |
ibmq_brooklyn | 65 | 2022-06-28 |
ibmq_bogota | 5 | 2022-06-17 |
ibmq_santiago | 5 | 2022-06-17 |
ibmq_casablanca | 7 | 2022-03-02 |
ibmq_sydney | 27 | 2022-01-11 |
ibmq_dublin | 27 | 2021-11-16 |
ibmq_manhattan | 65 | 2021-09-22 |
ibmq_5_yorktown | 5 | 2021-08-09 |
ibmq_16_melbourne | 15 | 2021-08-09 |
ibmq_paris | 27 | 2021-06-30 |
ibmq_rome | 5 | 2021-06-30 |
ibmq_athens | 5 | 2021-06-30 |
ibmq_berlin | 27 | 2020-12-31 |
ibmq_boeblingen | 20 | 2021-01-31 |
ibmq_ourense | 5 | 2021-01-15 |
ibmq_vigo | 5 | 2021-01-15 |
ibmq_valencia | 5 | 2021-01-15 |
ibmq_rochester | 53 | 2020-10-31 |
ibmq_cambridge | 28 | 2020-10-31 |
ibmq_almaden | 20 | 2020-08-31 |
ibmq_singapore | 20 | 2020-08-31 |
ibmq_johannesburg | 20 | 2020-08-31 |
ibmq_essex | 5 | 2020-08-31 |
ibmq_burlington | 5 | 2020-08-31 |
ibmq_london | 5 | 2020-08-31 |
Retired processor families
- Canary: The Canary family comprised small designs containing anywhere from 5 to 16 qubits.
- Falcon: The Falcon family of devices offered a valuable platform for medium-scale circuits, and also served as a valuable platform for demonstrating performance and scalability improvements before being pushed onto the larger devices.
- Egret: Egret brought the innovations of tunable couplers onto a 33-qubit platform, resulting in faster and higher-fidelity two-qubit gates.
- Hummingbird: Using a heavy-hexagonal qubit layout, the Hummingbird family allowed up to 65 qubits.
- Osprey: Osprey was nearly quadruple the size of Eagle at 433 qubits. The larger chip sizes required further enhancements to device packaging, as well as custom flex cabling in the cryostat to fit the greater I/O requirements within the same wiring footprint.
Retrieve a job from a retired QPU
Use the following code to retrieve a job from a retired QPU.
Passing in a Cloud Resource Name (CRN) in the following code is optional. When it is passed in, only backends and jobs from that instance are available. If an instance is not specified, all backends and jobs across all instances in your account are available. In this case, when a backend is specified, an instance that can access that backend is found and used.
from qiskit_ibm_runtime import QiskitRuntimeService
# Load your IBM Quantum account. Replace "<IBM Cloud CRN>" with your desired instance's CRN.
service = QiskitRuntimeService(channel="ibm_quantum_platform", instance="<IBM Cloud CRN>")
# Retrieve a single job by id
job = service.job(<job_id>)
# Retrieve a batch of jobs. Filtering options can be found in the QiskitRuntimeService.jobs api reference
jobs = service.jobs(backend_name=<backend_name>)
service.jobs()
returns jobs run from both qiskit-ibm-runtime
and the deprecated qiskit-ibm-provider
package. Jobs submitted by the older (also deprecated) qiskit-ibmq-provider
package are no longer available.