It is usually one of a few things
A marathon that comes apart in a full-distance race almost always traces back to one of these, and they leave different fingerprints in the data.
- You overbiked. The bike sat a little above what you could truly hold for that long, and the marathon started controlled then ground down as the legs emptied. Over 140.6 even a small overbike shows up here.
- You under-fuelled. The most common full-distance cause of all. You ran a calorie and carbohydrate deficit for hours, and it caught up as a wall — pace collapsing out of proportion to how the day felt earlier.
- Heat and dehydration. Heart rate drifts up across a long day while power and pace fall, and the drop is bigger than your fitness or your bike alone would explain.
- You went out too hard on the marathon itself. The first few kilometres are quick off the bike, then a long slow fade over the back half. This one is on the run, not the bike.
Overbiking versus under-fuelling: the one that actually matters
Over 140.6 these two account for most marathon collapses, they feel identical from the inside, and they are the pair most often confused. The separation is in when and how fast the decay arrives.
- An overbike decays gradually. The marathon holds near target for 10 to 15 km, then grinds down continuously. Look for bike fade over 10% or heart-rate-to-power drift over 16% — the full-distance thresholds, roughly double the 70.3 ones.
- A fuelling shortfall falls off a cliff. Pace is fine, then within a kilometre or two it is not, often at a repeatable point between 25 and 32 km. The bike file frequently looks clean, which is the tell: a good ride followed by a sudden collapse is a fuelling story, not a pacing one.
- Heat shows in the heart rate. Drift climbs across the whole day rather than appearing on the run, and the drop exceeds what either the bike or your fitness alone explains.
A full-distance day is long enough for two of these to be true at once, and when they are, a decay that starts early and then accelerates is usually both.
The fix diverges completely depending on which it was. More run volume will not save a marathon that failed because the bike was too hard; a smarter bike will not save a race you did not fuel; and a nutrition overhaul will not help if you rode 0.78 IF when your ceiling for that duration was 0.72.
Read it from the file
Upload your race file and The Debrief reads the bike and the marathon together and tells you which pattern your data actually shows. In plain language, the way a coach would walk you through it, and honest about what the file can and cannot prove. If the bike and the fuelling are tangled together it will say that too, rather than picking one to sound confident.
A full sample debrief on a real 9:12:22 file shows the bike and marathon read together.