> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Instance Uptime, Redis

> Instance Uptime for Redis instances. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Executive Overview](/nerve-centre/connectors#connectors-by-type)

## At a glance

> **Instance Uptime** is how long the Redis process has been running since its last start, read from `INFO server` (`uptime_in_seconds`). A high, steadily climbing number is healthy. A sudden reset to near zero means the instance restarted, which on a cache often means a cold start and a temporary collapse in hit rate while the cache refills.

|                    |                                                                                                                                                                                                     |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it tracks** | `uptime_in_seconds` from `INFO server`, rendered in days, hours and minutes. The value counts up while the process lives and resets to zero on every restart or failover to a freshly started node. |
| **Data source**    | `INFO server`, `uptime_in_seconds` (and `uptime_in_days`).                                                                                                                                          |
| **Time window**    | `RT` (real-time, read on each refresh).                                                                                                                                                             |
| **Alert trigger**  | None by default. A reset is the signal to watch; pair with the hit-rate and memory cards to gauge cold-start impact.                                                                                |
| **Roles**          | owner, engineering, operations                                                                                                                                                                      |

## What it tracks

Uptime is the time elapsed since the Redis process started, not the time since the host booted. It resets on a planned restart, a crash, an out-of-memory kill, or a managed-service maintenance event. On a pure cache an unexpected reset matters because the keyspace is rebuilt from cold: [Keyspace Hit Rate %](/nerve-centre/kpi-cards/redis/keyspace-hit-rate) will sag while the cache warms, pushing more load onto the origin database behind it. On a persistence-backed instance the dataset reloads from RDB or AOF, so the keyspace returns quickly but there is still a brief unavailability window. Read uptime alongside [Last RDB Save (minutes ago)](/nerve-centre/kpi-cards/redis/last-rdb-save-minutes-ago) and [Connected Replicas](/nerve-centre/kpi-cards/redis/connected-replicas) so a restart can be tied to whether failover and recovery behaved as designed.

## Reconciling against the source

Run `redis-cli INFO server` and read `uptime_in_seconds` (or `uptime_in_days` for the rounded figure). On Amazon ElastiCache, correlate against the `EngineUptime` CloudWatch metric and the cluster events log. A reset in either source confirms a restart rather than a sampling gap.

***

### Tracked live in Vortex IQ Nerve Centre

*Instance Uptime* is one of hundreds of KPI pulses Vortex IQ tracks across Redis and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

[Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.