FixesUpdated 23 Oct 20261 min read

"Transaction loads an address table account that doesn't exist" fix

The fix

The versioned transaction points to an address lookup table that is not on this network, was closed, or the app used a table from a different cluster.

What the error means

Transaction loads an address table account that doesn't exist

The versioned transaction points to an address lookup table that is not on this network, was closed, or the app used a table from a different cluster.

Where it comes fromSolana runtime (transaction error)
CodeAddressLookupTableNotFound

How to fix it

  1. Check the network: a lookup table on mainnet does not exist on devnet.
  2. If the app manages its own lookup table, recreate or extend it and rebuild the transaction.
  3. Fall back to a legacy transaction if the instruction fits in 1,232 bytes without a table.

If that is not it

  • If the table exists, the error may instead say it has an invalid owner or index; read the exact message.

More fixes: how to decode any Solana error code and why Solana transactions fail.

Source

Error text and code from Solana SDK transaction and instruction error definitions (anza-xyz/solana-sdk); Solana transaction documentation, read on 24 October 2026.

Questions people ask

What is an address lookup table?

An on-chain list of addresses that lets a versioned transaction reference more accounts while staying within the 1,232-byte limit.

Can a closed table be reused?

No. Create a new table and rebuild the transaction.

"Transaction loads an address table account that doesn't exist"