DOM MBO badge grey: “Aggregated L2 only (~10-20 levels)” and stale depth
On a Rithmic DOM, the MBO badge tells whether the full order-by-order book is active. When it is grey, the ladder is limited to the aggregated levels the feed publishes. A separate age indicator turns red after 3 seconds without a depth update.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- MBO off tooltip
- “Aggregated L2 only (~10-20 levels) — intermittent broker refusal”
- MBO on tooltip
- “MBO active — full order-by-order book”
- Stale tooltip
- “No depth update for a while — a dead feed looks like a quiet market”
- Stale threshold
- 3 seconds
What you see
The DOM header has an MBO badge. Grey, its tooltip reads “Aggregated L2 only (~10-20 levels) — intermittent broker refusal”; lit, “MBO active — full order-by-order book”. Next to it, the age of the last depth update turns red with “No depth update for a while — a dead feed looks like a quiet market”.
Why it happens
The badge separates a data ceiling from a display window. With MBO, the ladder can show deep levels and iceberg refills; without it, the broker’s aggregated book only publishes a limited number of levels, so deeper prices are simply absent. The code records the MBO refusal as intermittent on the broker side. The badge appears only on Rithmic: bridges and Quantower deliver aggregated depth and hide it.
The age indicator shares its 3-second threshold with the heatmap ladder. It is the one signal that separates “nobody is trading” from “the connection is down”.
How to fix it
- If MBO is grey, reload the chart or reconnect later: the refusal has been intermittent.
- If the depth age is red during market hours, check the connection badge and the chart status bar.
- Scroll over the ladder to explore depth; faded levels were seen earlier in the session and are no longer in the live book.
What it is not
- Not a ladder setting: “Levels / side” cannot show levels the feed does not publish.
- Not proof of a quiet market when the age is red.
When to contact support
If the problem persists, contact support through Menu → Report a problem, or on the Senzoukria Discord. Say how long MBO stayed grey across sessions and include the Rithmic system name.
Related pages
In the same section
- dxFeed: no order book
- Databento sessions not written
- Free Rithmic demo refused
- Databento files set aside
- GEX delayed or stale
- Databento file names without a date
- GEX no data or provider error
- DBN parent symbol not imported
This page in other languages
Frequently asked questions
- Why don’t I see iceberg badges?
- Iceberg detection relies on the order-by-order feed. With aggregated L2 only, or on bridges, there is nothing per order to follow.
- What are the faded levels in the DOM?
- Levels seen earlier in the session that are no longer in the live book.