Jito Bundle Status Monitoring: Pending, Landed, Failed and Invalid

A production guide to tracking Jito bundles after submission without confusing a returned bundle ID with successful on-chain execution.

A bundle ID is only an acknowledgement

The sendBundle response confirms that the Block Engine received the request. It does not guarantee auction selection, forwarding or landing. Store the bundle ID together with signatures, blockhash, opportunity ID and submission region.

Use the two status surfaces correctly

getInflightBundleStatuses covers recent submissions and reports Pending, Landed, Failed or Invalid. getBundleStatuses provides processed bundle details and confirmation state. Poll with bounded backoff instead of treating a temporary null response as a final failure.

Reconcile transaction signatures

After a bundle lands, verify every expected signature and the economic state change. Confirmation alone does not prove the strategy produced the expected token balances or profit.

Set operational deadlines

A trading opportunity has a shorter business lifetime than the technical blockhash. Mark it expired when the expected edge disappears, while continuing background reconciliation so late evidence cannot create duplicate retries.

Build reliable Solana execution

TierZero develops Solana MEV and arbitrage bots and low-latency infrastructure. See the official Jito transaction-send documentation and send your current execution flow through contact.

Need this in production?

Send your current stack, target chain, data providers and operational requirements through the TierZero contact page.