Overtraining Signs for Runners: RHR, HRV, Performance, and When to Rest

Your easy runs feel heavy. Resting heart rate crept from 48 to 54 over two weeks. Tuesday intervals that used to feel controlled now leave you gasping. Garmin says "Unproductive" for the fifth straight day. You sleep eight hours but wake exhausted. Are you overtrained, under-recovered, or just in a normal post-race slump?

True overtraining syndrome (OTS) is rare in recreational runners — it requires months of imbalance and often medical diagnosis. Functional overreaching — a short-term performance dip from accumulated load — is common and reversible in days to weeks. The problem is both get labeled "overtraining" on Reddit, and the wrong response (more miles to push through) worsens one while rest fixes the other.

This guide separates normal fatigue from warning signs, explains what resting heart rate (RHR) and heart rate variability (HRV) actually indicate, covers performance and subjective markers, and gives a decision framework for rest days, deload weeks, and when to seek help.

Overtraining vs. Overreaching vs. Normal Fatigue

Sports scientists distinguish three states on a continuum:

• Functional overreaching (FOR): planned or accidental short-term load excess; performance dips 5–14 days; recovers with rest and restores supercompensation
• Non-functional overreaching (NFOR): deeper performance suppression lasting weeks; mood, sleep, and autonomic markers worsen; requires structured deload
• Overtraining syndrome (OTS): months-long maladaptation with hormonal and immune dysfunction; medical evaluation warranted; recovery takes months

Most runners who worry they are "overtrained" are either normally tired from a hard week or in functional overreaching that a few easy days fixes. The skill is catching NFOR patterns before they deepen — using trends, not one bad workout.

Resting Heart Rate (RHR): The Simplest Trend Line

Resting heart rate measured consistently — ideally upon waking before standing — reflects autonomic nervous system balance. In trained runners, RHR often sits 40–60 bpm with individual baselines set by genetics, age, and fitness.

Acute elevation of 5–10 bpm above your four-week average for three or more consecutive mornings suggests incomplete recovery, oncoming illness, dehydration, or accumulated training stress. Context matters: one night of alcohol, a late meal, or bedroom heat also elevates RHR without overtraining.

How to use RHR practically:

• Establish a 14–28 day baseline during normal training
• Compare like to like — same measurement conditions (supine in bed vs. standing vs. watch overnight average are different instruments)
• Act on sustained elevation, not single spikes: swap intensity for easy running or rest when RHR stays 5+ bpm high for 3+ days alongside heavy legs
• Track return to baseline after rest — failure to normalize after 5–7 easy days suggests deeper overreaching

Garmin, COROS, and Apple Watch each measure overnight RHR differently. Our Resting Heart Rate and Recovery guide explains platform quirks. Consistency within one device beats comparing absolute numbers across brands.

Heart Rate Variability (HRV): What It Adds

HRV measures variation between consecutive heartbeats — higher variation generally reflects stronger parasympathetic (recovery) tone in rested endurance athletes. Morning HRV readings (Whoop, Oura, Garmin HRV Status, COROS, Apple Health via third-party apps) compare today against your rolling baseline.

Low HRV relative to baseline for multiple days correlates with accumulated stress — training, work, sleep debt, illness — not training alone. HRV is sensitive and noisy: alcohol crushes HRV for 24–48 hours; travel and late caffeine do the same.

Interpret HRV as a nudge, not a veto:

• Green / normal HRV + feel good: proceed with planned training
• Yellow / low HRV + feel fine: easy day or downgraded intensity; re-test tomorrow
• Red / low HRV + RHR elevated + heavy legs: rest or very easy movement; stack 2–3 recovery days
• Low HRV + feel awful: trust feel over green HRV — subjective markers matter

HRV does not replace pace and HR during runs. It informs whether today is a good day to spend glycogen on intervals or bank recovery credit with easy running in Zone 2.

Performance Markers That Signal Trouble

Physiological data is useless if performance trends ignore the obvious. Watch for these patterns over 7–14 days:

• Same HR, slower pace: cardiac drift inverted — easy pace at normal HR becomes impossible without HR spike (see heart rate drift and decoupling)
• Same pace, higher HR: economy loss on familiar routes at familiar effort
• Failed workouts repeatedly: missing rep paces that were achievable four weeks ago despite adequate rest between attempts
• Stale VO2 max estimates: Garmin or COROS trending down 2–3 points over a month without race or heat explanation — read our Garmin Training Status guide
• Race predictor divergence: recent race-equivalent efforts lag predictions from the Race Predictor when inputs were honest

One failed tempo is data. Three failed tempos in three weeks with rising RHR is a pattern. Compare against training log volume: did mileage jump more than 10–15% month over month? Was intensity stacked without a down week? Performance decline with load explanation is overreaching until proven otherwise.

Subjective Signs Runners Underestimate

Autonomic and performance markers lag behind how you feel. Subjective signs often appear first:

• Motivation collapse: dreading runs you usually enjoy — not one morning, but every morning for a week
• Mood irritability: disproportionate frustration at work, family, or training partners
• Sleep disruption: falling asleep exhausted but waking at 3 AM; unrefreshing sleep despite duration — see Sleep and Running Performance
• Persistent muscle soreness: legs never feel fresh; stairs hurt on rest days
• Appetite changes: loss of appetite or cravings for sugar and caffeine to compensate energy debt
• Elevated perceived effort: RPE 7 on runs that used to feel RPE 4 at the same pace
• Illness frequency: second cold in six weeks; cuts that won't heal — immune suppression from chronic overload

The RPE vs Heart Rate framework helps when metrics disagree with feel: if RPE says hard and HR says easy, trust RPE for load management decisions.

Load Mistakes That Produce Overreaching

Overtraining is usually under-recovery, not heroic volume alone. Common triggers:

• Too much Zone 3: every run moderately hard — no true easy, no true rest — the gray zone trap described in Zone 2 vs Zone 3
• Rapid mileage spikes: exceeding 10% weekly increase during base building
• Stacked intensity: intervals Tuesday, tempo Thursday, long run fast Sunday — insufficient easy volume between
• Life stress ignored: watch metrics treat work deadlines and newborn sleep like neutral background — they are not
• Returning too fast post-race: resuming quality within 5 days of marathon without recovery block
• Concurrent heavy lifting: strength training on legs before key run days without program adjustment

Polarized 80/20 training reduces overreaching risk by keeping easy days genuinely easy — validated with the Zone 2 Calculator and HR Zones Calculator.

Platform Recovery Scores: Garmin, COROS, Apple

Wearables synthesize RHR, HRV, sleep, and load into composite scores — Garmin Training Status and Body Battery, COROS Training Status and Recovery, Apple Training Load and readiness features. These aggregate complex inputs into green/yellow/red guidance.

Use them as secondary confirmation:

• Multiple days "Unproductive" or "Recovery": audit load and subjective feel; downgrade intensity
• Green score + body feels terrible: trust body; scores inherit bad overnight HR from one beer
• Declining training load tolerance: same weekly miles produce higher load scores — early overreaching signal

Do not let a green readiness score auto-authorize a workout your RHR trend vetoed. Composite scores smooth noise that individual markers reveal.

When to Rest, Deload, or Seek Help

One to three days: normal fatigue

Single bad workout, one elevated RHR morning, poor sleep night. Response: one rest day or 30–45 minute very easy jog. Resume plan if next session feels normal.

Three to seven days: functional overreaching

Multiple markers elevated — RHR up 5+ bpm sustained, HRV suppressed, easy pace feels hard, motivation low. Response: 3–5 days easy running only (true Zone 1–2) or complete rest; cut intensity entirely; prioritize sleep and nutrition from our Running Recovery Guide and Post-Run Recovery Nutrition article.

One to three weeks: non-functional overreaching

Performance decline persists despite easy days; RHR will not normalize; workouts fail repeatedly; mood and sleep worsen. Response: structured deload — 50–70% volume reduction for 7–14 days, zero intensity, reintroduce quality gradually. Consider training log review with a coach.

Months: possible overtraining syndrome

Extended performance suppression, amenorrhea, unexplained weight loss, depression, frequent illness, RHR elevated 10+ bpm for weeks. Response: medical evaluation — blood work (ferritin, thyroid, testosterone/cortisol ratio, vitamin D), rule out RED-S and clinical depression. Running pause may be required. This is beyond self-coaching.

A Practical Monitoring Checklist

Run this weekly audit — five minutes Sunday evening:

1. RHR trend: 7-day average vs. 28-day baseline — flag if +5 bpm or more
2. HRV trend: 7-day average vs. baseline — flag if suppressed 5+ consecutive days
3. Key workout result: did this week's tempo or long run match recent fitness?
4. Subjective score (1–10): energy, mood, leg freshness — flag if all three below 5 for 7 days
5. Load math: mileage and intensity vs. plan — accidental spike?
6. Sleep hours: average below 7 hours for two weeks amplifies all other flags

Two or more flags: insert an extra rest day and downgrade next intensity session. Three or more flags for two consecutive weeks: deload. Catching trends early converts a missed week into a avoided month.

What Recovery Actually Requires

Rest is not only absence of running. Recovery that reverses overreaching includes:

• Sleep extension: 8–9 hours; naps optional during heavy deload
• Caloric adequacy: deficit during deload deepens maladaptation
• Intensity ban: truly easy — HR below aerobic threshold; ego pace kills deloads
• Stress reduction: training load is one input; reduce optional life stress where possible
• Patience: fitness feels lost before it returns — performance rebounds often suddenly after 10–14 days proper rest

Returning to training: reintroduce intensity at 50% previous rep volume, one session first week, two second week if markers normalize. Race goals may need adjustment — see tapering guidance for how elites shed fatigue without losing fitness.

Final Takeaway

Overtraining in the clinical sense is rare; overreaching from stacked load and insufficient recovery is common and fixable. Resting heart rate and HRV trends — read over weeks, not mornings — provide early warning when paired with performance and subjective markers.

One bad day means nothing. A pattern of elevated RHR, suppressed HRV, failed workouts, poor sleep, and crushed motivation means rest — not another interval session to prove toughness. The runners who progress for decades are not the ones who never fatigue; they are the ones who recognize fatigue early and deload before it becomes a season.

→ Set heart rate zones · → Resting HR and recovery guide

FAQ

How much should resting heart rate rise before I worry about overtraining?

A sustained elevation of 5–7 bpm above your personal 28-day average for three or more consecutive mornings — especially combined with heavy legs, poor sleep, or failed workouts — warrants backing off intensity. Single-day spikes of 10 bpm happen from alcohol, illness onset, or dehydration without overtraining. Context and duration separate normal noise from actionable trends.

Can I still run easy miles if my HRV is low?

Often yes, if legs feel acceptable and RHR is not simultaneously elevated. Low HRV alone suggests downgrading intensity — swap intervals for easy running, shorten duration 20–30%. If low HRV pairs with elevated RHR, heavy legs, and low motivation, take a full rest day or cross-train lightly. Never run hard quality on multiple consecutive red HRV days unless a race demands it.

What is the difference between overtraining and being out of shape?

Out-of-shape fitness loss follows time off — pace slows, HR rises, but RHR may actually drop with detraining and motivation stays intact. Overreaching shows elevated RHR, suppressed HRV, persistent heaviness despite continued training, mood disruption, and failed sessions at paces recently achievable. Out-of-shape improves with gradual return; overreaching worsens if you push harder to "run through it."

How long does it take to recover from overreaching?

Functional overreaching typically resolves in 5–14 days with reduced volume and zero intensity. Non-functional overreaching may require 2–4 weeks of structured deload before performance normalizes. True overtraining syndrome can take months. Most recreational runners encountering warning signs need days to two weeks of easy running and rest — not a full season off — if they respond at the first pattern of multiple markers, not the tenth.