Why did my HRV baseline suddenly change?

This is a different question from why a single recovery score reads low on a given day. That guide is about a score moving against a stable baseline. This one is about the baseline itself moving — your new "normal" being a genuinely different number than it was a month ago, with every day since then scoring against that new number.

Every platform's "baseline" is a different rolling window

The first thing worth knowing is that "baseline" isn't one standardized thing across devices — each platform picks its own window, and the window size determines how fast (or slowly) it reacts to a real change in your life.

None of these are "wrong" — a longer window (Oura) is more resistant to noise but slower to reflect a genuine change; a shorter window (Garmin's 7-day comparison) reacts faster but can look "broken" during a temporary blip that a longer window would have smoothed over. If you've switched platforms recently, part of what feels like "my baseline changed" is really "I'm now looking through a different window at the same underlying trend."

The six real reasons a baseline actually moves

Work through these roughly in the order they're worth checking — the first two explain the majority of "sudden" baseline changes people notice.

1. You switched wearables, wear position, or wrist. This is the single most common cause and the easiest to miss. Apple Watch calculates HRV as SDNN; WHOOP, Oura, Fitbit, and most other wearables calculate it as RMSSD — different formulas applied to the same underlying heartbeat data, producing numbers that were never designed to be compared directly. A device switch alone, with zero physiological change, can move your number meaningfully. Moving a watch from your dominant to non-dominant wrist, or switching from a ring to a wrist band, changes sensor placement and can shift baseline too.
2. You're on the other side of an illness. HRV commonly stays suppressed for roughly two to three weeks around a cold, flu, or similar illness. Once you're actually recovered, your true HRV typically climbs back toward its old range — but the platform's own rolling average takes a similar few weeks to catch up, so there's a lag where you feel fine while the baseline is still settling.
3. Your training load has genuinely shifted for weeks, not days. A baseline partly reflects your current conditioning and training stress, not just an abstract "you." An extended hard training block, a long taper, a deload period, or stopping training altogether for a few weeks can move your normal range in either direction — this is the range doing its job, not malfunctioning.
4. You've had a meaningful change in body weight. Research on people carrying excess weight finds that moderate weight loss — roughly 5-10% of body weight — is associated with a real improvement in parasympathetic (vagal) tone, which shows up as higher HRV. If you've lost or gained a substantial amount of weight over recent months, expect the baseline itself to have moved along with it.
5. You're tracking across menstrual cycle phases without accounting for them. HRV tends to shift across the cycle's phases in a repeating pattern rather than settling on one number — if you're not aware of where you are in the cycle, that wave can look like "my baseline randomly changed" when it's actually a monthly rhythm.
6. Slow, ordinary aging drift. HRV tends to decline gradually across years for most people — this shows up as a baseline creeping down over a long timescale, not something that happens between one week and the next. If your change matches this description (very slow, very gradual, over a year or more), it's the least concerning item on this list.

A change in prescription medication that affects heart rate or the autonomic nervous system can also shift a baseline; if you've recently started or stopped one, that's worth mentioning to whoever prescribed it rather than troubleshooting through a wearable app.

A protocol for telling a real shift from noise

1. Name a cause from the list above in the last 4-6 weeks. Most "sudden" baseline changes have an identifiable trigger once you actually check the calendar — a device switch, being sick, a training block, a scale change, or a cycle transition.
2. Look at the 30-day trend, not the daily view. A genuine baseline shift shows up as a sustained new plateau across weeks — a single dip or spike, even a dramatic one, is noise the baseline is specifically designed to absorb.
3. Don't compare across a device switch. If you changed wearables, treat the switch date as a fresh starting line rather than judging the new device against the old one's number — see the HRV glossary entry for why the two aren't measuring quite the same thing.
4. Give it the platform's own recalibration window before trusting the new range. That's roughly 3-6 weeks depending on the device (see the table above) — a baseline that's still "adjusting" for the first few weeks after a real change isn't a bug, it's the rolling average doing exactly what it's designed to do.
5. If none of the above explains it, treat it like an unexplained pattern. A baseline shift with no identifiable cause, especially one paired with a persistently elevated resting heart rate or new symptoms, is worth a doctor's visit rather than something to wait out.

When it's worth a doctor visit, not just patience

Most baseline shifts trace back to one of the six causes above and settle within the platform's own recalibration window. Treat it differently if you notice:

• A sustained drop in your baseline with no identifiable cause from the list above, lasting a month or more
• A baseline shift accompanied by a resting heart rate that stays elevated for a week or longer
• New symptoms alongside the shift — unusual fatigue, breathlessness, chest discomfort, or fever
• A baseline that never returns toward your old range even long after you feel fully recovered from whatever explained the initial dip

A wearable's baseline is a trend signal, not a diagnosis — genuinely useful for noticing that something changed, but not for explaining what.

Why this matters more once you're tracking across sources

The single biggest hidden cause of a "changed" baseline is switching which device is feeding it — and that's exactly the trap that opens up once you own more than one wearable. This is part of why Vita's cross-source merge deliberately picks one source per metric across a given window rather than splicing WHOOP nights and Apple Health nights into the same rolling average: mixing RMSSD readings from one device with SDNN readings from another wouldn't produce a baseline that measures anything consistent, even though both would display as "HRV." If you're evaluating whether your own baseline shift is real or just an artifact of switching sources, Vita's recovery score is built to keep that comparison honest rather than quietly blending two different measurements into one number.