About the Stability Score and Spike Detection

Overview: 

We recently released new Levels experience that makes it easier to achieve stable glucose each day: a Stability Ring to show your daily progress achieving stable glucose, and Spike Detection, to highlight the portions of your day that have the highest potential for improvement. This article provides an overview of these features.


About the Stability Score and Spike Detection

The stability ring and glucose state description are located on your Today tab, above your graph:

How does it work?
With the Stability Ring, you’ll earn stable hours for periods of time without glucose spikes exceeding 30 mg/dL from your baseline glucose. Levels will automatically detect when these spikes happen to make it clear which activities and periods of the day are holding back your stable hours. 
What is my baseline glucose?

Your baseline glucose is personalized to your data and is calculated based on the previous four hours of glucose readings. Levels will detect periods of stability, as well as glucose spikes that exceed +30 mg/dL from your baseline, and share whether your current glucose is stable, spiking, crashing, or recovering

What does each glucose state mean?
  • Spiking: Spikes that exceed +30 mg/dL from your baseline glucose.
  • Recovering: Crossing and staying below the spike threshold in the 1-hour window after crossing.
  • Crashing: When you're 10 points below start of spike baseline, within 30-minutes of crossing below spike threshold.
  • Stable: There's no spike end time in the last 1 hour and you are not currently spiking.
  • Missing Data: No data if there are three consecutive 15-minute intervals with no data.
How can I view my trends over time?
Within the My Data tab, you’ll see trends of your stable hours and spike counts in My Data, and earn streaks for days without glucose spikes exceeding +30 mg/dL

If you have any questions or feedback, please email support@levelshealth.com.

Did this article answer your question? Thanks for the feedback! There was a problem submitting your feedback. Please try again later.