Zone 2 running is supposed to be comfortable. That’s the whole point of the zone. Comfortable, conversational, sustainable. You can run for hours at Zone 2. You feel fine at the end. Cardiac drift is minimal. You finish saying “I could do more.”
For the first 3 to 4 weeks of an aerobic base build, this is exactly what it feels like. Easy pace, easy effort, easy breathing, data shows everything clean and controlled.
Then something shifts. Around week 6 or 7, you notice the same pace is harder. By week 8 or 9, what was comfortable Zone 2 in May feels like threshold work in July. The watch still shows the same heart rate zone. The pace is the same. The perceived effort is no longer remotely the same.
This is Zone 2 drift. It’s real, it’s predictable, and none of the major training platforms flag it for you.
What’s Actually Happening
When you run Zone 2 pace at week 2 of a training block, your heart rate might settle at 135 bpm within the first 10 minutes and stay there. Heart rate variability during the run is stable. The effort feels trivial.
By week 8, the same pace run the same day of the week requires 142 bpm to sustain. Within 30 minutes, you’re seeing drift up toward 148. The run feels like a mild tempo rather than a base run.
Heart rate drift during long aerobic efforts is well known. Within a single session, heart rate tends to rise over time at constant pace due to dehydration, glycogen depletion, and central nervous system fatigue. That’s the classic cardiac drift discussed in most endurance training resources.
Zone 2 drift over training weeks is different. It’s a cumulative shift in how much work it takes to produce the same output at what the device believes is the same relative effort. Three contributors, in combination, drive it.
Contributor One: Accumulated Training Load
The most obvious factor is also the most ignored. Your baseline state is shifting as training accumulates.
Your cardiovascular system is the same. Your leg muscles are not. Eight weeks into a build, your quads, hamstrings, and calves are carrying accumulated fatigue from every session between week 1 and now. That fatigue has a metabolic cost. It raises the heart rate required to produce the same pace.
This isn’t overreaching. It’s the normal fatigue state of being deep in a training block. Your system is working with tired legs. Tired legs require more oxygen to move at the same pace. More oxygen requires a higher heart rate.
The wearable doesn’t know this. It sees 142 bpm and classifies it as Zone 2. The zone boundaries haven’t changed. The physiological cost of being in Zone 2 has.
Contributor Two: Stale Zone Boundaries
Training zones on most platforms are calculated once, then never updated. You do a lactate threshold test in January, your device sets your zones, and those zones remain the reference point for the next 10 months.
This is a problem for two reasons.
If your fitness has improved since the test. Your actual threshold has moved. What the device still calls Zone 2 might now be high Zone 1. Your Zone 2 pace is slower than it needs to be. You’re undertraining.
If you’re accumulating fatigue during a block. Your functional threshold drops during heavy training blocks, even as fitness is improving in the long run. What was true Zone 2 at week 2 is functionally Zone 3 by week 8. Your zones haven’t updated to reflect the current state of your system.
Neither of these is a fault of the sensor. It’s a fault of the model that the sensor feeds into. A static zone model can’t track a dynamic physiology.
Contributor Three: Heart Rate Threshold Drift
The specific threshold between aerobic and anaerobic metabolism is not fixed. It shifts with training, fatigue, hydration, environmental conditions, and sleep state.
A well rested athlete might transition from aerobic to partially anaerobic metabolism at 150 bpm. The same athlete after three consecutive hard training weeks might make that transition at 143 bpm.
Zone 2 is defined as below your first lactate threshold. If your threshold has dropped by 7 beats, the heart rate ceiling of Zone 2 has dropped with it. You need to be running at 138 bpm now to produce the same metabolic state you were producing at 145 bpm a month ago.
Nothing on your wrist is tracking this. The zones displayed on your watch are the zones that were set months ago. Your actual physiology is somewhere else.
How to Recognise Zone 2 Drift in Your Data
Here are the signals that distinguish Zone 2 drift from other problems.
Pace to heart rate decoupling on easy runs. Run the same route at the same perceived effort. If week 8’s heart rate is 7 to 12 beats higher than week 2’s at the same pace, and you can’t pin it to heat, hydration, or acute life stress, you’re looking at drift.
Rising perceived effort without rising pace. You feel like you’re working harder for the same output. This is a subjective indicator that’s often 1 to 2 weeks ahead of the objective data.
Declining heart rate recovery after easy efforts. The 60 second drop after you stop running has been getting smaller over the block. Healthy adaptation should either preserve or improve HR recovery. A declining trend during a build indicates accumulating load that is outpacing adaptation.
Mildly elevated morning resting heart rate. Over the course of a block, a 3 to 5 beat upward drift in morning RHR, combined with flat HRV, suggests accumulated load. Combined with Zone 2 drift, it confirms you’re deeper in fatigue than you realised.
What to Do About It
Three options, depending on what you’re training toward.
Option one: Recalibrate zones mid block. If you’re 8 weeks into a 16 week build and you notice significant Zone 2 drift, do a fresh threshold test. Not a maximum effort test, which carries its own recovery cost, but a 20 to 30 minute steady state time trial to recalibrate your zones to current state. Update your watch. Run your zones properly for the remainder of the block.
Option two: Deload and reset. If drift is significant and it coincides with other fatigue markers (suppressed HRV, elevated RHR, declining sleep quality), use it as the signal to insert an unplanned deload. One week of volume cut by 40 percent, no intensity, lots of sleep. Come back in and your Zone 2 should be closer to where it was at the start of the block. The drift should have cleared.
Option three: Stop caring about the number. This is the heretical one. Many experienced endurance athletes learn to ignore the zone numbers and train by effort. Easy runs are the ones where you can hold a conversation. You stop caring whether that conversation is at 138 or 148 bpm on any given day. The pace adjusts to the state. You don’t try to force your pre-fatigued pace through a fatigued system.
The Platform Gap
All of this is physiology 101 for experienced endurance coaches. None of it is reflected in consumer wearable zone models.
The reason is structural. Zone models require a calibrated threshold. Thresholds drift. Wearable platforms mostly don’t want to ask users to retest frequently, don’t trust the data that would be required to update zones automatically, and default to static zones that are correct for one narrow window of the athlete’s year.
The result is that every serious endurance athlete eventually learns to distrust their device’s zone boundaries and start training by feel. Which is fine. But it’s a learned skill that the platforms should be supporting, not making necessary through their own limitations.
The data exists to do this properly. Continuous heart rate data, pace data, subjective markers, cardiac drift patterns, training load. A proper analysis layer could flag Zone 2 drift within a week of it starting and recommend a specific action. No wearable currently does.
Green score. Destroyed legs. There are 6 blind spots in your wearable data. We wrote a free guide covering every one of them.
Green score. Destroyed legs. There are 6 blind spots in your wearable data. We wrote a free guide covering every one of them.
Download the Free Guide