Chainstack Outage History

Chainstack is up right now

Chainstack had 103 outages in the last 2 years totaling 280h 43m of downtime — averaging 4.2 incidents per month.

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

Source: https://status.chainstack.com

Notice May 10, 2026

Degraded performance on Base Mainnet

Detected by Pingoru
May 10, 2026, 05:01 PM UTC
Resolved
May 10, 2026, 05:29 PM UTC
Duration
28m
Affected: Base Global Nodes (Base Mainnet)Base Trader Nodes (Base Mainnet Archive (Chainstack Cloud, Los Angeles))
Timeline · 3 updates
  1. identified May 10, 2026, 05:01 PM UTC

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

  2. monitoring May 10, 2026, 05:23 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 10, 2026, 05:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 10, 2026

Solana Mainnet degraded performance (Chainstack Cloud, London)

Detected by Pingoru
May 10, 2026, 06:32 AM UTC
Resolved
May 10, 2026, 08:43 AM UTC
Duration
2h 11m
Affected: Solana Global Nodes (Solana Mainnet)Solana Trader Nodes (Solana Mainnet Full (Chainstack Cloud, London))
Timeline · 3 updates
  1. identified May 10, 2026, 06:32 AM UTC

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

  2. monitoring May 10, 2026, 07:59 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 10, 2026, 08:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2026

Plasma Testnet Peering Issues

Detected by Pingoru
May 08, 2026, 08:01 PM UTC
Resolved
May 08, 2026, 09:17 PM UTC
Duration
1h 15m
Affected: Plasma Global Nodes (Plasma Testnet)
Timeline · 2 updates
  1. investigating May 08, 2026, 08:01 PM UTC

    We are currently investigating this incident.

  2. resolved May 08, 2026, 09:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 7, 2026

Degraded performance on Ethereum Mainnet

Detected by Pingoru
May 07, 2026, 11:14 AM UTC
Resolved
May 07, 2026, 01:09 PM UTC
Duration
1h 55m
Affected: Ethereum Global Nodes (Ethereum Mainnet)Ethereum Trader Nodes (Ethereum Mainnet Full (Chainstack Cloud, London))Ethereum Trader Nodes (Ethereum Mainnet Full (Chainstack Cloud, Singapore))
Timeline · 3 updates
  1. investigating May 07, 2026, 11:14 AM UTC

    Users may experience elevated latency. We are currently investigating this incident.

  2. monitoring May 07, 2026, 12:23 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 07, 2026, 01:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2026

Sui Testnet Headlag

Detected by Pingoru
May 06, 2026, 10:04 PM UTC
Resolved
May 06, 2026, 10:11 PM UTC
Duration
7m
Affected: Sui Global Nodes (Sui Testnet)
Timeline · 2 updates
  1. investigating May 06, 2026, 10:04 PM UTC

    We are currently investigating this incident.

  2. resolved May 06, 2026, 10:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 6, 2026

Cronos Mainnet degraded performance

Detected by Pingoru
May 06, 2026, 12:30 AM UTC
Resolved
May 06, 2026, 02:55 AM UTC
Duration
2h 25m
Affected: Cronos Global Nodes (Cronos Mainnet)Cronos Trader Nodes (Cronos Mainnet Archive (Chainstack Cloud, Frankfurt))
Timeline · 4 updates
  1. investigating May 06, 2026, 12:30 AM UTC

    We are currently investigating this incident.

  2. identified May 06, 2026, 01:42 AM UTC

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

  3. monitoring May 06, 2026, 02:09 AM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved May 06, 2026, 02:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 5, 2026

Solana Mainnet getTokenLargestAccounts temporary method ban

Detected by Pingoru
May 05, 2026, 05:57 PM UTC
Resolved
May 11, 2026, 02:37 PM UTC
Duration
5d 20h
Affected: Solana Global Nodes (Solana Mainnet)Solana Trader Nodes (Solana Mainnet Full (Chainstack Cloud, London))Solana Trader Nodes (Solana Mainnet Full (Chainstack Cloud, New York))
Timeline · 2 updates
  1. identified May 05, 2026, 05:57 PM UTC

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

  2. resolved May 11, 2026, 02:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 5, 2026

Cronos Testnet - Incident

Detected by Pingoru
May 05, 2026, 04:05 PM UTC
Resolved
May 06, 2026, 10:05 AM UTC
Duration
17h 59m
Affected: Cronos Trader Nodes (Cronos Testnet Full (Chainstack Cloud, London))
Timeline · 2 updates
  1. investigating May 05, 2026, 04:05 PM UTC

    We are currently investigating this incident.

  2. resolved May 06, 2026, 10:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 5, 2026

Solana Mainnet degraded performance

Detected by Pingoru
May 05, 2026, 01:34 AM UTC
Resolved
May 06, 2026, 02:37 AM UTC
Duration
1d 1h
Affected: Solana Global Nodes (Solana Mainnet)
Timeline · 3 updates
  1. investigating May 05, 2026, 01:34 AM UTC

    We are currently investigating this incident.

  2. identified May 05, 2026, 04:02 AM UTC

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

  3. resolved May 06, 2026, 02:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 3, 2026

Solana Mainnet degraded performance in Singapore

Detected by Pingoru
May 03, 2026, 01:48 PM UTC
Resolved
May 03, 2026, 10:30 PM UTC
Duration
8h 41m
Affected: Solana Global Nodes (Solana Mainnet)
Timeline · 3 updates
  1. investigating May 03, 2026, 01:48 PM UTC

    We are currently investigating this incident.

  2. monitoring May 03, 2026, 05:06 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved May 03, 2026, 10:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 2, 2026

Polygon zkEVM Mainnet - PROBLEM

Detected by Pingoru
May 02, 2026, 04:42 PM UTC
Resolved
May 02, 2026, 05:47 PM UTC
Duration
1h 5m
Affected: Polygon zkEVM Global Nodes (Polygon zkEVM Mainnet)
Timeline · 3 updates
  1. investigating May 02, 2026, 04:42 PM UTC

    We are currently investigating this incident

  2. identified May 02, 2026, 04:58 PM UTC

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

  3. resolved May 02, 2026, 05:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 1, 2026

Polygon zkEVM - Degraded Performance

Detected by Pingoru
May 01, 2026, 03:30 PM UTC
Resolved
May 01, 2026, 04:02 PM UTC
Duration
32m
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 May 01, 2026, 03:30 PM UTC

    We are currently investigating this incident.

  2. resolved May 01, 2026, 04:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 29, 2026

Base Sepolia / Degraded Performance in Dallas

Detected by Pingoru
Apr 29, 2026, 08:24 AM UTC
Resolved
Apr 29, 2026, 12:31 PM UTC
Duration
4h 6m
Affected: Base Global Nodes (Base Sepolia Testnet)
Timeline · 2 updates
  1. investigating Apr 29, 2026, 08:24 AM UTC

    We are currently investigating this incident.

  2. resolved Apr 29, 2026, 12:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 29, 2026

Los Angeles (LAX) cluster degraded performance

Detected by Pingoru
Apr 29, 2026, 02:46 AM UTC
Resolved
Apr 29, 2026, 02:57 AM UTC
Duration
10m
Affected: Arbitrum Trader Nodes (Arbitrum One Mainnet Archive (Chainstack Cloud, Los Angeles))Arbitrum Trader Nodes (Arbitrum One Mainnet Full (Chainstack Cloud, Los Angeles))Avalanche Trader Nodes (Avalanche Mainnet Full (Chainstack Cloud, Los Angeles))Base Trader Nodes (Base Mainnet Full (Chainstack Cloud, Los Angeles))Base Trader Nodes (Base Mainnet Archive (Chainstack Cloud, Los Angeles))Bitcoin Trader Nodes (Bitcoin Mainnet Full (Chainstack Cloud, Los Angeles))Fantom Trader Nodes (Fantom Mainnet Archive (Chainstack Cloud, Los Angeles))Fantom Trader Nodes (Fantom Mainnet Full (Chainstack Cloud, Los Angeles))Optimism Trader Nodes (Optimism Mainnet Archive (Chainstack Cloud, Los Angeles))Optimism Trader Nodes (Optimism Mainnet Full (Chainstack Cloud, Los Angeles))Polygon zkEVM Trader Nodes (Polygon zkEVM Mainnet Full (Chainstack Cloud, Los Angeles) )ZKsync Era Trader Nodes (ZKsync Era Mainnet Archive (Chainstack Cloud, Los Angeles) )
Timeline · 3 updates
  1. investigating Apr 29, 2026, 02:46 AM UTC

    We are currently investigating this incident.

  2. monitoring Apr 29, 2026, 02:47 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Apr 29, 2026, 02:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026

Solana Mainnet Incident

Detected by Pingoru
Apr 28, 2026, 07:37 PM UTC
Resolved
Apr 28, 2026, 11:30 PM UTC
Duration
3h 52m
Affected: Solana Global Nodes (Solana Mainnet)Solana Trader Nodes (Solana Mainnet Full (Chainstack Cloud, London))Solana Trader Nodes (Solana Mainnet Full (Chainstack Cloud, New York))
Timeline · 2 updates
  1. investigating Apr 28, 2026, 07:37 PM UTC

    We are currently investigating this incident.

  2. resolved Apr 28, 2026, 11:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026

Sonic/Blaze Testnet degraded performance

Detected by Pingoru
Apr 28, 2026, 06:09 AM UTC
Resolved
Apr 28, 2026, 06:35 AM UTC
Duration
26m
Affected: Sonic Global Nodes (Sonic Blaze Testnet)Sonic Global Nodes (Sonic Testnet)
Timeline · 2 updates
  1. investigating Apr 28, 2026, 06:09 AM UTC

    We are currently investigating this incident.

  2. resolved Apr 28, 2026, 06:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026

BSC Testnet in LONDON degraded performance

Detected by Pingoru
Apr 27, 2026, 03:33 AM UTC
Resolved
Apr 27, 2026, 05:07 AM UTC
Duration
1h 33m
Affected: ChainstackBNB Smart Chain Global Nodes (BNB Smart Chain Testnet)BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, Ashburn))BNB Smart Chain Trader Nodes (BNB Smart Chain Testnet Full (Chainstack Cloud, London))
Timeline · 4 updates
  1. investigating Apr 27, 2026, 03:33 AM UTC

    We are currently investigating this incident.

  2. resolved Apr 27, 2026, 03:40 AM UTC

    This incident has been resolved.

  3. investigating Apr 27, 2026, 04:51 AM UTC

    We are currently investigating this incident.

  4. resolved Apr 27, 2026, 05:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 25, 2026

BSC Testnet in London - Headlag

Detected by Pingoru
Apr 25, 2026, 01:45 PM UTC
Resolved
Apr 25, 2026, 02:35 PM UTC
Duration
50m
Affected: ChainstackBNB Smart Chain Trader Nodes (BNB Smart Chain Testnet Full (Chainstack Cloud, London))
Timeline · 3 updates
  1. investigating Apr 25, 2026, 01:45 PM UTC

    We are currently investigating this incident.

  2. monitoring Apr 25, 2026, 02:16 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Apr 25, 2026, 02:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 25, 2026

BSC Mainnet in Singapore - Timeout issues

Detected by Pingoru
Apr 25, 2026, 01:40 PM UTC
Resolved
Apr 25, 2026, 02:49 PM UTC
Duration
1h 8m
Affected: ChainstackBNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, Singapore))
Timeline · 3 updates
  1. investigating Apr 25, 2026, 01:40 PM UTC

    We are currently investigating this incident.

  2. monitoring Apr 25, 2026, 02:17 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Apr 25, 2026, 02:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 25, 2026

Timeouts with APIs hosted in Singapore region

Detected by Pingoru
Apr 25, 2026, 08:06 AM UTC
Resolved
Apr 25, 2026, 08:48 AM UTC
Duration
42m
Affected: ChainstackBNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, Singapore))Ethereum Beacon (Ethereum Mainnet Beacon (Chainstack Cloud, Singapore))Plasma Global Nodes (Plasma Mainnet)TON Global Nodes (TON Testnet API v2)
Timeline · 3 updates
  1. identified Apr 25, 2026, 08:06 AM UTC

    We are experiencing interruptions and timeouts with our API traffic hitting Singapore region and this is being actively investigated

  2. monitoring Apr 25, 2026, 08:22 AM UTC

    The incident has been mitigated, performance restored and we are currently monitoring the result.

  3. resolved Apr 25, 2026, 08:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 24, 2026

Gnosis Chiado Testnet outage

Detected by Pingoru
Apr 24, 2026, 06:49 AM UTC
Resolved
Apr 24, 2026, 07:09 AM UTC
Duration
20m
Affected: ChainstackGnosis Global Nodes (Gnosis Chain Chiado Testnet)Gnosis Trader Nodes (Gnosis Chiado Testnet Full (Virtuozzo, Frankfurt))
Timeline · 4 updates
  1. investigating Apr 24, 2026, 06:49 AM UTC

    We are currently investigating this incident.

  2. identified Apr 24, 2026, 06:51 AM UTC

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

  3. monitoring Apr 24, 2026, 06:52 AM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Apr 24, 2026, 07:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 21, 2026

Ethereum Mainnet Incident

Detected by Pingoru
Apr 21, 2026, 02:35 PM UTC
Resolved
Apr 24, 2026, 07:11 AM UTC
Duration
2d 16h
Affected: ChainstackEthereum Trader Nodes (Ethereum Mainnet Archive (Chainstack Cloud, London))Ethereum Trader Nodes (Ethereum Mainnet Archive (Chainstack Cloud, Ashburn))
Timeline · 3 updates
  1. investigating Apr 21, 2026, 02:35 PM UTC

    We are currently investigating this incident.

  2. monitoring Apr 24, 2026, 01:18 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Apr 24, 2026, 07:11 AM UTC

    This incident has been resolved.

Read the full incident report →