Avalanche Outage History
Avalanche is up right nowPingoru has recorded 41 incidents for Avalanche: 4 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 2 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 2 | 35 of 720 (5%) |
| October 2026 | 0 | 0 of 525 (0%) |
Incidents, newest first
Major September 19, 2026 Mainnet API degraded 1h 1m Mainnet APIs
Started Sep 19, 2026, 03:56 PM UTC· resolved Sep 19, 2026, 04:57 PM UTC
- investigating Sep 19, 2026, 03:56 PM UTC
We are currently investigating this issue.
- identified Sep 19, 2026, 03:56 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 19, 2026, 04:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 19, 2026, 04:57 PM UTC
This incident has been resolved.
Major September 8, 2026 ICM Relayer and C-Chain RPC outage on AvaCloud 1d 9h AvaCloud
Started Sep 08, 2026, 01:00 AM UTC· resolved Sep 09, 2026, 10:38 AM UTC
- investigating Sep 08, 2026, 02:53 PM UTC
The ICM Relayer and C-Chain RPC service on AvaCloud is reporting issues. Team is investigating.
- identified Sep 08, 2026, 02:55 PM UTC
The issue has been identified, the team is working on a fix.
- identified Sep 08, 2026, 02:58 PM UTC
The solution for the issue has been determined and the recovery procedure has has started.
- identified Sep 08, 2026, 02:59 PM UTC
Due to large size of databases involved, the recovery is taking longer than initially anticipated.
- identified Sep 08, 2026, 03:01 PM UTC
Service has been restored at a lower capacity. Full recovery efforts are still in progress.
- monitoring Sep 08, 2026, 06:01 PM UTC
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.
- resolved Sep 09, 2026, 10:38 AM UTC
Continued monitoring showed no further issues. All services are back to regular operation in all supported regions.
Major July 28, 2026 Fuji(Testnet) C-Chain Helicon Block Indexing 2h 4m Explorer
Started Jul 28, 2026, 03:09 PM UTC· resolved Jul 28, 2026, 05:13 PM UTC
- investigating Jul 28, 2026, 03:09 PM UTC
We are currently investigating delayed C-Chain block indexing after the Helicon activation.
- investigating Jul 28, 2026, 03:10 PM UTC
We are continuing to investigate this issue.
- investigating Jul 28, 2026, 03:31 PM UTC
We are continuing to investigate this issue.
- investigating Jul 28, 2026, 03:46 PM UTC
We are continuing to investigate this issue impacting Fuji(Testnet) C-Chain block ingestion.
- investigating Jul 28, 2026, 03:51 PM UTC
We are continuing to investigate this issue.
- investigating Jul 28, 2026, 03:52 PM UTC
We are continuing to investigate this issue.
- identified Jul 28, 2026, 04:08 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 28, 2026, 04:34 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 28, 2026, 05:13 PM UTC
This incident has been resolved.
Major November 22, 2025 AvaCloud new L1 creation issue 2d 20h AvaCloud
Started Nov 22, 2025, 12:16 AM UTC· resolved Nov 24, 2025, 08:26 PM UTC
- investigating Nov 22, 2025, 12:16 AM UTC
We are investigating AvaCloud new L1 creation issue. This does not impact any existing L1s.
- identified Nov 22, 2025, 12:48 AM UTC
The cause has been identified as an issue with a third party integration and a fix is being proposed and implemented.
- identified Nov 24, 2025, 02:18 PM UTC
A fix is being tested.
- monitoring Nov 24, 2025, 06:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Nov 24, 2025, 08:26 PM UTC
This incident has been resolved.
Minor October 20, 2025 C-Chain explorer delay 2h 37m Explorer
Started Oct 20, 2025, 12:15 PM UTC· resolved Oct 20, 2025, 02:52 PM UTC
- identified Oct 20, 2025, 01:15 PM UTC
Our data processing infrastructure is running behind which is causing delayed ingestion of C-Chain Explorer. Team is working on restoring the service.
- identified Oct 20, 2025, 01:17 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 20, 2025, 01:18 PM UTC
Service has been restored and data is being backfilled. We are continuing to monitor the recovery.
- resolved Oct 20, 2025, 02:52 PM UTC
Data has been backfilled, the explorer is now up fully up to date.
Minor March 26, 2025 AvaCloud instability 2h 43m AvaCloud
Started Mar 26, 2025, 12:48 AM UTC· resolved Mar 26, 2025, 03:31 AM UTC
- identified Mar 26, 2025, 12:48 AM UTC
We have identified the cause of the incident and are actively working on it.
- monitoring Mar 26, 2025, 01:39 AM UTC
Fixes have been put in places and we are actively monitoring.
- monitoring Mar 26, 2025, 01:41 AM UTC
We are continuing to monitor for any further issues.
- resolved Mar 26, 2025, 03:31 AM UTC
This incident has been resolved.
Major March 5, 2025 Fuji Testnet Instability 1d 17h Fuji Testnet Primary Network
Started Mar 05, 2025, 11:38 PM UTC· resolved Mar 07, 2025, 05:29 PM UTC
- investigating Mar 05, 2025, 11:38 PM UTC
We are aware of instability on the Fuji testnet and are currently investigating the root cause. No Avalanche Mainnet nodes or services are impacted.
- investigating Mar 05, 2025, 11:42 PM UTC
We are continuing to investigate this issue.
- investigating Mar 06, 2025, 03:05 AM UTC
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.
- identified Mar 06, 2025, 06:22 PM UTC
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.
- monitoring Mar 06, 2025, 09:44 PM UTC
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.
- resolved Mar 07, 2025, 05:29 PM UTC
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
Minor December 17, 2024 P-Chain Transaction Processing Delays 8h 40m Mainnet Primary Network
Started Dec 17, 2024, 02:47 PM UTC· resolved Dec 17, 2024, 11:27 PM UTC
- monitoring Dec 17, 2024, 02:47 PM UTC
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.
- resolved Dec 17, 2024, 11:27 PM UTC
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