The core: blood first, tissue after
A CGM measures glucose not in the blood but in the fluid between the cells. Blood sugar changes first, the sensor glucose follows, the lag is, depending on the situation, roughly 2 to 20 minutes.1 As long as the value barely moves (rate of change under about 1 mg/dl per minute), blood and tissue are practically the same.2 Only when it goes fast does the gap become visible.3
You can see exactly this on my beer-garden evening
After the unexpected sugar surge (the detective work is here) my sensor showed 205 mg/dl at 19:42 with a steeply rising arrow. Later in the day, in hindsight, with a smoothed curve, the peak reaches about 190. Then the curve falls steeply, shoots below the target band to about 78 mg/dl, and afterwards settles around 100, where it stays calm for hours.
This is exactly the pattern that unsettles many: the sensor overshoots on a fast rise and undershoots on a fast fall, before it catches itself. That’s not a malfunction, it’s the physics of the tissue lag plus the smoothing algorithms in the device.
When the deviation is largest
Typical situations with fast changes, and therefore the largest deviation:1
- After eating, especially with fast carbs (my beer-garden evening)
- During and right after exercise
- After treating a hypo, the sensor still reads low although the blood is already rising
- After medications that move blood sugar fast
The other gap: the sensor change
On 13 July my notes simply say: “gap due to sensor change”. That’s the mundane but important kind of gap: between the old and new sensor there’s simply no data. On top of that, a fresh sensor is often not yet up to operating temperature in the first hours: the values can deviate more at the start.
How I handle it: mark the gap as a note. Otherwise weeks later I puzzle over why there’s nothing there, or worse: I interpret a gap as an event.
Key takeaways
- Trend beats single value. With a steep arrow the direction matters more than the exact number.
- Don’t react to the swing, but to the pattern. The undershoot to 78 was no cause for panic: the curve caught itself.
- If feeling and display conflict: finger-prick. If symptoms don’t match the sensor value or it’s implausible, use a fingertip measurement per the manufacturer.
- Note gaps so the later analysis stays honest.
- In calm phases the sensor is most accurate, that’s where absolute numbers are most worth looking at.
- CGM measures in tissue fluid, not blood: lag typically 2–20 minutes.
- With calm values, blood and tissue practically agree; with speed the gap opens.
The original measurement record remains unchanged. This section adds only method, sources, limitations and a reproducible follow-up plan.
The central question in this article
The article “When the sensor "lies": why the CGM reads too high, then too low” examines how data gaps, compression lows, physiological lag and real changes can be distinguished. The quality test is not whether one curve creates a compelling story. It is whether the timeline, data source, surrounding circumstances and alternative explanations are documented well enough for readers to separate observation from interpretation.

What the data show — and what they do not
A personal series can show timing and recurring patterns. It cannot by itself prove which physiological mechanism caused the pattern. Direct observation, plausible explanation and open question are therefore separated. Numbers remain linked to unit, time and data source, and missing details are not replaced with guesses.
Reading CGM correctly
Continuous glucose monitoring measures interstitial glucose. During rapid rises or falls, the display may follow blood glucose with a delay. Pressure on the sensor, a newly inserted sensor, hydration and short data gaps can add uncertainty. When a reading does not match symptoms or the situation, a confirmatory measurement may be appropriate depending on the clinical significance.
Technical context: CGM data and long-term patterns
A CGM measures glucose in interstitial fluid rather than directly in blood. During rapid change, sensor glucose and blood glucose may differ. Compression, newly inserted sensors, gaps and technical interruptions therefore need to remain visible. Long-term data are more credible when coverage and downtime are reported alongside averages. A month with only a few sensor days is not automatically comparable with a nearly complete month. Outliers should neither be removed without a rule nor presented dramatically without context.

Article-specific interpretation
For “When the sensor "lies": why the CGM reads too high, then too low”, this means first establishing which of the four phases — Check data coverage, Mark measurement quality, Calculate metrics, Add context and limits — are actually documented. A missing phase is not guessed from the curve. This matters especially because how data gaps, compression lows, physiological lag and real changes can be distinguished. More decimal places do not improve research; more complete context does.
Alternative explanations
The competing influences considered are Sensor age and change, Data gaps, Time of day and events, Aggregation and outliers. Several can act at once and partly mask one another. No factor is therefore declared causal merely because it occurred close in time. A plausible explanation remains labelled as plausible until a targeted comparison supports it.
Data sheet and provenance
The data sheet for “When the sensor "lies": why the CGM reads too high, then too low” records more than the start and peak. It also covers Check data coverage, Mark measurement quality, Calculate metrics and Add context and limits. Each section states whether a value was measured directly, read from a screenshot, calculated from raw data or reconstructed from memory. This keeps strong research separate from details that require later verification.
Typical failure modes
Common failure modes in this topic are incomplete portions, an incorrect time origin, events added retrospectively and observation ending too soon. For “When the sensor "lies": why the CGM reads too high, then too low”, Sensor age and change and Time of day and events are particularly important competing explanations. A finding is therefore given more weight only when the same direction appears on several sufficiently similar days and counterexamples are documented as well.
Editorial decision
The editorial decision is to keep the personal experience visible without turning it into universal advice. Headline, hero image, alternative text, captions and conclusion must communicate the same uncertainty. When the article contains an open question, it ends with the next testable step — Preserve raw data — rather than a claim of effect.
Interpretation matrix
The interpretation matrix for “When the sensor "lies": why the CGM reads too high, then too low” assigns every core statement to one of four classes: directly measured, calculated from several readings, physiologically plausible or still open. Direct measurement does not automatically establish causation. A calculated result requires a documented formula and time window. Plausible means consistent with physiology and timing but not isolated in the personal data. Open means that data, repetitions or comparison conditions are missing.
Publication review
Before publication, a final review asks whether the hero image matches the actual message of “When the sensor "lies": why the CGM reads too high, then too low”, whether every number can be found in the text, whether units and timing are correct, and whether every image has alternative text and a caption. It also checks that Sensor age and change or Data gaps has not accidentally been turned into a proven cause. Only then is the article editorially complete.

Reproducible follow-up plan
The next useful comparison follows four steps: Preserve raw data, Flag incomplete days, Use the same metrics, Export reproducibly. This sequence turns a spontaneous observation into a protocol and reduces the risk of selecting only spectacular days while forgetting ordinary patterns.
What can be transferred
The transferable lesson from “When the sensor "lies": why the CGM reads too high, then too low” is therefore not necessarily the exact number. What transfers are the question, the documented conditions and the handling of uncertainty. Other people may respond very differently because of treatment, fitness, insulin sensitivity, digestion or comorbidity.
Comparison rather than snapshot
A credible comparison starts with one clear question and conditions that are as similar as possible. Starting value, trend, time, portion, drinks, activity, sleep, stress and medication all belong in the record. Not every factor can be controlled; the important point is to show differences rather than explain them away afterwards.
State the observation window
Thirty minutes answers a different question from two, four or twelve hours. The article therefore states when observation begins and recognises that mixed meals, alcohol or intense activity can act later. A peak is not interpreted without the pattern before and after it.
Personal readings are not universal limits
Typical guideline targets can provide orientation but require individualisation. Age, comorbidities, pregnancy, medication, hypoglycaemia risk and personal treatment goals change the interpretation. The self-observations shown here do not replace diagnosis or treatment decisions.
Practical safety framework
Marked symptoms, recurrent hypoglycaemia, very high readings, ketones or a pattern that does not fit the situation require clinical assessment rather than another self-experiment. People using insulin or glucose-lowering medication must not derive dose changes or corrections from a blog post.
Further technical limitations
Metrics such as mean glucose, variability, time in an individually defined range and coverage answer different questions. They do not replace laboratory values or clinical assessment. In particular, remission cannot be established from a CGM chart alone. A reproducible analysis records export date, time zone, sensor version, filtering rules and calculation method. This is the only way to explain later why two analyses of similar raw data may differ.

Questions before drawing a conclusion
- Is the starting value for “When the sensor "lies": why the CGM reads too high, then too low” documented with trend and time?
- Are Sensor age and change and Data gaps described adequately?
- Did observation continue through “Add context and limits”?
- Is there a comparison day after “Preserve raw data”?
- Is each statement clearly labelled as personal, plausible or generally established?
Sources and context
- American Diabetes Association: Standards of Care in Diabetes—2026, glycaemic goals
- American Diabetes Association: Standards of Care in Diabetes—2026, diabetes technology
- NIDDK: Healthy Living with Diabetes
- Abbott: difference between interstitial and blood glucose
- American Diabetes Association: Standards of Care in Diabetes—2026, health behaviours and exercise
Medical notice: This article explains a personal observation and general context. It does not replace diagnosis, treatment adjustment or emergency care.
Article ID: SWF-P-004Please quote this ID for corrections or additions.
Sources
Sources as of: 21 Jul 2026.
- CGM tissue lag (~2–20 min) and largest deviation during fast changes. Reference. pmc.ncbi.nlm.nih.gov (opens in a new window)
- Blood and interstitial glucose agree at low rates of change (<~1 mg/dl/min). Reference. pmc.ncbi.nlm.nih.gov (opens in a new window)
- At rates of change of −1 to 3 mg/dl/min, MARD is about 9.4–11.4%; above 3 mg/dl/min it rises to 19.0% (flash glucose monitoring, meal test in type 2 diabetes). PMC. ncbi.nlm.nih.gov/PMC7199533 (opens in a new window)
