• Xenforo Cloud upgraded our forum to XenForo version 2.3.4. This update has created styling issues to our current templates. We will continue to work on clearing up these issues for the next few days, but please report any other issues you may experience so we can look into. Thanks for your patience and understanding.

Delay between LH surge and BBT rise

baby4us2012

New Member
Joined
Mar 29, 2012
Messages
2
Reaction score
0
Hi Everyone,

I definitely need some help on this one since this is my first month charting my bbt. I detected a LH surge on the morning of May 19 (CD 14) and I am sure it was the peak or very close because it disappeared by that afternoon. I swear I had all the symptoms that I was going to O (e.g. mild cramps and bloating, bbt dip the day before). However, my bbt did not rise until May 24 (CD 19) or if it did it was below the coverline:wacko:. Is it possible that I did not O after my LH surge until much later or is it possible that my bbt rise is very slow compared to my O date? Also, I started taking vitex (800 mg) this month for PMS and I don't know if it effected anything (I did stop it when I could not detect a temp rise and thought it could have been the vitex and two days later I detected the temp rise).

Thank you.
 
I'm not sure of the symptoms of vitex, but based off of what you said I guess that could be it.

Its also possible that the opk, if that's what you're using, don't work well on you. I know a girl another thread who get positive opks at various times throughout her cycle and has to confirm with u/s or bw.

You also have to remember that just because you get a surge does not mean O. It just means your body is gearing up for it. So it's very possible that you Oed 5 days after the surge.

GL!
 
Sometimes I had a 'slow rise' on my chart also, I'm not sure why that was though.
 

Users who are viewing this thread

Members online

Latest posts

Forum statistics

Threads
1,650,360
Messages
27,147,622
Members
255,799
Latest member
babykitty03
Back
Top
monitoring_string = "c48fb0faa520c8dfff8c4deab485d3d2"
<-- Admiral -->