Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jun 29, 2026 - 10:00 UTC
Scheduled
We will perform an upgrade of the Solana Mainnet cluster from Agave & Jito v4.0.3 to Agave & Jito v4.1.0 on June 25, 2026, at 10:00 UTC.
This release includes the latest Solana validator improvements and fixes recommended for Mainnet operators. Our Testnet and Devnet clusters are already running v4.1.0.
No downtime is expected, but customers may experience brief connection interruptions and a small number of HTTP 503 responses as services restart and resynchronize with the cluster.
What changes for API consumers
This is a backward-compatible release. All changes are additive JSON extensions or value-precision refinements — no existing fields are removed or renamed. Well-behaved JSON clients are unaffected. Two response details are worth noting:
* getVoteAccounts — Each entry in the "current" and "delinquent" arrays gains a new optional field "inflation_rewards_commission_bps" (Option): the validator's commission in basis points (0–10000). Before SIMD-0291 feature-gate activation it is derived as percent * 100; after activation it is the native bps value. The existing "commission" (u8) field is still populated (derived from bps as bps.div_ceil(100).min(255) after activation). The new field is tagged serde(skip_serializing_if = "Option::is_none"), so older clients simply ignore it. Action: clients using strict deserialization that REJECT unknown fields should relax that setting. Standard additive JSON extension — most clients handle it transparently.
* getPriorityFeeEstimate / getRecentPrioritizationFees — The "prioritization_fee" in the response is now the EFFECTIVE price (rounded up to the nearest lamport, then re-expressed in micro-lamports per CU) instead of the raw micro-lamports-per-CU price. This makes the returned value consistent with what the bank actually charged. Values may be slightly HIGHER than before due to rounding. Consumers that compute fee estimates from this API may see small changes.
Test it now on Devnet & Testnet
You don't need to wait for the Mainnet window to validate your integration. Our Devnet and Testnet clusters are already running v4.1.0, so you can run the full set of your tests against them today — using the exact same version that Mainnet will be on. We especially recommend exercising any strict JSON deserialization (getVoteAccounts) and any priority-fee estimation logic against these endpoints before June 25.