Technologie & IA
Chainlink plans to remove 11 networks from CCIP on November 30
The November 17 changelog announces the end of messaging and token transfers to and from the affected networks. The legacy CCIP API is due to be permanently retired on the same day.

Eleven networks will leave CCIP’s coverage
On November 17, 2026, Chainlink announced that its CCIP interoperability protocol would stop supporting 11 networks on November 30. They are Corn, Core, Metal, Zora, Abstract, Edge, Lisk, Lens, Merlin, Superseed, and B2 Mainnet. The changelog says CCIP will stop supporting cross-chain messages or token transfers to and from those networks after that date. The measure covers the connections CCIP provides.
Chainlink attributes the decision to a review of use and economic viability across its connections. The notice discloses no traffic figures or thresholds for individual networks. It asks teams with affected integrations to coordinate migrations or wind-downs before November 30. The notice gives no time of day for the cutoff. It also does not detail how operations still in progress at the cutoff will be handled.
The legacy API will be retired on the same day
Chainlink’s documentation also sets November 30 for permanently retiring version 1 of its CCIP API. The first step came on November 11, when the API was disabled. According to the migration guide, version 1 requests have returned HTTP status 410 since then. Permanent retirement is therefore not the first disruption for software still using that version.
The guide says the second-generation API uses more parameters to estimate message delivery times, including the connection version and the token involved. It also identifies a change to the path for looking up a message and to some field names. An integration that tracks transmissions or estimates delivery times may therefore need separate adaptations to keep reading those data.
Switching APIs does not restore a connection
The changes affect different parts of the service. Network support determines whether CCIP can carry messages or tokens to and from a network. The API version concerns how software queries the service. Switching to the new API therefore does not keep routes that Chainlink plans to deactivate.
For a team running a CCIP integration, the first check concerns the networks at the start and end of its routes. The second concerns the API version its tracking tools rely on. Chainlink’s documents give both changes the same date and list the networks for the first. They do not give a single replacement route for all 11 networks.
