Jussi Number: How many blocks behind are really behind?

My understanding of the jussi_num which you see when sending a node to Steem RPC is the latest block number that node has reached e.g. the block height for that node.

In my steem load balancer nodes, I have set it to allow max 100 blocks difference:

See this

The following nodes were "behind" the latest block height (more than 100) at the time of requests:

But, if you were simply sending a GET block request which is e.g. 100, then it will work despite that node is classified as "behind".. So not sure what is the best way to deal with this?

I've continued features and bug fixes for the Steem Load Balancer Nodes which is open sourced here: https://github.com/DoctorLai/steem-load-balancer

I have deployed/maintained two:

• London, UK: https://api.steemyy.com
• Dallas, TX, USA: https://steem.justyy.com

See witness nodes.

Steem to the Moon🚀!

• You can rent Steem Power via rentsp!
• You can swap the TRON:TRX/USDT/USDD to STEEM via tron2steem!
• You can swap the STEEM/SBD to SOL Solana via steem2sol!
• You can swap the STEEM/SBD to ETH Ethereum via steem2eth!
• You can swap the STEEM/SBD to Tether USDT (TRC-20) via steem2usdt!
• You can swap the STEEM/SBD to TRX (TRON) via steem2trx!
• You can swap the STEEM/SBD to BTS (BitShares) via steem2bts!
• Register a free STEEM account at SteemYY!
• Steem Block Explorer
• ChatGPT/Steem Integration: You can type !ask command to invoke ChatGPT
• Steem Witness Table and API
• Other Steem Tools