3 min czytania · Anonimowo
Nocny skok tętna
Kiedy Fitbit męża pokazał skok tętna o 3 w nocy podczas służbowego wyjazdu, wiedziałam, że to nie przez koszmar.
Pełna historia poniżej jest po angielsku.
I’ve always been data-driven. That’s why, when Liam and I decided to get healthier together, we bought matching Fitbits and linked our accounts on a shared dashboard. Every morning, we’d compare steps, sleep quality, and resting heart rates. It was playful competition, a way to stay connected even when one of us was traveling. Six years of marriage, two kids, and a renovated fixer-upper later, we were still that couple. Or so I thought.
When Liam left for a three-day business trip to Chicago, I didn’t think twice. He texted me the first night: “Exhausted. Going to sleep early. Love you.” I replied with a heart emoji and checked our dashboard before bed. His heart rate was already low, dipping into the sixties. Satisfied, I went to sleep.
The next morning, I woke up to a notification: “Great workout, Liam!” That was odd. He hadn’t mentioned exercising. I opened the app and saw a red spike on his heart rate graph. At 3:22 AM, his heart rate had jumped to 160 beats per minute and stayed elevated for nearly half an hour. I stared at the screen, my coffee growing cold. The numbers didn’t lie—but they didn’t make sense. He was supposed to be asleep in a hotel room, alone.
I called his room. No answer. Texted him: “Hope you slept well. Hey, your heart rate spiked last night—are you okay?” He replied an hour later: “Yeah, must have been a nightmare. Didn’t even wake me.” A nightmare? His heart rate pattern looked more like a sprint than a nightmare. I pulled up his GPS location from the hotel’s check-in—still at the hotel. But something gnawed at me.
Over the next two days, I watched the dashboard obsessively. Each night, the same pattern: a sudden spike between two and four in the morning, lasting twenty to thirty minutes. On the third day, I flew to Chicago unannounced. I told myself I was being paranoid. But I needed to see the room, the context.
I met him in the lobby. He looked surprised. “What are you doing here?” he asked, hugging me stiffly. I forced a smile. “I missed you. Surprise.” We went to his room. It was tidy, nothing suspicious. But then I saw a second phone charger plugged into the outlet beside the bed. “Who else was here?” I asked, my voice flat.
Liam turned pale. “What? No one. I had the charger for my work phone.” I picked up the cord—it was pink, not black. He stammered, “Maybe it was from a previous guest.” I opened the hotel app on my phone and checked the room’s history: he had checked in alone, but the housekeeping logs showed no pink charger left behind. The lies crumbled like ash.
“Show me your Fitbit data,” I said. He hesitated, then unlocked his phone. The raw data confirmed everything: heart rate spikes, movement, and then—I scrolled back further—a series of late-night calls to an unknown number. “Who is she?” I asked.
He didn’t deny it. “Her name is Rachel. She works in the Chicago office. It just… happened.” He said they’d been meeting on these trips for months. The Fitbit had been an oversight; he never thought I’d pay that close attention. I laughed bitterly. “We’re supposed to be motivating each other. You used our trust to cover an affair.”
I left that night. Back home, I packed his things and set them in the garage. The next day, I unlinked our Fitbits. The dashboard went gray, empty. For weeks, I couldn’t shake the image of that red line—jagged, relentless, a marker of betrayal written in biometrics. Our love had been quantified, and the number 160 told me everything I needed to know.
Months later, I still check my own heart rate during sleepless nights. It’s never that high. But sometimes I wonder if the truth, once revealed, leaves a permanent scar on the data of our lives—a spike that never fully returns to baseline.