Avalanche had 8 outages in the last 2 years totaling 160h 45m of downtime — averaging 0.3 incidents per month.
There were 8 Avalanche outages since October 14, 2024 totaling 160h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The ICM Relayer and C-Chain RPC service on AvaCloud is reporting issues. Team is investigating.
The issue has been identified, the team is working on a fix.
The solution for the issue has been determined and the recovery procedure has has started.
Due to large size of databases involved, the recovery is taking longer than initially anticipated.
Service has been restored at a lower capacity. Full recovery efforts are still in progress.
Service has been restored to full functionality with increased latency for some of the regions while we continue to sync up all the provisioned regions.
Continued monitoring showed no further issues. All services are back to regular operation in all supported regions.
We are investigating AvaCloud new L1 creation issue. This does not impact any existing L1s.
The cause has been identified as an issue with a third party integration and a fix is being proposed and implemented.
A fix is being tested.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our data processing infrastructure is running behind which is causing delayed ingestion of C-Chain Explorer. Team is working on restoring the service.
We are continuing to work on a fix for this issue.
Service has been restored and data is being backfilled. We are continuing to monitor the recovery.
Data has been backfilled, the explorer is now up fully up to date.
We have identified the cause of the incident and are actively working on it.
Fixes have been put in places and we are actively monitoring.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are aware of instability on the Fuji testnet and are currently investigating the root cause. No Avalanche Mainnet nodes or services are impacted.
We are continuing to investigate this issue.
We are continuing to investigate the issue. Blocks continue to be accepted on Fuji blockchains. Fuji node operators should not update or restart nodes for the time being until the issue is identified. No Avalanche Mainnet nodes or services are impacted.
We've identified issues affecting Fuji nodes and are implementing a fix that will be released in a new AvalancheGo version. Blocks continue to be accepted on Fuji blockchains. Fuji node operators should not update or restart nodes for the time being until the fix version is released. The new release will be posted here once available. No Avalanche Mainnet nodes or services are impacted.
AvalancheGo v1.13.0-fuji has been release, which should fix any instability issues observed by Fuji testnet nodes. https://github.com/ava-labs/avalanchego/releases/tag/v1.13.0-fuji Node operators are encouraged to update as soon as possible. We are continuing to monitor the Fuji network performance.
The issue causing instability of Fuji nodes has been resolved with the latest AvalancheGo release. This release also schedules the Fortuna network upgrade to activate at 11:00 AM ET on Thursday, March 13th. All Fuji node operators should update their nodes prior to the activation time. https://github.com/ava-labs/avalanchego/releases/tag/v1.13.0-fuji
For the past few hours, transactions issued on the Avalanche P-Chain experienced delays due to improper P-Chain transaction mempool handling. A fix has been identified and improved acceptance times are being observed. Valid transactions issued during this time should now be included in blocks. If any transactions were dropped from the mempool, they can be safely re-issued. The Avalanche X- and C-Chains, and Avalanche L1s are not impacted.
P-Chain transactions are being accepted as expected. Primary Network Validator nodes are encouraged to upgrade to the latest AvalancheGo release (linked below) to leverage the latest P-Chain mempool handling improvements. https://github.com/ava-labs/avalanchego/releases/tag/v1.12.1