Show databases
Enterprise Edition

The SHOW DATABASES command lists all databases in the DBMS, including their states and other relevant information.

For general information about the SHOW command, see the Cypher Manual → SHOW.

Syntax

Command Syntax

Command	Syntax
`SHOW DATABASE`	`SHOW { DATABASE[S] name \| DATABASE[S] \| DEFAULT DATABASE \| HOME DATABASE } [WHERE expression]` `SHOW { DATABASE[S] name \| DATABASE[S] \| DEFAULT DATABASE \| HOME DATABASE } YIELD { * \| field[, ...] } [ORDER BY field[, ...]] [SKIP n] [LIMIT n] [WHERE expression] [RETURN field[, ...] [ORDER BY field[, ...]] [SKIP n] [LIMIT n]]`

SHOW DATABASE

SHOW { DATABASE[S] name | DATABASE[S] | DEFAULT DATABASE | HOME DATABASE }
[WHERE expression]

SHOW { DATABASE[S] name | DATABASE[S] | DEFAULT DATABASE | HOME DATABASE }
YIELD { * | field[, ...] } [ORDER BY field[, ...]] [SKIP n] [LIMIT n]
[WHERE expression]
[RETURN field[, ...] [ORDER BY field[, ...]] [SKIP n] [LIMIT n]]

In Cypher 25 from 2026.05, it is possible to combine the SHOW DATABASES command with regular Cypher syntax. However, since SHOW DATABASES is run against the system database, all parts of the query must be allowed on the system database. For example, clauses like MATCH and SHOW INDEXES are not allowed on the system database; therefore, they cannot be used with SHOW DATABASES. However, procedure calls of system-allowed procedures are allowed. If the SHOW DATABASES is combined with other clauses, the automatic re-routing of the command to the system database is disabled, and explicit connection or routing is required.

`SHOW DATABASES` output

Depending on what you want to see, you can show different sets of databases:

All databases.
A particular database.
The DBMS default database.
The home database.

These commands return the following columns:

Table 1. Listing databases output
Column	Description	Type
`name`	The name of the database.	`STRING`
`type`	The type of the database: `system`, `standard`, `graph shard`, `property shard`, or `composite`.	`STRING`
`aliases`	The names of any aliases the database may have.	`LIST<STRING>`
`access`	The database access mode, either `read-write` or `read-only`. A database may be described as `read-only` when using `ALTER DATABASE … SET ACCESS READ ONLY`.	`STRING`
`databaseID`	The database unique ID. Only available for `online` or `deallocating` databases. For other database states the value will be `NULL`.	`STRING`
`serverID`	The server ID.	`STRING`
`address`	Server address in a clustered DBMS. The default for a standalone server is neo4j://localhost:7687.	`STRING`
`role`	The current role of the database (`primary`, `secondary`, `property shard replica`, `unknown`). Not applicable to composite databases (the value is `NULL`).	`STRING`
`writer`	`true` for the copy of the database that accepts writes for this database (this copy is the leader for this database in a cluster or this is a standalone server).	`BOOLEAN`
`requestedStatus`	The expected status of the database. Valid values are `online` or `offline`.	`STRING`
`currentStatus`	The actual status of the database. Possible statuses are: `online` `offline` `starting` `stopping` `store copying` `initial` `deallocating` `dirty` `quarantined` `unknown` `mixed` See Database states for more information.	`STRING`
`statusMessage`	A message explaining the status of the database, often explaining why it is not in the correct state.	`STRING`
`default`	`true` if this is the default database for the DBMS. Not returned by `SHOW HOME DATABASE` or `SHOW DEFAULT DATABASE`.	`BOOLEAN`
`home`	`true` if this is the home database for the current user. Not returned by `SHOW HOME DATABASE` or `SHOW DEFAULT DATABASE`.	`BOOLEAN`
`currentPrimariesCount`	Number of primaries for this database reported as running currently. It is the same as the number of rows where `role=primary` and `name=this database`. Not applicable to composite databases^[1], virtual sharded databases, and property shards (the value is `NULL`).	`INTEGER`
`currentSecondariesCount`	Number of secondaries for this database reported as running currently. It is the same as the number of rows where `role=secondary` and `name=this database`. Not applicable to composite databases^[1], virtual sharded databases, and property shards (the value is `NULL`).	`INTEGER`
`currentPropertyShardReplicas`	Introduced in 2025.12Enterprise edition Number of property shard replicas for this database reported as running currently. It is the same as the number of rows where `role=property shard replica` and `name=this database`.	`INTEGER`
`requestedPrimariesCount`	The requested number of primaries for this database. May be lower than current if the DBMS is currently reducing the number of copies of the database, or higher if it is currently increasing the number of copies. Not applicable to composite databases^[1], virtual sharded databases, and property shards (the value is `NULL`).]	`INTEGER`
`requestedSecondariesCount`	The requested number of secondaries for this database. May be lower than current if the DBMS is currently reducing the number of copies of the database, or higher if it is currently increasing the number of copies. Not applicable to composite databases^[1], virtual sharded databases, and property shards (the value is `NULL`).]	`INTEGER`
`requestedPropertyShardReplicas`	Introduced in 2025.12Enterprise edition The requested number of property shard replicas for this database. May be lower than current if the DBMS is currently reducing the number of copies of the database, or higher if it is currently increasing the number of copies.	`INTEGER`
`creationTime`	The date and time at which the database was created.	`ZONED DATETIME`
`lastStartTime`	The date and time at which the database was last started.	`ZONED DATETIME`
`lastStopTime`	The date and time at which the database was last stopped.	`ZONED DATETIME`
`store`	Information about the storage engine and the store format. The value is a string formatted as `{storage engine}-{store format}-{major version}.{minor version}`. Only available for `online` or `deallocating` databases. For other database states the value will be `NULL`. Not applicable to composite databases^[1] and virtual sharded databases (the value is `NULL`).	`STRING`
`lastCommittedTxn§`	The ID of the last transaction received. Only available for `online` or `deallocating` databases. For other database states the value will be `NULL`. Not applicable to composite databases^[1] and virtual sharded databases (the value is `NULL`).	`INTEGER`
`replicationLag`	The number of transactions the current database is behind compared to the most up-to-date allocation of that database. The lag is expressed in negative integers. In standalone environments, the value is always `0`. Only available for `online` or `deallocating` databases. For other database states the value will be `NULL`. Not applicable to composite databases^[1] and property sharded databases (the value is `NULL`).	`INTEGER`
`shardTxnLag`	Introduced in 2025.12Enterprise edition The number of transactions the current shard is behind compared to the most up-to-date shard allocation of the sharded database. The lag is expressed in negative integers.	`INTEGER`
`constituents`	The names of any constituents the database may have. Applicable only for composite databases.	`LIST<STRING>`
`graphShards`	Introduced in 2025.12Enterprise edition The names of any graph shards the database may have. Applicable also for standard databases (non-sharded databases), which have a single graph shard with the same name as the database. Not applicable to composite databases.	`LIST<STRING>`
`propertyShards`	Introduced in 2025.12Enterprise edition The names of any property shards the database may have.	`LIST<STRING>`
`defaultLanguage`	Introduced in Neo4j 2025.06 The default Cypher version for this database. Queries that are not prefixed with a Cypher version will be executed with the Cypher version of the database.	`STRING`
`options`	The map of options applied to the database. Not applicable to composite databases (the value is `NULL`).	`MAP`
1. The change for composite databases applies to versions 2025.04 and later and 5.26.5 and later.

The results of the SHOW DATABASES command are filtered according to the ACCESS privileges of the user. However, some privileges enable users to see additional databases regardless of their ACCESS privileges:

Users with CREATE/DROP/ALTER DATABASE or SET DATABASE ACCESS privileges can see all standard databases.
Users with CREATE/DROP/ALTER COMPOSITE DATABASE or COMPOSITE DATABASE MANAGEMENT privileges can see all composite databases.
Users with DATABASE MANAGEMENT privilege can see all databases.

The SET DATABASE DEFAULT LANGUAGE privilege is intentionally left out and does not affect the returned databases.

If a user has not been granted ACCESS privilege to any databases nor any of the above special cases, the command can still be executed but it will only return the system database, which is always visible.

Database states

A database’s currentStatus can be one of the following:

State Description

State	Description
`online`	The database is running.
`offline`	The database is not running. If the `statusMessage` column is filled, the database is not running because of a problem.
`starting`	The database is not running, but is about to.
`stopping`	The database is not running anymore, but still has not stopped completely. No offline operations (e.g. `load`/`dump`) can be performed yet.
`store copying`	The database is currently being updated from another instance of Neo4j.
`initial`	The database has not yet been created.
`deallocating`	Only applies to databases in a cluster. The database is still online but will eventually be offline due to a transfer of its role in the cluster to a different member. The status is `deallocting` until the transfer is complete, which can take anything from a second to a day or more.
`dirty`	This state implies an error has occurred. The database’s underlying store files may be invalid. For more information, consult the `statusMessage` column or the server’s logs.
`quarantined`	The database is effectively stopped and its state may not be changed until no longer quarantined. For more information, consult the `statusMessage` column or the server’s logs.
`unknown`	This instance of Neo4j does not know the state of this database.
`mixed`	If a database is a sharded database, this status indicates that not all shards have the same `currentStatus`. The `statusMessage` column shows how many shards have a certain status, e.g. online (4), starting(1)

online

The database is running.

offline

The database is not running. If the statusMessage column is filled, the database is not running because of a problem.

starting

The database is not running, but is about to.

stopping

The database is not running anymore, but still has not stopped completely. No offline operations (e.g. load/dump) can be performed yet.

store copying

The database is currently being updated from another instance of Neo4j.

initial

The database has not yet been created.

deallocating

Only applies to databases in a cluster. The database is still online but will eventually be offline due to a transfer of its role in the cluster to a different member. The status is deallocting until the transfer is complete, which can take anything from a second to a day or more.

dirty

This state implies an error has occurred. The database’s underlying store files may be invalid. For more information, consult the statusMessage column or the server’s logs.

quarantined

The database is effectively stopped and its state may not be changed until no longer quarantined. For more information, consult the statusMessage column or the server’s logs.

unknown

This instance of Neo4j does not know the state of this database.

mixed

If a database is a sharded database, this status indicates that not all shards have the same currentStatus. The statusMessage column shows how many shards have a certain status, e.g. online (4), starting(1)

Note that for failed databases, the currentStatus and requestedStatus are different. This often implies an error, but that is not always the case. For example, a database may take a while to transition from offline to online due to a performing recovery. Or, during normal operation, a database’s currentStatus may be transiently different from its requestedStatus due to a necessary automatic process, such as one Neo4j instance copying store files from another.

Show all available databases

A summary of all available databases can be displayed using the command SHOW DATABASES.

Query

SHOW DATABASES

Result

+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| name     | type       | aliases                      | access       | address          | role      | writer | requestedStatus | currentStatus | statusMessage | default | home  | constituents |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| "movies" | "standard" | ["films", "motion pictures"] | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | FALSE   | FALSE | []           |
| "neo4j"  | "standard" | []                           | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | TRUE    | TRUE  | []           |
| "system" | "system"   | []                           | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | FALSE   | FALSE | []           |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Databases hosted on servers that are offline are also returned by the SHOW DATABASES command. For such databases, the address column displays NULL, the currentStatus column displays unknown, and the statusMessage displays Server is unavailable.

Show detailed information for a particular database

In this example, the detailed information for a particular database can be displayed using the command SHOW DATABASE name YIELD *. When a YIELD clause is provided, the full set of columns is returned.

Query

SHOW DATABASE movies YIELD *

Result

+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| name     | type       | aliases                      | access       | databaseID                                                         | serverID                               | address          | role      | writer | requestedStatus | currentStatus | statusMessage | default | home  | currentPrimariesCount | currentSecondariesCount | requestedPrimariesCount | requestedSecondariesCount | creationTime             | lastStartTime            | lastStopTime | store                | lastCommittedTxn | replicationLag | constituents | defaultLanguage | options |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| "movies" | "standard" | ["films", "motion pictures"] | "read-write" | "C066801F54B44EA1520F0FE392B4005AABF42D8DD0A5FD09969B955575D287D5" | "e3063985-e2f4-4728-824b-a7d53779667a" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | FALSE   | FALSE | 1                     | 0                       | 1                       | 0                         | 2023-08-14T10:01:29.074Z | 2023-08-14T10:01:29.074Z | NULL         | "record-aligned-1.1" | 3                | 0              | []           | "CYPHER 5"      | {}      |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

In Cypher 25 from 2026.05, if the given database is a parameter that evaluates to null, the command no longer fails on the wrong type but instead returns nothing. This behavior aligns with not returning anything when the given database name does not exist.

Show the number of databases

The number of distinct databases can be seen using YIELD and a count() function in the RETURN clause.

Query

SHOW DATABASES YIELD name
RETURN count(DISTINCT name) AS count

Result

+-------+
| count |
+-------+
| 3     |
+-------+

By specifying the name column and sorting the results by distinct name, only the number of distinct databases are counted, not the number of allocations of databases in a clustered environment.

Show the default database

The default database can be seen using the command SHOW DEFAULT DATABASE.

Query

SHOW DEFAULT DATABASE

Result

+--------------------------------------------------------------------------------------------------------------------------------------------------------+
| name    | type       | aliases | access       | address          | role      | writer | requestedStatus | currentStatus | statusMessage | constituents |
+--------------------------------------------------------------------------------------------------------------------------------------------------------+
| "neo4j" | "standard" | []      | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | []           |
+--------------------------------------------------------------------------------------------------------------------------------------------------------+

Show the home database

The home database for the current user can be seen using the command SHOW HOME DATABASE.

Query

SHOW HOME DATABASE

Result

+--------------------------------------------------------------------------------------------------------------------------------------------------------+
| name    | type       | aliases | access       | address          | role      | writer | requestedStatus | currentStatus | statusMessage | constituents |
+--------------------------------------------------------------------------------------------------------------------------------------------------------+
| "neo4j" | "standard" | []      | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | []           |
+--------------------------------------------------------------------------------------------------------------------------------------------------------+

Filter the listed databases

It is also possible to filter and sort the results by using YIELD, ORDER BY, and WHERE.

Query

SHOW DATABASES YIELD name, currentStatus, requestedStatus
ORDER BY currentStatus
WHERE name CONTAINS 'o'

In this example:

The number of columns returned has been reduced with the YIELD clause.
The order of the returned columns has been changed.
The results are ordered by the currentStatus column using ORDER BY.
The results have been filtered to only show database names containing 'o'.

It is also possible to use SKIP and LIMIT to paginate the results.

Result

+--------------------------------------------+
| name     | currentStatus | requestedStatus |
+--------------------------------------------+
| "movies" | "online"      | "online"        |
| "neo4j"  | "online"      | "online"        |
+--------------------------------------------+

Show the default Cypher version of a database
Introduced in 2025.06

To view the default Cypher version of each database in the DBMS, run the command SHOW DATABASES with the YIELD clause and specify the defaultLanguage column. For example:

Query

SHOW DATABASES YIELD name, defaultLanguage

Table 2. Result
name	defaultLanguage
`"movies"`	`"CYPHER 5"`
`"neo4j"`	`"CYPHER 25"`
`"system"`	`"CYPHER 25"`
Rows: 3

Show quarantined databases and lift their quarantine
Cypher 25Introduced in 2026.05

The SHOW DATABASES command can be combined with procedure calls. To ensure the command is run against the system database, prepend it with the USE clause. Combining SHOW DATABASES with other Cypher clauses disables the automatic re-routing.

Query

USE system
SHOW DATABASES
YIELD name AS database, serverID AS server, currentStatus
WHERE currentStatus='quarantined'
CALL dbms.unquarantineDatabase(server, database)

Nothing is returned from the query, as it ends with a procedure call of a void procedure. To return the affected databases, add RETURN database, server at the end of the query. It is possible to specify the operation argument to the dbms.unquarantineDatabase() procedure.

For more information on the dbms.unquarantineDatabase() procedure, see Standard databases → Error handling. For more information on void procedures, see Call procedures → Note on VOID procedures.

Glossary

allocator: A component in the cluster that allocates databases to servers according to the topology constraints specified and an allocation strategy.
asynchronous replication: Asynchronous replication is used by secondary copies to poll for new transactions, which means they cannot be guaranteed to have received the most recent transactions. This enables efficient scale-out of read-performance.
Aura instance: A fully-managed DBMS represented by a single instance ID, that is running in the Neo4j Aura cloud.
auto-commit transaction: An automatically committed transaction that contains a single query.
Bolt protocol: Bolt is a protocol used for interaction between Neo4j instances and drivers.
bookmark: A marker the client can request from the cluster to ensure that it is able to read its own writes so that the application’s state is consistent and only databases that have a copy of the bookmark are permitted to respond.
category (Bloom): A category is based on a node label and is defined in a Perspective as a way of visually distinguishing nodes with the same label(s).
causal consistency: All servers in a cluster agree on the order in which transactions take place. The position of a server on the causal chain can be guaranteed using a bookmark.
cluster: A Neo4j DBMS that spans multiple servers working together to increase fault tolerance and/or read scalability. Databases on a cluster may be configured to replicate across servers in the cluster thus achieving read scalability or high availability.
client application: Software that interacts with a Neo4j server.
commit: A commit is the successful completion of a transaction, which ensures durability of any changes made. For more details, visit Operations Manual → Transaction management.
composite database: Composite databases are the means to access partitioned graph data with a single Cypher query.
constraint: Constraints are sets of data modeling rules that ensure the data is consistent and reliable.
Cypher®: Neo4j’s graph query language.
data model: A data model defines how information is organized in a database. A good data model will make querying and understanding your data easier. In Neo4j, the data models have a graph structure.
database: A database is a container used by the DBMS to manage and store graph data. The physical structure of data is controlled by the database.
database vs graph: Databases are the physical containers of graph data. Graphs are the logical structure of data in Neo4j.
Database Management System: Database Management System, or DBMS, capable of managing multiple databases. A DBMS may run on a single server, or span several servers configured as a cluster.
database schema: The prescribed property existence and datatypes for nodes and relationships.
deallocate: An act of removing a database from a server or a server from a cluster without loss of data or reduced fault tolerance.
degree (of a node): The number of relationships of a specific node; loops are counted twice.
disaster recovery: A manual intervention to restore availability of a cluster, or databases within a cluster.
driver: A software library that provides access to Neo4j from a particular programming language.
election: In the event that the Raft leader becomes unresponsive, followers automatically trigger an election and vote for a new leader.
entity: A node or a relationship.
expression (Cypher): A component of a Cypher query which produces values. It may be used in projections, as a predicate, or when setting properties on graph elements.
fabric: Fabric is the architectural design of a unified system that provides a single access point to local or distributed graph data.
fault tolerance: A guarantee that a cluster can maintain a database’s persistence and availability in the event of one or more servers failing.
follower: A primary copy of a database acting as a follower, receives and acknowledges synchronous writes from the leader.
Generative AI (GenAI): A type of artificial intelligence (AI) system that generates text, images, or other media in response to prompts.
graph: A logical representation of a set of nodes where some pairs are connected by relationships.
index: Data structure that improves read performance of a database.
knowledge graph: A specific type of graph that has an organizing principle so that a user (or a computer system) can reason about the underlying data. The organizing principle provides an additional layer of structure that adds context to support knowledge discovery.
label: Marks a node as a member of a named and indexed subset. A node may be assigned zero or more labels.
leader: A single primary copy of a database is designated as the leader. It receives all write transactions from clients and replicates writes synchronously to followers and asynchronously to secondary copies of the database.
main database: In terms of Neo4j Enterprise Studio, the database(s) containing the user’s data. Can exist in the same Neo4j deployment as the tool asset database.
motif: A description of a specific pattern within a graph.
node: A node represents an entity or discrete object in your graph data model. Nodes can be connected by relationships, hold data in properties, and are classified by labels.
operator: A symbol representing a mathematical or logical operation.
parameter: Named value provided when running a Cypher statement.
path: A sequence of nodes and the relationships connecting them, that does not contain duplicate relationships. Several paths can match a pattern.
pattern: A specific arrangement of nodes and relationships that can be matched in a graph. A pattern follows a motif.
perspective (Bloom): A Perspective defines a certain business view or domain that can be found in the target Neo4j graph. A single Neo4j graph can be viewed through different Perspectives, each tailored for a different business purpose.
primary: A copy of the database that is able to process write transactions and is eligible to be elected as a leader. It participates in fault tolerant writes as it is part of the majority required to acknowledge and commit write transactions.
primary vs secondary: In a cluster, databases can operate in either primary or secondary mode. Primary databases are able to process write and read transactions, ensuring fault tolerance. Secondary databases are replicated asynchronously from primaries, and their main purpose is to provide read scaling within the cluster.
project (Aura): An isolated environment in the unified Aura console that contains its own database instances, configurations, and resources. Preceded by tenant in the classic Aura console.
property: Properties are key-value pairs that are used for storing data on nodes and relationships.
query (Cypher): A statement that retrieves or writes information to a database.
Raft group: A group of servers that are participating in hosting a particular database in primary mode.
Raft group member: A server that is participating in a Raft group. A server can be a member of one or more groups.
Raft log: A shared log between all Raft group members that is guaranteed to be consistently updated and viewed by those members. The log contains both database data and operational state of the Raft group.
Raft protocol: The networking mechanism that enables a database to replicate its data across multiple servers to give high availability for accessing the data and high durability to the data stored.
read scaling: Distributing query load by creating additional database copies hosted in secondary mode (read-only).
relationship: A relationship represents a connection between nodes in your graph data model. Relationships connect a source node to a target node, hold data in properties, and are classified by type.
secondary: An asynchronously replicated copy of the database that provides read scaling within the cluster.
seed: A seed is a database dump or a full backup used to create a database on a cluster. This is sometimes called seeding.
server: A physical machine, a virtual machine, or a container running an instance of Neo4j. Servers can be standalone or part of a cluster.
session: A causally linked sequence of transactions.
session consistency: An alternative name for Neo4j’s causal consistency.
standalone: A single server running Neo4j and not part of a cluster.
synchronous replication: Synchronous replication requires the leader primary to replicate a transaction and block the commit until a quorum of the follower primaries acknowledges that the transaction is successfully replicated. Once the transaction is replicated, the commit is allowed to proceed. This ensures data durability and consistency within the cluster.
system database: A database used by Neo4j to store system information.
tenant (Aura): An isolated environment in the classic Aura console that contains its own database instances, configurations, and resources. Replaced by project in the unified Aura console.
tool asset database: In terms of Neo4j Enterprise Studio, the database where tools' assets are stored. This can be in the same Neo4j deployment as the main database(s) or in a separate deployment.
topology: A configuration that describes how the copies of a database should be spread across the servers in a cluster, see primary mode and secondary mode.
transaction: A transaction comprises a unit of work performed against a database. It is treated in a coherent and reliable way, independent of other transactions. Transactions comply with the ACID consistency model (atomic, consistent, isolated, and durable).

Show databasesEnterprise Edition

Syntax

SHOW DATABASES output

Database states

Show all available databases

Show detailed information for a particular database

Show the number of databases

Show the default database

Show the home database

Filter the listed databases

Show the default Cypher version of a databaseIntroduced in 2025.06

Show quarantined databases and lift their quarantineCypher 25Introduced in 2026.05

Glossary

Show databases
Enterprise Edition

`SHOW DATABASES` output

Show the default Cypher version of a database
Introduced in 2025.06

Show quarantined databases and lift their quarantine
Cypher 25Introduced in 2026.05