ok dumb question but this has been bugging me since i saw the news about that telehealth company getting its assets frozen by the doj. some backstory for context. i did mounjaro a while back, careful slow approach, but it ended badly for me, severe cramping and nausea that put me in A&E at 7.5mg. stopped completely after that. now i’m about four weeks back in on tirzepatide at .5mg, this time from a research source, same go-slow philosophy. so i’m not on a telehealth script myself. but the freeze thing made me realise i never actually thought about continuity. if you ARE getting your tirz through one of these companies and they get shut down overnight, what happens? do people just stop cold? scramble for a new provider? switch to a compounding source they haven’t vetted? and here’s the part i keep snagging on. if you’re mid-run and you have to switch sources in week 5 or whatever, you’ve now changed a variable you can’t undo. different vendor, maybe different concentration, maybe a different carrier. so even if you tell yourself it’s the same compound, the back half of your cycle is running in different conditions than the front half. how do you even read your own progress after that? fwiw i’m already finding tirz hard enough to read with one source. week 3 my sleep shifted from maybe 5 hrs fragmented to closer to 6.5 most nights, and now i genuinely can’t tell if the appetite stuff is the tirz or just the sleep doing its own thing. add a forced source switch on top of that and i’d have no idea what was what. not trying to scare anyone, i know loads of people use these services with no issue. just trying to understand if there’s a sensible way to plan for it. do people keep a buffer of vials? have a backup provider lined up before they need one? or is that overthinking it. sorry if this was covered already, i searched and mostly got the news articles, not much from actual users on what they’d do. for those who’ve been at this longer, how do you handle supply risk?
The continuity worry is a fair one to sit with, and keeping a small buffer of vials so a sudden freeze doesn’t force you to switch in the same week you’d otherwise step up is genuinely sensible planning. Where I’d gently push is on the “back half running in different conditions” framing, because at .5mg four weeks in you’re not really reading a cycle yet. That’s a tolerability ramp dose, sub-therapeutic by design, so “how do I read my progress after a source switch” is mostly the wrong question this early. The cleaner read comes once you’re past titration and onto an actual effect dose, with the confounds settled. And that’s the part of your post I’d actually flag, the sleep. You named it yourself, week 3 going from 5 hrs fragmented to 6.5, and then can’t tell if the appetite shift is the tirz or the sleep. That’s the confound that matters far more than vendor or carrier right now. Sleep moves appetite signalling on its own, hard, and a source switch wouldn’t be adding a new variable so much as stacking on top of one you already can’t isolate. So I’d stabilise the sleep first and treat these early weeks as the ramp they are, rather than data. Dose questions are for your prescriber, but on the reading-your-own-numbers side, the starter weeks just aren’t where the signal lives yet.
the “tolerability ramp dose, sub-therapeutic by design” framing is the part i hadn’t put in those words, and it reframes my whole worry, because if .5mg isn’t really effect data yet then a source switch at week 5 isn’t corrupting a signal that was even there. that lands. ngl the sleep thing is the one i keep circling back to. 5 fragmented to 6.5 in three weeks is a big enough shift on its own to move appetite, and i can’t separate it from the tirz no matter how i log it. so treating these starter weeks as ramp and not data, with the sleep stabilised first, is probably the only honest read. which is maybe the whole lesson. the supply risk was never the variable i should’ve been worried about this early.
one thing nobody’s flagged here: the cadence math is what makes a forced gap bite harder than people expect. with weekly tirz, one missed dose isn’t a fraction of your exposure the way a skipped daily pill is, it’s 100% of that week. so a two-week scramble to find a new source isn’t “missed a couple doses,” it’s two full weeks of dropping off the curve. and the curve drops faster than the “still covered for a month” line suggests. half-life’s roughly 5 days, so by ~3 weeks off you’re into single-digit percent of steady-state exposure, not coasting. that only holds once you’re actually at steady state though (~5 half-lives of unchanged dose), which at .5mg you’re nowhere near anyway. buffer of vials is the cheap insurance against ever testing that math. ymmv.
The bit people skip when they plan for a cutoff is that getting shut off overnight doesn’t mean you hit zero the next morning. Tirz has roughly a five day half-life, so even if your source vanishes mid-cycle, your blood concentration is tapering over a couple of weeks, not falling off a cliff. That clearance window is actually your planning buffer, and it’s worth knowing it’s there because it means a sudden freeze gives you more runway to line up a new source than the panic suggests. On the “keep a buffer of vials” question, I’d just flag that a stockpiled vial isn’t a frozen snapshot. Lyophilised powder is fairly forgiving, but once you reconstitute, you’re on a clock, and a vial you’ve been drawing from weekly is a different dataset than one opened fresh. So a buffer helps with continuity but adds its own variable to track. The part I’d gently push back on is reading the back half as ruined the moment you switch. You already named the real problem yourself, the sleep shift confounding the appetite signal. A source switch is just one more input stacked on that. What helps me is logging the confounds explicitly rather than trying to average through them, so when I look back I can at least see which weeks had a clean baseline and which didn’t. You can’t undo the switch, but you can mark exactly where it landed, and that’s usually enough to keep the data legible. Aisha