Quick Answer: A long run that collapses in the final two miles is almost always a pacing or fueling problem, not a fitness ceiling. The most common cause by a wide margin is starting 20-30 seconds per mile too fast — which feels like nothing at mile one and costs you everything at mile nine. Fix the first two miles before you change anything else.

Every week the same shape. Comfortable through eight, then the wheels come off and you shuffle home.

It reads like an endurance limit. Seven times out of ten, it’s something you did in the first fifteen minutes.

1. You started too fast — and it felt easy

This is the big one, and the reason it hides so well is that going out fast doesn’t feel fast when you’re rested. Fresh legs make 8:40 feel like 9:10.

The cost is deferred. Running 20-30 seconds per mile too quick for the first three miles drains glycogen faster and accumulates fatigue you don’t perceive until it arrives all at once.

Fix: deliberately run the first two miles slower than feels right — you should be mildly annoyed by how easy it is. Aim to run the second half of the run at the same pace or slightly faster than the first. A negative split on a long run is the single clearest sign you paced it correctly.

If you only change one thing on this list, change this one.

2. You’re under-fueled for the distance

Under roughly 75 minutes, stored glycogen carries you fine. Past that, the tank starts running low, and the point where it empties is remarkably consistent — right around 90-120 minutes for most people. If your long run is two hours, the last two miles are exactly where you’d expect to hit it.

Fix: take in 30-60g of carbohydrate per hour on any run over 75 minutes, starting at about the 45-minute mark. Not at mile eight when you already feel bad — by then you’re 20 minutes behind, since it takes that long to reach the muscle.

Gels, chews, sports drink, dried fruit, whatever your stomach tolerates. Practice it on training runs; race day is not the time to find out.

3. You’re dehydrated from the day before, not the run

Runners obsess over drinking during the run and ignore the 20 hours preceding it. Starting a long run already down on fluid means your blood volume is lower, your heart rate runs higher for the same effort, and cooling is less efficient. All three compound over time — which is why it shows up late, not early.

Fix: the day before a long run, drink consistently and add a little sodium with meals. Check your morning urine color — pale straw is the target. In late-summer humidity, add 300-500mg of sodium per hour during the run, since plain water alone can leave you low on electrolytes.

This one is invisible until you fix it, and then it’s obvious.

4. Your long run is disproportionate to your week

A long run should be roughly 25-30% of weekly mileage. If you run 20 miles a week and 12 of them are the long run, that run is 60% of your volume — the last two miles aren’t failing, they’re beyond what your week has prepared you for.

Fix: build the midweek runs before extending the long one. Two extra easy miles on Tuesday and Thursday will do more for the back end of Saturday’s run than adding another mile to Saturday.

This is the most common structural error in self-made training plans, and it’s slow to fix — give it four to six weeks.

5. Your form degrades and nobody told you

Fatigue quietly changes mechanics: cadence drops, stride lengthens, the foot lands further ahead of the body, hips drop slightly. Each change makes running less efficient, so the same pace costs more, so fatigue accelerates. It’s a loop that tightens over the final miles.

Fix: at the point where it usually falls apart, run a 60-second form reset — shorten the stride, quicken the turnover slightly, relax the shoulders and unclench the hands. It feels like doing less. It’s usually faster.

Setting your watch to buzz at that mile marker works better than remembering.

6. You’re running the same route with the hills at the end

Worth checking before you diagnose anything physiological: look at your route’s elevation profile. A surprising number of loops save their climb for the return leg, because they head out downhill without anyone noticing.

Fix: run the loop backwards for a few weeks. If the final two miles stop being a problem, you had a route problem, not a fitness problem.

It’s the cheapest thing on this list to test and it costs you nothing to rule out.

7. You’re doing them on tired legs from Thursday

If your hard session is Thursday and your long run is Saturday, you may simply not be recovered — particularly if Thursday involved heavy lifting or downhill running, both of which produce muscle damage that peaks 24-48 hours later.

Fix: put at least one genuinely easy day between your hardest session and your long run. If the schedule won’t allow it, move the hard session earlier in the week rather than shortening the long run.

Myth vs Fact: Myth — long runs should always feel hard at the end or they weren’t long enough. Fact — a well-executed long run should end at a controlled effort you could hold a bit longer. Ending in a death march isn’t proof of work; it’s proof of poor pacing, and it costs you recovery days you’d rather spend training.

This is general information, not medical advice. Sharp pain, dizziness, or unusual shortness of breath during a run means stop and check in with a healthcare professional.

TL;DR:

• Start slower than feels right — going out 20-30 sec/mile too fast is the cause more often than everything else combined.
• Fuel at 30-60g of carbs per hour past 75 minutes, starting at the 45-minute mark, not when you feel bad.
• Hydrate the day before, and add sodium in humid conditions.
• Keep the long run at 25-30% of weekly mileage; build midweek before extending it.
• Check your route’s elevation and your recovery from Thursday before blaming your endurance.

Work down the list in order. Most runners fix it at number one or number two, and spend the rest of the fall wondering why the last two miles ever felt like that.