Chainstack Outage History

Chainstack degraded · 4 active incidents View live status →

Chainstack had 226 outages in the last 2 years totaling 119h 39m of downtime — averaging 9.3 incidents per month.

There were 226 Chainstack outages since December 10, 2025 totaling 119h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.chainstack.com

Minor July 9, 2026

Degraded performance on Arbitrum Sepolia (Chainstack Cloud, Tokyo)

Detected by Pingoru
Jul 09, 2026, 08:52 AM UTC
Resolved
Jul 09, 2026, 09:32 AM UTC
Duration
40m
Affected: Arbitrum Global Nodes (Arbitrum Sepolia)
Timeline · 3 updates
  1. investigating Jul 09, 2026, 08:52 AM UTC

    We are currently investigating this incident.

  2. monitoring Jul 09, 2026, 08:57 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jul 09, 2026, 09:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 8, 2026

Berachain Mainnet Sync issue

Detected by Pingoru
Jul 08, 2026, 07:38 PM UTC
Resolved
Jul 08, 2026, 09:10 PM UTC
Duration
1h 31m
Affected: Berachain Global Nodes (Berachain Mainnet)
Timeline · 3 updates
  1. investigating Jul 08, 2026, 07:38 PM UTC

    We are currently investigating this incident.

  2. monitoring Jul 08, 2026, 08:30 PM UTC

    We have identified the cause of the Berachain mainnet sync issue and applied the required configuration update. The affected nodes are recovering, and we are monitoring synchronization progress.

  3. resolved Jul 08, 2026, 09:10 PM UTC

    Berachain mainnet nodes are fully synced and operating normally.

Read the full incident report →

Major July 8, 2026

Solana Mainnet - Instability affecting New York cluster

Detected by Pingoru
Jul 08, 2026, 05:18 PM UTC
Resolved
Jul 08, 2026, 08:29 PM UTC
Duration
3h 10m
Affected: Solana Global Nodes (Solana Mainnet)Solana Trader Nodes (Solana Mainnet Full (Chainstack Cloud, New York))
Timeline · 3 updates
  1. investigating Jul 08, 2026, 05:18 PM UTC

    We are currently investigating this incident.

  2. monitoring Jul 08, 2026, 06:19 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jul 08, 2026, 08:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 7, 2026

Degraded Performance on TON Testnet and Mainnet

Detected by Pingoru
Jul 07, 2026, 05:54 PM UTC
Resolved
Jul 07, 2026, 09:38 PM UTC
Duration
3h 43m
Affected: TON Global Nodes (TON Mainnet API v2)TON Global Nodes (TON Mainnet API v3)TON Global Nodes (TON Testnet API v2)TON Global Nodes (TON Testnet API v3)
Timeline · 3 updates
  1. investigating Jul 07, 2026, 05:54 PM UTC

    We are currently investigating this incident.

  2. investigating Jul 07, 2026, 06:30 PM UTC

    We are currently investigating this incident.

  3. resolved Jul 07, 2026, 09:38 PM UTC

    We identified a storage issue on the underlying infrastructure. Mitigation has been applied, the affected services have been restored, and the issue is now resolved.

Read the full incident report →

Major July 6, 2026

Degraded Performance in Ashburn Region Affecting Multiple Networks

Detected by Pingoru
Jul 06, 2026, 05:51 PM UTC
Resolved
Jul 06, 2026, 06:45 PM UTC
Duration
54m
Affected: Cronos Global Nodes (Cronos Mainnet)Ethereum Global Nodes (Ethereum Mainnet)Ethereum Trader Nodes (Ethereum Mainnet Archive (Chainstack Cloud, Ashburn))Ethereum Trader Nodes (Ethereum Mainnet Full (Chainstack Cloud, Ashburn))Polygon Global Nodes (Polygon Amoy Testnet)
Timeline · 3 updates
  1. investigating Jul 06, 2026, 05:51 PM UTC

    We are currently investigating this incident.

  2. monitoring Jul 06, 2026, 06:45 PM UTC

    The issue was caused by an underlying infrastructure storage problem during a disk replacement, which temporarily affected multiple services. The storage has recovered, and the impacted workloads are back online. We will continue to monitor the environment while the remaining repair on one dedicated node is completed.

  3. resolved Jul 06, 2026, 06:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 4, 2026

Gnosis Chiado Testnet - Degraded Performance

Detected by Pingoru
Jul 04, 2026, 09:25 PM UTC
Resolved
Jul 04, 2026, 10:31 PM UTC
Duration
1h 6m
Affected: Gnosis Global Nodes (Gnosis Chain Chiado Testnet)Gnosis Trader Nodes (Gnosis Chiado Testnet Full (Virtuozzo, Frankfurt))
Timeline · 2 updates
  1. investigating Jul 04, 2026, 09:25 PM UTC

    We are currently investigating this incident. Issues affecting lighthouse layer.

  2. resolved Jul 04, 2026, 10:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 4, 2026

Monad Testnet - 503's response codes observed

Detected by Pingoru
Jul 04, 2026, 01:33 AM UTC
Resolved
Jul 04, 2026, 02:16 AM UTC
Duration
42m
Affected: Monad Global Nodes (Monad Testnet)
Timeline · 3 updates
  1. investigating Jul 04, 2026, 01:33 AM UTC

    We are currently investigating this incident.

  2. monitoring Jul 04, 2026, 01:36 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jul 04, 2026, 02:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 2, 2026

Increased latency in LAX region

Detected by Pingoru
Jul 02, 2026, 08:56 AM UTC
Resolved
Jul 02, 2026, 04:12 PM UTC
Duration
7h 15m
Affected: Arbitrum Global Nodes (Arbitrum One Mainnet)Arbitrum Global Nodes (Arbitrum Sepolia)Avalanche Global Nodes (Avalanche Mainnet)Base Global Nodes (Base Mainnet)Bitcoin Global Nodes (Bitcoin Mainnet)Fantom Global Nodes (Fantom Mainnet)Optimism Global Nodes (Optimism Mainnet)Polygon zkEVM Global Nodes (Polygon zkEVM Mainnet)Starknet Global Nodes (Starknet Mainnet)ZKsync Era Global Nodes (ZKsync Era Mainnet)
Timeline · 4 updates
  1. investigating Jul 02, 2026, 08:56 AM UTC

    Arbitrum Sepolia & Avalanche Mainnet Global nodes may experience increase in latency specifically from Los Angeles (LAX) region due to Cloudflare maintenance:

  2. identified Jul 02, 2026, 10:29 AM UTC

    Impact increased to more protocols & networks in LAX region.

  3. monitoring Jul 02, 2026, 04:12 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jul 02, 2026, 04:12 PM UTC

    Post conclusion of maintenance on Cloudflare side, there were no more timeouts and latency jumps observed. The incident is considered resolved

Read the full incident report →

Minor July 1, 2026

Polygon ZkEVM degraded performance

Detected by Pingoru
Jul 01, 2026, 04:31 AM UTC
Resolved
Jul 01, 2026, 05:14 AM UTC
Duration
43m
Affected: Polygon zkEVM Global Nodes (Polygon zkEVM Mainnet)Polygon zkEVM Trader Nodes (Polygon zkEVM Mainnet Full (Chainstack Cloud, Los Angeles) )
Timeline · 2 updates
  1. investigating Jul 01, 2026, 04:31 AM UTC

    Nodes are currently lagging across all the clusters. We are currently investigating this incident.

  2. resolved Jul 01, 2026, 05:14 AM UTC

    Nodes are back in sync. This incident has been resolved.

Read the full incident report →

Minor June 30, 2026

Ethereum Mainnet Beacon Endpoint Instability

Detected by Pingoru
Jun 30, 2026, 09:39 PM UTC
Resolved
Jun 30, 2026, 11:10 PM UTC
Duration
1h 30m
Affected: Ethereum Beacon (Ethereum Mainnet Beacon)
Timeline · 2 updates
  1. investigating Jun 30, 2026, 09:39 PM UTC

    We are currently investigating this incident.

  2. resolved Jun 30, 2026, 11:10 PM UTC

    We have resolved the issue affecting performance of our Ethereum Mainnet Beacon nodes. The root cause has been traced to internal queue exhaustion for archive BeaconState execution. The response times have returned to normal and the service is stable.

Read the full incident report →

Major June 30, 2026

Tempo Testnet – Degraded Performance in New York Region

Detected by Pingoru
Jun 30, 2026, 02:15 PM UTC
Resolved
Jun 30, 2026, 03:10 PM UTC
Duration
54m
Affected: Tempo Global Nodes (Tempo Moderato Testnet)
Timeline · 4 updates
  1. investigating Jun 30, 2026, 02:15 PM UTC

    We are currently investigating this incident.

  2. identified Jun 30, 2026, 02:19 PM UTC

    The degraded performance is due to a stress test on the Tempo Testnet network. Our team is monitoring the situation, and we will provide further updates as they become available.

  3. monitoring Jun 30, 2026, 02:37 PM UTC

    Response times have returned to normal, and the upstream service is healthy.

  4. resolved Jun 30, 2026, 03:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 30, 2026

Polygon Mainnet degraded performance in Tokyo

Detected by Pingoru
Jun 30, 2026, 02:08 AM UTC
Resolved
Jun 30, 2026, 05:07 AM UTC
Duration
2h 58m
Affected: Polygon Global Nodes (Polygon Mainnet)
Timeline · 3 updates
  1. investigating Jun 30, 2026, 02:08 AM UTC

    Nodes seem to be out of sync. We are currently investigating this incident.

  2. monitoring Jun 30, 2026, 04:14 AM UTC

    We implemented a fix, nodes are back in sync. We are currently monitoring the result.

  3. resolved Jun 30, 2026, 05:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 26, 2026

Base Mainnet – Degraded Performance Due to Network Halt

Detected by Pingoru
Jun 26, 2026, 03:40 PM UTC
Resolved
Jun 27, 2026, 01:54 AM UTC
Duration
10h 13m
Affected: Base Global Nodes (Base Mainnet)Base Trader Nodes (Base Mainnet Full (Chainstack Cloud, Los Angeles))Base Global Nodes (Base Sepolia Testnet)Base Trader Nodes (Base Mainnet Archive (Chainstack Cloud, Los Angeles))
Timeline · 3 updates
  1. investigating Jun 26, 2026, 03:40 PM UTC

    We are currently investigating this incident.

  2. monitoring Jun 26, 2026, 06:53 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jun 27, 2026, 01:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 25, 2026

Solana Mainnet - Elevated response times affecting Singapore, Frankfurt and Los Angeles.

Detected by Pingoru
Jun 25, 2026, 05:35 PM UTC
Resolved
Jun 25, 2026, 07:45 PM UTC
Duration
2h 9m
Affected: Solana Global Nodes (Solana Mainnet)
Timeline · 3 updates
  1. investigating Jun 25, 2026, 05:35 PM UTC

    We are currently investigating this incident.

  2. monitoring Jun 25, 2026, 05:45 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jun 25, 2026, 07:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 25, 2026

Polygon Amoy Testnet – Degraded Performance

Detected by Pingoru
Jun 25, 2026, 04:52 PM UTC
Resolved
Jun 25, 2026, 06:53 PM UTC
Duration
2h
Affected: Polygon Global Nodes (Polygon Amoy Testnet)
Timeline · 2 updates
  1. investigating Jun 25, 2026, 04:52 PM UTC

    We are currently investigating this incident.

  2. resolved Jun 25, 2026, 06:53 PM UTC

    The issue was caused by the Polygon Amoy network upgrade (Valencia hard fork). The network has stabilized, and service has returned to normal.

Read the full incident report →

Minor June 25, 2026

Solana Mainnet - Elevated response times in London

Detected by Pingoru
Jun 25, 2026, 02:42 PM UTC
Resolved
Jun 26, 2026, 09:31 PM UTC
Duration
1d 6h
Affected: Solana Global Nodes (Solana Mainnet)Solana Trader Nodes (Solana Mainnet Full (Chainstack Cloud, Frankfurt))
Timeline · 2 updates
  1. investigating Jun 25, 2026, 02:42 PM UTC

    We are currently investigating this incident.

  2. resolved Jun 26, 2026, 09:31 PM UTC

    The affected nodes have recovered and response times are back to normal levels. We are closing this incident as resolved.

Read the full incident report →

Major June 25, 2026

Base Mainnet Archive – Degraded Performance in Ashburn, London, and Los Angeles Regions

Detected by Pingoru
Jun 25, 2026, 02:22 PM UTC
Resolved
Jun 26, 2026, 04:15 AM UTC
Duration
13h 53m
Affected: Base Global Nodes (Base Mainnet)
Timeline · 4 updates
  1. investigating Jun 25, 2026, 02:22 PM UTC

    We are currently investigating this incident.

  2. identified Jun 25, 2026, 04:10 PM UTC

    We have identified this as a network halt. Our team is actively monitoring the situation and will provide updates as more information becomes available.

  3. monitoring Jun 25, 2026, 11:06 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Jun 26, 2026, 04:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 25, 2026

Degraded performance on Tempo Moderato Testnet nodes

Detected by Pingoru
Jun 25, 2026, 07:57 AM UTC
Resolved
Jun 25, 2026, 08:49 AM UTC
Duration
52m
Affected: Tempo Global Nodes (Tempo Moderato Testnet)
Timeline · 2 updates
  1. investigating Jun 25, 2026, 07:57 AM UTC

    Our team is currently investigating the cause of the nodes falling out of sync.

  2. resolved Jun 25, 2026, 08:49 AM UTC

    The incident has been resolved and all nodes are now back in sync. The issue was caused by a network-wide outage on the Tempo Testnet:

Read the full incident report →

Minor June 24, 2026

Solana Mainnet - Elevated response times in Singapore

Detected by Pingoru
Jun 24, 2026, 09:38 PM UTC
Resolved
Jun 25, 2026, 12:06 AM UTC
Duration
2h 27m
Affected: Solana Global Nodes (Solana Mainnet)
Timeline · 2 updates
  1. investigating Jun 24, 2026, 09:38 PM UTC

    The team is currently working on equalizing the load to stabilize the response times.

  2. resolved Jun 25, 2026, 12:06 AM UTC

    We have resolved the issue affecting performance of our Solana Mainnet nodes. The response times have returned to normal and the service is stable.

Read the full incident report →

Minor June 24, 2026

Degraded performance on Base sepolia nodes

Detected by Pingoru
Jun 24, 2026, 08:47 AM UTC
Resolved
Jun 24, 2026, 10:48 AM UTC
Duration
2h 1m
Affected: Base Global Nodes (Base Sepolia Testnet)
Timeline · 2 updates
  1. investigating Jun 24, 2026, 08:47 AM UTC

    We are currently investigating this incident.

  2. resolved Jun 24, 2026, 10:48 AM UTC

    The issue affecting our Base Sepolia nodes has now been resolved and they are fully back in sync.

Read the full incident report →

Minor June 23, 2026

Solana Devnet degraded performance in Ashburn

Detected by Pingoru
Jun 23, 2026, 02:06 AM UTC
Resolved
Jun 23, 2026, 05:25 AM UTC
Duration
3h 18m
Affected: Solana Global Nodes (Solana Devnet)Solana Trader Nodes (Solana Devnet Full (Chainstack Cloud, Ashburn))
Timeline · 2 updates
  1. investigating Jun 23, 2026, 02:06 AM UTC

    We are currently investigating this incident.

  2. resolved Jun 23, 2026, 05:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 22, 2026

Degraded performance on Arbitrum Mainnet Global nodes

Detected by Pingoru
Jun 22, 2026, 08:51 AM UTC
Resolved
Jun 22, 2026, 11:07 AM UTC
Duration
2h 15m
Affected: Arbitrum Global Nodes (Arbitrum One Mainnet)
Timeline · 3 updates
  1. investigating Jun 22, 2026, 08:51 AM UTC

    We are currently investigating this incident.

  2. monitoring Jun 22, 2026, 10:03 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jun 22, 2026, 11:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 19, 2026

Degraded performance on Polygon Amoy

Detected by Pingoru
Jun 19, 2026, 01:40 PM UTC
Resolved
Jun 20, 2026, 12:39 PM UTC
Duration
22h 58m
Affected: Polygon Global Nodes (Polygon Amoy Testnet)
Timeline · 2 updates
  1. investigating Jun 19, 2026, 01:40 PM UTC

    We are currently investigating this incident.

  2. resolved Jun 20, 2026, 12:39 PM UTC

    This incident has been resolved.

Read the full incident report →