Maintenance

We're implementing planned infrastructure improvements across both our testnet and mainnet environments to enhance performance and reliability.

Testnet And Mainnet DNS maintenance

We're implementing planned infrastructure improvements across both our testnet and mainnet environments to enhance performance and reliability.

FA Watch towers will be under maintenance.

We're conducting routine performance testing on Testnet to optimize system reliability.

We're implementing planned infrastructure improvements across both our testnet and mainnet environments to enhance performance and reliability.

We are going to make small adjustments on the infrastructure of our public endpoint. The downtime should be minimal, if any, but spurious RPC failures can be expected during the maintenance window.

We are going to make adjustments on the infrastructure of the sequencer, ahead of the change of operator. The downtime should be minimal, and the block production should not be affected. But it is possible that some RPC requests fail during the maintenance window.

We will perform a software upgrade on the Etherlink Testnet sequencer. Temporary disruption in transaction sequencing may occur during this window.

We are updating the DNS records for ghostnet.node.etherlink.com to point to new IP addresses associated with our public testnet RPC nodes. During the DNS propagation period, you may experience intermittent connectivity issues when resolving or accessing the service.

We will perform a software upgrade on the Etherlink Testnet sequencer. Temporary disruption in transaction sequencing may occur during this window.

MIDL.dev will perform a software upgrade on the Etherlink Mainnet Sequencer and Public endpoint. Temporary disruption in transaction sequencing and RPC services may occur during this window.

We're implementing planned infrastructure improvements on mainnet environments to enhance performance and reliability.

The FA Watch Tower will be undergoing maintenance

Switching the sequencer of etherlink testnet to Optimistic Labs. A downtime of 10 mns is expected.

User running a node must update their node to at least V0.31.

https://gitlab.com/tezos/tezos/-/releases/octez-evm-node-v0.32

https://medium.com/@etherlink/its-voting-month-for-etherlink-two-governance-votes-coming-in-july-2025-301ae7bcd29f

Testnet DNS maintenance

We will perform a software upgrade on the Etherlink Mainnet sequencer. Temporary disruption in transaction sequencing may occur during this window.

We will perform a software upgrade on the Etherlink Testnet sequencer. Temporary disruption in transaction sequencing may occur during this window.

We are going to make small adjustments to the infrastructure of our public RPC Mainnet RPC endpoints (node.mainnet.etherlink.com). The downtime should be minimal, if any, but spurious RPC failures can be expected during the maintenance window.

We will perform a restart on the Etherlink Mainnet sequencer in order to fine-tune its configuration. Temporary disruption in transaction sequencing may occur during this window.

We will perform a restart on the Etherlink Ghostnet sequencer in order to fine-tune its configuration. Temporary disruption in transaction sequencing may occur during this window.

MIDL.dev will perform a software upgrade on the Public endpoints. Temporary disruption in RPC services may occur during this window.

The DNS changes have been completed successfully.

We will perform a software upgrade on the Etherlink Mainnet sequencer. Temporary disruption in transaction sequencing may occur during this window.

We will perform a software upgrade on the Etherlink Testnet sequencer. Temporary disruption in transaction sequencing may occur during this window.

We will be updating the DNS record for relay.mainnet.etherlink.com to point to the updated infrastructure.

The migration from MIDL.dev to the new sequencer operator is expected to take place around 8AM BST (following a successful vote by Tezos bakers). MIDL.dev will halt block production 5 minutes ahead of the migration, and the new operator will resume it a few minutes after the migration. The migration will be transparent for the node providers (no manual intervention is needed except for upgrading their nodes to v0.35 or higher)