Travelling with your ring: what happens to your data while you are away

Charge it before you go, because nothing will remind you

This is the one genuine gap, and it is worth stating plainly because it surprises people: *Vitra cannot show your ring's battery level, and it never will unless Oura changes something.* The ring reports its charge over Bluetooth to the phone app. That reading never reaches Oura's cloud, so their API has no field for it, and a desktop app has no Bluetooth link to the ring at all.

We built a battery indicator early on and removed it in v0.4.0 for exactly this reason — a number we could not actually obtain is worse than an honest absence. So: charge before the airport, and keep the charger with you rather than in the hold.

Days without the phone are deferred, not lost

Your ring records whether or not your phone is nearby. What it cannot do is reach the internet by itself. The chain is ring → phone app → Oura's cloud → the API → Vitra, and a break anywhere in it stalls everything downstream.

So a few days of the phone staying in a bag does not lose the nights. It means nothing shows up in Vitra until the phone syncs, at which point the backlog arrives at once. If you are somewhere with no signal for a week, open the Oura app when you next have connectivity and let it finish before you expect Vitra to know anything.

Gaps stay gaps

A day with no data is drawn as a day with no data. Vitra does not interpolate across it, does not average the neighbours into it, and does not quietly count it as a zero — a missing night is an absence of measurement, not a measurement of nothing.

The related property matters when the backlog does land: a later sync fills empty fields in without wiping what is already there. An incomplete day that arrives first and is completed later ends up complete, rather than each sync overwriting the last.

Your baseline goes on holiday too

This is the part people miss. Most of what a tracker tells you is relative to your own recent history — typically a rolling window of about thirty days. Spend a week sleeping badly in a hot hotel at altitude, and that week is now inside the window.

Two consequences. While away, your readings are compared against a baseline built at home, so everything looks worse than it is. Once home, your baseline has been dragged in the direction of the trip, so the first several days look better than they are. Neither is a malfunction and neither is news about your fitness; it is the window catching up.

What to actually do

Sync before you fly so the trip starts from a complete record. Open the phone app on arrival and again before you come home. Expect the first night in a new time zone to look bad and expect not to need a chart to tell you that. And treat the readiness score as uninformative for the duration — every input it uses is being pushed around by travel, so it mostly restates that you are travelling.

The useful readings are the ones that survive the noise: resting heart rate settling back down across successive nights, and sleep timing drifting back toward your usual hour. Those are the two that actually show you re-adapting.

Frequently asked questions