Resting order lifetime (and level flicker)
Updated
A price level in the order book is not a permanent thing. It appears when someone posts size there, and it clears when that size is cancelled or traded. How long levels tend to stand, and how often they blink in and out, says something measurable about how a book behaves. Almost no data feed reports it, and the search term for it is close to unclaimed, so this page defines it plainly.
What is resting order lifetime?
Resting order lifetime is how long a price level stands in the book before it clears. BlackForge reports the median lifetime of levels that both appeared and disappeared inside a five-minute window, in milliseconds, alongside a flicker count of levels that appeared, vanished, then reappeared. Together they measure whether the book was stable or repeatedly rebuilt.
How lifetime and flicker are measured
Both columns require tracking the birth and death of individual price levels across the whole update stream, not just sampling the book. Every time a level comes into existence and later clears, its lifetime is the time between those two events. BlackForge takes the median of those lifetimes over the window and reports it in milliseconds as levelLifetimeMedianTime.
The median counts only levels that both appeared and disappeared inside the window. A level that was already there when the window opened, or that is still there when it closes, has no complete lifetime to measure, so it is left out. That makes the statistic bounded and well defined rather than an estimate that leaks across window edges.
Level flicker is the companion count: levelFlickerCount is the number of levels that appeared, vanished, then reappeared within the same window. Where the median lifetime describes how long levels last, flicker describes how often the book rebuilt the same levels it had just cleared.
What it looks like in real data
Here are both columns for BTCUSDT on binance in the latest closed window: the median level lifetime in milliseconds, and the flicker count. The units differ, so they are shown as a labelled readout rather than a chart.
BTCUSDT on binance
- Median level lifetime
- 1,800ms
- Level flicker count
- 7,970
What it tells you, and what it does not
Together, lifetime and flicker measure the stability of the resting book. A book whose levels stand for a while and rarely reappear behaved differently, in a measurable way, from one whose levels cleared quickly and kept being rebuilt at the same prices. That is a structural description of the book over the window, and it is the kind of thing you cannot recover from a depth snapshot alone.
What these columns are not is a verdict. A short median lifetime or a high flicker count is a measurement of book behaviour, and calling it spoofing or manipulation reads an intent into it that the number does not contain. There are ordinary reasons a book churns quickly, including plain market-making. BlackForge reports the measured behaviour and stops there; the interpretation is not encoded in the column.
Related columns
levelLifetimeMedianTime and levelFlickerCount are in the bookMicro family, next to the liquidity added and removed columns that measure the same churn as a flow of value. All of them need a maintained live book and per-level tracking, and all are computed per pair per closed five-minute window across nine spot venues.
See the full metric reference, or browse the glossary.
What is resting order lifetime?
It is how long a price level stands in the order book before it clears, reported as a median over the window in milliseconds. BlackForge measures the time between a level appearing and disappearing for every level that completed its life inside the window, then takes the median. Levels that spanned a window edge are excluded so the statistic stays bounded and well defined.
What is level flicker?
Level flicker counts price levels that appeared, vanished, then reappeared within the same five-minute window. It is a companion to median lifetime: lifetime says how long levels last, flicker says how often the book rebuilt the same levels it had just cleared. A higher flicker count means more of that rebuild activity happened during the window.
Does a high flicker count mean spoofing?
No. Flicker is a measurement of how often levels were rebuilt after clearing, and reading manipulation into it adds a judgement the number does not carry. Fast, repeated posting and cancelling is normal market-maker behaviour on many venues. BlackForge publishes the count as a measurement of book behaviour, not as an accusation, and leaves the interpretation to you.
Who else measures resting order lifetime?
Across the vendors we surveyed, none ships median level lifetime or level flicker as a column, and the term itself is close to unclaimed in search. Both require per-level birth and death tracking across the full update stream, which is more than a depth snapshot provides. It is one of the behavioural columns BlackForge computes that a raw feed leaves you to build.