Avalanche Outage History

Avalanche is up right now

Avalanche had 4 outages in the last 2 years totaling 106h 29m of downtime — averaging 0.2 incidents per month.

There were 4 Avalanche outages since October 20, 2025 totaling 106h 29m 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 →