> ## 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, MongoDB

> Instance Uptime for MongoDB deployments. 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 `mongod` process has been running continuously since it last started, for the selected period. It is the simplest health proof point in the Executive Overview: a long, steady uptime means the process has not crashed or been restarted, while a sudden reset to near zero means the member has just come back from a restart, a crash, or a failover, which is worth knowing about even when everything now looks healthy.

## What it tracks

The card reports the Instance Uptime for the selected period: the number of seconds (rendered as days, hours, and minutes) that this `mongod` has been up since its last start. The value comes straight from the `uptime` field of the `serverStatus` command, which the server resets to zero every time the process starts. Read it as a stability signal rather than an availability percentage: an uptime that climbs steadily day after day confirms the member is stable, whereas an uptime that has unexpectedly reset points at a restart you may not have planned. On a replica set, compare uptimes across members; if one member's uptime is much lower than its peers it has restarted recently, which often correlates with an election (see [Elections (24h)](/nerve-centre/kpi-cards/mongodb/elections-24h)) or a member that dropped out and rejoined. Note that uptime measures the process, not data availability: a replica set can serve traffic throughout a single member's restart because another member takes over as primary.

## Reconciling against the source

To check natively, run `db.serverStatus().uptime` in `mongosh` for the raw seconds, or `db.hostInfo()` and the `mongod` log start-up lines to confirm when the process last began. On MongoDB Atlas, the cluster's process restart history and the Metrics tab show the same restarts as uptime resets. Compare uptime per member across the replica set to spot a node that has restarted out of step with its peers.

***

### Tracked live in Vortex IQ Nerve Centre

*Instance Uptime* is one of hundreds of KPI pulses Vortex IQ tracks across MongoDB 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.