Previous incidents

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.

The team has updated the nodes to the latest version available v6.2.0. Aftter the update, the nodes caught up with the tip.

• https://github.com/zcash/zcash/releases/tag/v6.2.0

Our team identified and resolved a misconfiguration on our platform that was impacting transaction broadcasts. The configuration has been corrected, and full functionality has been restored.

We are implementing additional safeguards to prevent similar issues in the future. Thank you for your patience and understanding.

The team has found and fixed a configuration issue. The service has been reestablished.

We appreciate your patience and understanding.

We have recovered all historical data. The nodes are operational again.

We appreciate your patience and understanding.

We have closely monitored system performance over the past 12 hours. No further issues have been observed, and all services remain stable.

The incident is now considered fully resolved.
We thank you for your patience.

We have fully restored the service across our chains.

The remaining chains are back online:

• kcs-mainnet.gateway.tatum.io
• kcs-testnet.gateway.tatum.io

We appreciate your patience and understanding.