Skip to main content
Use CLIENT LIST to get one line of statistics for every client connection to the server. Each line holds space-separated field=value pairs with the connection’s id, name, address, age, idle time, protocol version, and last command, so the reply gives a snapshot of who is connected and what they are doing. It is the usual starting point for tracking down connection leaks and idle connections. The reply grows with the number of clients, so avoid calling it on a hot path, and parse it defensively because fields can be added over time.

Syntax

Arguments

This command takes no arguments.

Important points

  • This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.
  • This command can expose administrative information or make a broad destructive change. Restrict it to trusted code paths.

Response

The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.

Examples

TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.