Switchboard has reached its stated September 25, 2026 end of technical support, turning a six-day migration warning into a live test of how well Solana’s decentralized finance stack can rewire its price feeds under deadline pressure.
The oracle project announced on September 19 that its core development contributor, Switchboard Technology Labs, would wind down and that all implementations were deprecated immediately. The team urged integrators to migrate to other providers, naming Pyth and RedStone as alternatives, with September 25 described as the last day of existing support.
The sunset removes one of Solana’s longer-standing oracle options, and the way applications handle it illustrates a broader point about blockchain infrastructure: a support deadline is an operational milestone, not proof that every feed stopped updating at midnight or that every application once associated with Switchboard still depends on it.
Three levels of evidence
Switchboard’s public documentation has named Kamino, Jito, marginfi and Drift as users. But those are historical integration claims from a provider selling an oracle service, not a real-time inventory of active feeds on deadline day. Assessing actual exposure requires separating three kinds of evidence.
First is the marketing or integration page, which shows a relationship existed. Second is a program’s supported configuration, visible in technical documentation or code. Third is the live configuration and recent update history of the actual market. Only the third supports a claim that a named market still relied on Switchboard at a given time, and even then a backup source may be configured, so the impact of a stopped primary feed must be checked against the relevant fallback and freshness rules.
Switchboard’s model was built on on-demand feeds: applications create or call the data they need, with prices made available through Solana accounts. A software development kit can support an oracle type long after the last bank switches away from it, while a website can change while a live reserve retains an older oracle account.
Marginfi’s pre-emptive exit
Marginfi offers the clearest documented route away from the dependency. Its protocol documentation retains SwitchboardPull and venue variants in an oracle table listing supported setups, alongside Pyth push feeds and Scope accounts, but a supported type is not the same as the feed a given bank uses today.
The project’s Program 0.1.11 upgrade note is more current and more specific. It instructed developers to upgrade the SDK to at least version 2.8.0 before September 4, saying banks would begin moving to new oracle setups from that date. The release added nine variants that do not depend on Switchboard, including Kamino Scope feeds and exchange-rate-based pricing for certain liquid staking and principal tokens.
The migration carries a subtle second failure mode: older SDKs cannot decode a bank configured with one of the new oracle enum values, and a single bank with an unsupported value can prevent Project0Client initialization and bank reads, not merely actions involving that bank. In other words, fixing an infrastructure dependency can break an integrator that has not updated its software.
Jito’s Tip Router still names Switchboard
Jito Foundation’s Tip Router overview, last updated roughly nine months before the deadline, says Switchboard determines the relative weight of assets such as JitoSOL and JTO held in vaults linked to the Tip Router. The pricing documentation names Switchboard as the current oracle feed and describes backup weights when feeds are unavailable.
Those documents place Switchboard in a specific job: pricing vault assets for weight calculations in a tip distribution and restaking system. They do not imply that an unavailable Switchboard feed would automatically liquidate a lending position, and the documented fallback mechanism weakens the claim that a support sunset halts all Tip Router operations. The exact fallback values, activation conditions and current live oracle accounts still require a program-state check.
No live protocol-wide count of unmigrated Switchboard feeds was verified for the September 25 deadline, a gap worth remembering when reading dramatic claims about stranded Solana markets. For context, Switchboard’s earlier funding round was 7.5 million USD in May 2024, a figure that says something about the venture’s history and nothing about today’s protocol exposure.
Why stale price feeds matter
The concern behind any oracle sunset is concrete. Lending and derivatives protocols rely on price feeds for collateral checks, and a stale feed can leave a market pricing an asset at an outdated level, mis-sizing risk in both directions. Whether that risk materializes depends on fallbacks, freshness rules and how quickly integrators migrated.
The migration also concentrates Solana’s oracle landscape further around Pyth and RedStone, the two providers Switchboard itself recommended. Pyth has continued expanding in the meantime, including price feeds powering Etherfi’s Earn product on Optimism.
For developers, the practical checklist after September 25 is straightforward: verify which oracle accounts live programs actually read, confirm SDK versions can decode new configuration values, and test fallback behavior before assuming a documented integration page describes a running system.
Market snapshot at publication (12:00 UTC, Sept. 25, 2026, CoinGecko via BitcoinsNews price cache): BTC 84,606 USD, ETH 2,716.64 USD, SOL 120.81 USD.
six days between the deprecation notice and support ending. marginfi made it but jito docs still listing switchboard feeds is not a great look
six days of warning to migrate price feeds on a chain with billions in tvl. marginfi moved, but jito docs still pointing at a dead feed is rough
pyth and redstone eating switchboards lunch on solana was already happening, this just made it official. rip to a 2021 era oracle
Pyth and RedStone were named as the landing spots from day one. The concerning part is how long stale docs linger after a deprecation like this
^ exactly. its not the feed dying that hurts, its some repo readme nobody updated telling a dev to integrate switchboard next week
tip router docs naming the feed while support ends today. someone at jito is getting a very boring friday
stale docs after a sunset are how new integrations end up on dead feeds months later. half of deprecation work is deleting your own marketing pages
boring friday is generous, that tip router doc is load bearing. someone should grep the repo before a mainnet break does it for them
Agreed on grepping the repo. A stale feed reference in tip router code is the kind of thing someone finds at 3am during an incident, never in review
RedStone quietly picking up another Solana defi migration. their feeds went from niche to default in about a year
default is doing a lot of work there. redstone won the migrations pyth did not already own, which was marginfi and not much else
swbx was the training wheels oracle for a lot of 2021 solana defi. everything it powered either graduated to pyth or died, no in between
graduated or died is exactly right. swbx fed so many low cap farms back in 2021, weird seeing the plug pulled for real now