Avalanche Outage History

Avalanche is up right now

Avalanche had 7 outages in the last 2 years totaling 159h 43m of downtime — averaging 0.3 incidents per month.

There were 7 Avalanche outages since October 14, 2024 totaling 159h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.avax.network

Major September 8, 2026

ICM Relayer and C-Chain RPC outage on AvaCloud

Detected by Pingoru
Sep 08, 2026, 01:00 AM UTC
Resolved
Sep 09, 2026, 10:38 AM UTC
Duration
1d 9h
Affected: AvaCloud
Timeline · 7 updates
  1. investigating Sep 08, 2026, 02:53 PM UTC

    The ICM Relayer and C-Chain RPC service on AvaCloud is reporting issues. Team is investigating.

  2. identified Sep 08, 2026, 02:55 PM UTC

    The issue has been identified, the team is working on a fix.

  3. identified Sep 08, 2026, 02:58 PM UTC

    The solution for the issue has been determined and the recovery procedure has has started.

  4. identified Sep 08, 2026, 02:59 PM UTC

    Due to large size of databases involved, the recovery is taking longer than initially anticipated.

  5. identified Sep 08, 2026, 03:01 PM UTC

    Service has been restored at a lower capacity. Full recovery efforts are still in progress.

  6. 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.

  7. 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.

Read the full incident report →

Major November 22, 2025

AvaCloud new L1 creation issue

Detected by Pingoru
Nov 22, 2025, 12:16 AM UTC
Resolved
Nov 24, 2025, 08:26 PM UTC
Duration
2d 20h
Affected: AvaCloud
Timeline · 5 updates
  1. investigating Nov 22, 2025, 12:16 AM UTC

    We are investigating AvaCloud new L1 creation issue. This does not impact any existing L1s.

  2. 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.

  3. identified Nov 24, 2025, 02:18 PM UTC

    A fix is being tested.

  4. monitoring Nov 24, 2025, 06:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Nov 24, 2025, 08:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

C-Chain explorer delay

Detected by Pingoru
Oct 20, 2025, 12:15 PM UTC
Resolved
Oct 20, 2025, 02:52 PM UTC
Duration
2h 37m
Affected: Explorer
Timeline · 4 updates
  1. 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.

  2. identified Oct 20, 2025, 01:17 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Oct 20, 2025, 01:18 PM UTC

    Service has been restored and data is being backfilled. We are continuing to monitor the recovery.

  4. resolved Oct 20, 2025, 02:52 PM UTC

    Data has been backfilled, the explorer is now up fully up to date.

Read the full incident report →

Minor March 26, 2025

AvaCloud instability

Detected by Pingoru
Mar 26, 2025, 12:48 AM UTC
Resolved
Mar 26, 2025, 03:31 AM UTC
Duration
2h 43m
Affected: AvaCloud
Timeline · 4 updates
  1. identified Mar 26, 2025, 12:48 AM UTC

    We have identified the cause of the incident and are actively working on it.

  2. monitoring Mar 26, 2025, 01:39 AM UTC

    Fixes have been put in places and we are actively monitoring.

  3. monitoring Mar 26, 2025, 01:41 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Mar 26, 2025, 03:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2025

Fuji Testnet Instability

Detected by Pingoru
Mar 05, 2025, 11:38 PM UTC
Resolved
Mar 07, 2025, 05:29 PM UTC
Duration
1d 17h
Affected: Fuji Testnet Primary Network
Timeline · 6 updates
  1. 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.

  2. investigating Mar 05, 2025, 11:42 PM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Read the full incident report →

Minor December 17, 2024

P-Chain Transaction Processing Delays

Detected by Pingoru
Dec 17, 2024, 02:47 PM UTC
Resolved
Dec 17, 2024, 11:27 PM UTC
Duration
8h 40m
Affected: Mainnet Primary Network
Timeline · 2 updates
  1. 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.

  2. 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

Read the full incident report →