Another one - AI FTP vs Ramp

Here we go again - but since other topics are already resolved, I don’t want to reopen them just to talk about my own N+1.

Since coming back to structured training, I’ve been doing a lot of base, a bit of build, and in the summer, a lot of base peppered with long, hard(ish) rides, that culminated with what I’d consider my A event last Sunday.
During that event, I smashed most of my PRs for the season.
Both Intervals.icu and Garmin suggested I increase my FTP (which stood at 222) to 227-230. Nothing major, but still good for a 4 week block.
I waited until it was (finally) time for my ai detection window and…. got suggested 218.
Considering the work I’ve put in, and the other metrics I have - this just seems off.
I know I shouldn’t put too much on a number, but I also want my training to be as efficient as possible.

So, I was debating doing a ramp, but before scheduling it, I read some topics here, and well, now I’m doubting myself.
So, TR Community, should I:

  • Keep my FTP at 222
  • Accept my fate, down to 218 you go
  • “the others” know better - get up to 227
  • go on, it’s been years since you tested, haven’t you missed that copper taste at the back of your throat?

PS: I know that it’s a tiny variation - but still, the direction of travel surprises me

If it was on the 24th August, it may have been a glitch?

1 Like

It was on the 24th, you’re right! I thought it was yesterday, but it was available and I hadn’t even asked it yet :smiley:

OK, now I feel stupid there has been a glitch, and I might have been affected. I’ll reply on the glitching thread so :person_facepalming:

We’ve gotten everything sorted out for you @holybinch! Sorry for the trouble!

3 Likes