- Detected by Pingoru
- Jul 31, 2026, 04:56 AM UTC
- Resolved
- Jul 31, 2026, 05:31 AM UTC
- Duration
- 34m
Affected: Polygon Global Nodes (Polygon Mainnet)Polygon Trader Nodes (Polygon Mainnet Full (Chainstack Cloud, Ashburn))
Timeline · 2 updates
-
investigating Jul 31, 2026, 04:56 AM UTC
Upstreams are lagging in the Ashburn cluster. We are currently investigating this incident.
-
resolved Jul 31, 2026, 05:31 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 03:17 AM UTC
- Resolved
- Jul 31, 2026, 03:43 AM UTC
- Duration
- 26m
Affected: Arbitrum Global Nodes (Arbitrum Sepolia)
Timeline · 3 updates
-
investigating Jul 31, 2026, 03:17 AM UTC
The nodes may return 503 errors. We are currently investigating this incident.
-
monitoring Jul 31, 2026, 03:23 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Jul 31, 2026, 03:43 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 03:03 AM UTC
- Resolved
- Jul 31, 2026, 08:08 AM UTC
- Duration
- 5h 4m
Affected: Avalanche Trader Nodes (Avalanche Fuji Testnet (Virtuozzo, Frankfurt))Bitcoin Trader Nodes (Bitcoin Testnet Full (Virtuozzo, Frankfurt))Ethereum Trader Nodes (Ethereum Sepolia Testnet Full (Virtuozzo, Frankfurt))Harmony Trader Nodes (Harmony Mainnet Full (Virtuozzo, Frankfurt))Ethereum Beacon (Ethereum Sepolia Testnet Beacon (Virtuozzo, Frankfurt))Gnosis Trader Nodes (Gnosis Chiado Testnet Full (Virtuozzo, Frankfurt))
Timeline · 6 updates
-
investigating Jul 31, 2026, 03:03 AM UTC
Due to network maintenance, some chains may be temporarily inaccessible for a short period. Our team is working on the same. We apologize for any inconvenience caused.
-
monitoring Jul 31, 2026, 03:38 AM UTC
We implemented a fix and are currently monitoring the result.
-
identified Jul 31, 2026, 04:42 AM UTC
We are continuing to work on a fix for this incident.
-
resolved Jul 31, 2026, 06:26 AM UTC
This incident has been resolved.
-
identified Jul 31, 2026, 06:51 AM UTC
Nodes are unstable again. We are continuing to work on a fix for this incident.
-
resolved Jul 31, 2026, 08:08 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2026, 02:44 PM UTC
- Resolved
- Jul 30, 2026, 09:19 AM UTC
- Duration
- 18h 34m
Affected: Solana Global Nodes (Solana Mainnet)
Timeline · 3 updates
-
investigating Jul 29, 2026, 02:44 PM UTC
We are currently investigating this incident.
-
monitoring Jul 29, 2026, 03:26 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Jul 30, 2026, 09:19 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 02:59 PM UTC
- Resolved
- Jul 27, 2026, 03:37 PM UTC
- Duration
- 38m
Affected: Avalanche Global Nodes (Avalanche Fuji Testnet)
Timeline · 3 updates
-
investigating Jul 27, 2026, 02:59 PM UTC
We are currently investigating this incident.
-
monitoring Jul 27, 2026, 03:08 PM UTC
The issue has auto-resolved, and the affected services have recovered. We are continuing to monitor while the team investigates the root cause
-
resolved Jul 27, 2026, 03:37 PM UTC
The issue has been resolved, and all services are operating normally. We’ll continue monitoring to ensure stability
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 07:10 PM UTC
- Resolved
- Jul 24, 2026, 09:00 PM UTC
- Duration
- 1h 49m
Affected: Avalanche Global Nodes (Avalanche Mainnet)Arbitrum Trader Nodes (Arbitrum One Mainnet Archive (Chainstack Cloud, Los Angeles))Base Global Nodes (Base Mainnet)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 Global Nodes (Base Sepolia Testnet)Base Trader Nodes (Base Mainnet Archive (Chainstack Cloud, Los Angeles))Bitcoin Global Nodes (Bitcoin Mainnet)Bitcoin Global Nodes (Bitcoin Testnet)Celo Global Nodes (Celo Mainnet)Bitcoin Global Nodes (Bitcoin Signet Testnet GEN Masternode Instatus)Bitcoin Trader Nodes (Bitcoin Mainnet Full (Chainstack Cloud, Los Angeles))Ethereum Global Nodes (Ethereum Mainnet)Fantom Global Nodes (Fantom Mainnet)Ethereum Global Nodes (Ethereum Sepolia Testnet)Ethereum Global Nodes (Ethereum Hoodi Testnet)Gnosis Global Nodes (Gnosis Chain Mainnet)Ethereum Beacon (Ethereum Mainnet Beacon)Gnosis Global Nodes (Gnosis Chain Chiado Testnet)Ethereum Beacon (Ethereum Sepolia Testnet Beacon)Hyperliquid Global Nodes (Hyperliquid Mainnet)Optimism Global Nodes (Optimism Mainnet)Optimism Global Nodes (Optimism Sepolia Testnet)Optimism Trader Nodes (Optimism Mainnet Archive (Chainstack Cloud, Los Angeles))Optimism Trader Nodes (Optimism Mainnet Full (Chainstack Cloud, Los Angeles))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)ZKsync Era Global Nodes (ZKsync Era Mainnet)ZKsync Era Global Nodes (ZKsync Era Sepolia Testnet)
Timeline · 2 updates
-
investigating Jul 24, 2026, 07:10 PM UTC
We are currently investigating this incident.
-
resolved Jul 24, 2026, 09:00 PM UTC
The intermittent connectivity issue affecting part of our LAX infrastructure has been resolved. Services are operating normally again.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 06:18 AM UTC
- Resolved
- Jul 30, 2026, 08:39 PM UTC
- Duration
- 6d 14h
Affected: Solana Global Nodes (Solana Mainnet)
Timeline · 6 updates
-
investigating Jul 24, 2026, 06:18 AM UTC
All upsttream nodes are lagging in Singapore. We are currently investigating this incident.
-
monitoring Jul 24, 2026, 07:02 AM UTC
We implemented a fix and are currently monitoring the result.
-
identified Jul 24, 2026, 08:37 AM UTC
The affected nodes are experiencing sync lag again. Our team continues to investigate and work towards a resolution.
-
identified Jul 24, 2026, 01:16 PM UTC
Impact has increased to Frankfurt region and nodes are experiencing increased response time for heavy requests. Our team continues to work towards resolution.
-
monitoring Jul 24, 2026, 01:51 PM UTC
We implemented a fix, response times have normalized and we will continue monitoring.
-
resolved Jul 30, 2026, 08:39 PM UTC
The issue has been resolved, and service performance has remained stable across the affected regions.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 03:06 PM UTC
- Resolved
- Jul 23, 2026, 03:33 PM UTC
- Duration
- 27m
Affected: BNB Smart Chain Global Nodes (BNB Smart Chain Testnet)BNB Smart Chain Trader Nodes (BNB Smart Chain Testnet Full (Chainstack Cloud, London))
Timeline · 2 updates
-
investigating Jul 23, 2026, 03:06 PM UTC
We are currently investigating this incident.
-
resolved Jul 23, 2026, 03:33 PM UTC
The issue was caused by peer connectivity on the affected BSC Testnet node. After updating the trusted peer list, the node successfully caught up and is now fully synced. Service has returned to normal.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 12:47 PM UTC
- Resolved
- Jul 23, 2026, 01:58 PM UTC
- Duration
- 1h 10m
Affected: Solana Global Nodes (Solana Mainnet)
Timeline · 3 updates
-
investigating Jul 23, 2026, 12:47 PM UTC
We are currently investigating what is causing our Solana Mainnet nodes to respond with 5xx errors.
-
monitoring Jul 23, 2026, 01:25 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Jul 23, 2026, 01:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 10:25 AM UTC
- Resolved
- Jul 23, 2026, 11:08 AM UTC
- Duration
- 42m
Affected: Solana Global Nodes (Solana Mainnet)
Timeline · 2 updates
-
identified Jul 23, 2026, 10:25 AM UTC
We are continuing to work on a fix for this incident.
-
resolved Jul 23, 2026, 11:08 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 08:00 AM UTC
- Resolved
- Jul 23, 2026, 08:55 AM UTC
- Duration
- 55m
Affected: Base Global Nodes (Base Mainnet)
Timeline · 2 updates
-
investigating Jul 23, 2026, 08:00 AM UTC
Our team is currently investigating an issue causing customers to receive 503 errors from their Base Mainnet nodes.
-
resolved Jul 23, 2026, 08:55 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 05:45 PM UTC
- Resolved
- Jul 22, 2026, 06:35 PM UTC
- Duration
- 49m
Affected: Berachain Global Nodes (Berachain Mainnet)
Timeline · 2 updates
-
investigating Jul 22, 2026, 05:45 PM UTC
We are currently investigating this incident.
-
resolved Jul 22, 2026, 06:35 PM UTC
The issue was caused by an outdated Berachain Testnet configuration following the network upgrade. The affected nodes have been updated, recovered, and are now operating normally across all regions.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 07:49 AM UTC
- Resolved
- Jul 22, 2026, 10:00 AM UTC
- Duration
- 2h 10m
Affected: BNB Smart Chain Global Nodes (BNB Smart Chain Mainnet)BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Archive (Chainstack Cloud, Ashburn))
Timeline · 3 updates
-
investigating Jul 22, 2026, 07:49 AM UTC
We are currently investigating this incident.
-
monitoring Jul 22, 2026, 09:20 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Jul 22, 2026, 10:00 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2026, 07:08 AM UTC
- Resolved
- Jul 22, 2026, 08:10 AM UTC
- Duration
- 1h 1m
Affected: Sui Global Nodes (Sui Testnet)
Timeline · 2 updates
-
investigating Jul 22, 2026, 07:08 AM UTC
We are currently investigating the cause of the intermittent timeouts affecting our Sui Testnet nodes.
-
resolved Jul 22, 2026, 08:10 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 06:01 PM UTC
- Resolved
- Jul 21, 2026, 08:31 PM UTC
- Duration
- 2h 30m
Affected: Polygon Global Nodes (Polygon Mainnet)Polygon Trader Nodes (Polygon Mainnet Full (Chainstack Cloud, Ashburn))Polygon Trader Nodes (Polygon Mainnet Archive (Chainstack Cloud, Ashburn))
Timeline · 3 updates
-
investigating Jul 21, 2026, 06:01 PM UTC
We are currently investigating this incident, which currently affects connectivity within our cluster.
-
monitoring Jul 21, 2026, 06:42 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Jul 21, 2026, 08:31 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 06:08 AM UTC
- Resolved
- Jul 21, 2026, 06:40 AM UTC
- Duration
- 32m
Affected: Ronin Global Nodes (Ronin Saigon)
Timeline · 2 updates
-
investigating Jul 21, 2026, 06:08 AM UTC
Ronin Saigon L2 nodes are lagging across all clusters. We are currently investigating this incident.
-
resolved Jul 21, 2026, 06:40 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2026, 01:21 AM UTC
- Resolved
- Jul 19, 2026, 05:11 AM UTC
- Duration
- 3h 49m
Affected: BNB Smart Chain Global Nodes (BNB Smart Chain Mainnet)BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Archive (Chainstack Cloud, London))BNB Smart Chain Trader Nodes (BNB Smart Chain Mainnet Full (Chainstack Cloud, London))
Timeline · 2 updates
-
identified Jul 19, 2026, 01:21 AM UTC
We have identified the issue causing the degraded performance on our BSC Mainnet nodes in London region. Elevated response times are expected for `eth_getLogs` calls. The root cause has been traced to a resource exhaustion. We are currently working on mitigation strategies.
-
resolved Jul 19, 2026, 05:11 AM UTC
We implemented a fix by adding more capacity, and things have stabilized. The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 02:34 PM UTC
- Resolved
- Jul 16, 2026, 03:28 PM UTC
- Duration
- 54m
Affected: Polygon Trader Nodes (Polygon Mainnet Archive (Chainstack Cloud, London))
Timeline · 2 updates
-
investigating Jul 16, 2026, 02:34 PM UTC
We are currently investigating this incident.
-
resolved Jul 16, 2026, 03:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 02:52 PM UTC
- Resolved
- Jul 15, 2026, 04:00 PM UTC
- Duration
- 1h 8m
Affected: Tempo Global Nodes (Tempo Moderato Testnet)
Timeline · 2 updates
-
investigating Jul 15, 2026, 02:52 PM UTC
We’re currently experiencing degraded performance on our Tempo Testnet nodes due to an ongoing network stress test, as confirmed by the Tempo team.
-
resolved Jul 15, 2026, 04:00 PM UTC
Performance has returned to normal, and the issue was resolved at 16:00 UTC. During the incident, the Tempo Testnet was under stress testing, which contributed to the observed degradation. Services are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2026, 12:11 AM UTC
- Resolved
- Jul 15, 2026, 12:43 PM UTC
- Duration
- 2d 12h
Affected: TON Global Nodes (TON Testnet API v2)TON Global Nodes (TON Testnet API v3)
Timeline · 2 updates
-
identified Jul 13, 2026, 12:11 AM UTC
Our team is currently working on a fix for an issue causing our TON Testnet nodes to restart continuously, which is resulting in 503 errors for customers.
-
resolved Jul 15, 2026, 12:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 08:04 PM UTC
- Resolved
- Jul 09, 2026, 08:22 PM UTC
- Duration
- 18m
Affected: Solana Global Nodes (Solana Devnet)
Timeline · 2 updates
-
investigating Jul 09, 2026, 08:04 PM UTC
We are currently investigating this incident.
-
resolved Jul 09, 2026, 08:22 PM UTC
This incident has been resolved.The issue was caused by an unintended simultaneous restart of both backend nodes. Service has been fully restored, and Solana Devnet is operating normally again.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 02:08 PM UTC
- Resolved
- Jul 10, 2026, 12:30 AM UTC
- Duration
- 10h 21m
Affected: BNB Smart Chain Global Nodes (BNB Smart Chain Testnet)BNB Smart Chain Trader Nodes (BNB Smart Chain Testnet Full (Chainstack Cloud, London))
Timeline · 3 updates
-
investigating Jul 09, 2026, 02:08 PM UTC
We are currently investigating this incident.
-
identified Jul 10, 2026, 12:30 AM UTC
We are continuing to work on a fix across multiple affected clusters for this incident.
-
resolved Jul 10, 2026, 12:30 AM UTC
The issue was fully resolved on Friday at 20:00 UTC, and services have been operating normally since then.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 02:00 PM UTC
- Resolved
- Jul 10, 2026, 03:28 PM UTC
- Duration
- 1d 1h
Affected: Linea Global Nodes (Linea Mainnet)
Timeline · 2 updates
-
identified Jul 09, 2026, 02:00 PM UTC
Our team has identified the cause of the issue and is actively working on a resolution. We will provide additional updates as they become available.
-
resolved Jul 10, 2026, 03:28 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jul 09, 2026, 08:52 AM UTC
We are currently investigating this incident.
-
monitoring Jul 09, 2026, 08:57 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Jul 09, 2026, 09:32 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jul 08, 2026, 07:38 PM UTC
We are currently investigating this incident.
-
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.
-
resolved Jul 08, 2026, 09:10 PM UTC
Berachain mainnet nodes are fully synced and operating normally.
Read the full incident report →
