Previous incidents

Erigon has released a HotFix patch. The nodes are catching up to the tip.

• https://github.com/erigontech/erigon/releases/tag/v3.0.11

We are experiencing degraded performance on the Polygon Amoy (Testnet).

• The nodes are several minutes behind the tip.
• This may impact RPC requests, transaction propagation, and data consistency for applications relying on near-tip data.

Our team is actively monitoring the situation and working to restore performance.

We will provide an update as we have more information we can share.

The team has restored the service. Flare (Mainnet) nodes are following the tip again.

We appreciate your patience and understanding.

The nodes were able to sync again with the tip after the Heimdall hard fork.

We appreciate your patience and understanding.

The team has recovered the service.
We appreciate your patience and understanding.

Despite the issues with Erigon, The team has been able to sync the nodes with the tip.
We appreciate your patience and understanding.

Further mitigations have been implemented. We have observed a stable latency for the past hour. We will keep monitoring the situation.
We appreciate your patience and understanding.

The service has been reestablished.
We appreciate your patience and understanding.

We have reestablished service for Polygon Amoy (Testnet).
Our nodes are now following the chain tip.

We appreciate your patience and understanding.

The nodes are in sync with the tip.
The service has been reestablished.

The issue affecting Solana Mainnet nodes has been resolved.
All services are now operational. Our nodes are currently catching up to the latest block (tip) of the chain.
We are monitoring synchronization closely to ensure full stability and consistency across the network.

The chain behaviour has returned to normal.
We will keep monitoring the situation.

The performance issue has been resolved.
We appreciate your patience and understanding.

The performance issue has been resolved.
We appreciate your patience and understanding.

The performance issue has been resolved.
We appreciate your patience and understanding.

The performance issue has been resolved.
We appreciate your patience and understanding.

The latency issue has been resolved.
We appreciate your patience and understanding.

The performance issue has been resolved.
We appreciate your patience and understanding.

The performance issue has been resolved.
We appreciate your patience and understanding.

The team has resolved the incident. The service has been reestablished.

Casper (Mainnet) has been restored and operational for recent blocks. Access to older blocks remains limited.

NOTE: Due to Casper's unique sync method, from the tip backwards, the current available block range is 4,878,557 to 4,748,174 (as of April 28, 2025) and expanding.

The team has successfully managed to spin up IOTA Rebased and brought the service back online.

We appreciate your patience and understanding.

The team has resolved the incident with Cosmos (Mainnet). The service has been reestablished.

We appreciate your patience and understanding.