Alchemy Outage History

Alchemy is up right now

Pingoru has recorded 199 incidents for Alchemy: 199 in the last 12 months and 61 in the last 90 days.

Source: status.alchemy.com

199incidents recorded
199last 12 months
61last 90 days
21 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct13
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct17%
Pingoru began tracking Alchemy in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202630500 of 720 (70%)
May 202629297 of 744 (40%)
June 202620221 of 720 (31%)
July 202633112 of 744 (15%)
August 202626172 of 744 (23%)
September 20261563 of 720 (9%)
October 202613100 of 589 (17%)

Incidents, newest first

Minor April 13, 2026 Elevated 500s Across Multiple Networks at USW2 51m US West

Started Apr 13, 2026, 08:37 PM UTC· resolved Apr 13, 2026, 09:29 PM UTC

  1. investigating Apr 13, 2026, 08:56 PM UTC

    We’re currently investigating an issue causing elevated internal server errors across multiple networks. We’ll provide updates as soon as we have more information.

  2. monitoring Apr 13, 2026, 09:12 PM UTC

    A fix has been implemented and we are starting to see signs of recovery. We are monitoring the results.

  3. resolved Apr 13, 2026, 09:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 10, 2026 Polygon Amoy Degraded Performance - Load Test 2h 23m Polygon

Started Apr 10, 2026, 04:02 PM UTC· resolved Apr 10, 2026, 06:26 PM UTC

  1. monitoring Apr 10, 2026, 04:02 PM UTC

    Polygon is currently conducting a load test on the Amoy testnet. As a result, nodes are experiencing difficulty staying in sync, and customers may encounter degraded performance or delayed data on this network. Customers using custom webhooks may also experience delays in event delivery. We are actively monitoring the situation.

  2. resolved Apr 10, 2026, 06:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2026 [Network-Wide] Botanix Testnet RPC Degradation 3d 23h Botanix

Started Apr 09, 2026, 03:23 PM UTC· resolved Apr 13, 2026, 03:20 PM UTC

  1. investigating Apr 09, 2026, 03:23 PM UTC

    We are currently investigating degraded performance affecting Botanix Testnet. Our nodes are stalled at block 4,063,589 and not producing new blocks. This issue is network-wide and affects all Botanix Testnet RPC traffic. We are actively coordinating with the Botanix team and will provide updates as the situation develops.

  2. resolved Apr 13, 2026, 03:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2026 Degraded Performance (US East) 8h 4m US East

Started Apr 09, 2026, 10:42 AM UTC· resolved Apr 09, 2026, 06:47 PM UTC

  1. investigating Apr 09, 2026, 10:42 AM UTC

    We are investigating elevated error rates affecting some requests routed through our US East region. A subset of our infrastructure experienced an unexpected hardware failure, and we are working with our infrastructure provider to restore stability. Some requests may return errors or experience elevated latency during this time. Our team is actively working to reschedule affected workloads and restore full capacity.

  2. monitoring Apr 09, 2026, 11:30 AM UTC

    Our team has applied a fix and we are monitoring the results.

  3. resolved Apr 09, 2026, 06:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2026 [Network-Wide] opBNB Testnet Stalled 3h 3m opBNB

Started Apr 09, 2026, 10:26 AM UTC· resolved Apr 09, 2026, 01:29 PM UTC

  1. investigating Apr 09, 2026, 03:37 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 09, 2026, 03:37 PM UTC

    Preliminary observation suggests this may have been a network-wide stall. The network has resumed and is producing blocks.

Read the full incident report →

Minor April 7, 2026 Botanix Testnet RPC Degradation 41m Botanix

Started Apr 07, 2026, 12:28 PM UTC· resolved Apr 07, 2026, 01:09 PM UTC

  1. investigating Apr 07, 2026, 12:28 PM UTC

    We are currently investigating degraded performance affecting Botanix Testnet. Our nodes are stalled at block 3,955,262 and not producing new blocks. This issue is network-wide and affects all Botanix Testnet RPC traffic. We are actively coordinating with the Botanix team and will provide updates as the situation develops.

  2. resolved Apr 07, 2026, 01:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 3, 2026 Ink Sepolia EUC1 Downgraded Performance 2d 18h Ink Chain

Started Apr 03, 2026, 12:30 PM UTC· resolved Apr 06, 2026, 06:45 AM UTC

  1. investigating Apr 03, 2026, 02:37 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 03, 2026, 02:38 PM UTC

    We are currently investigating degraded performance on Ink Sepolia. Customers might experience elevated 503 error rates and latency.

  3. investigating Apr 03, 2026, 02:40 PM UTC

    We are continuing to investigate this issue.

  4. resolved Apr 06, 2026, 06:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 1, 2026 [Network-Wide] Rise Testnet Degraded Performance 6d 16h Rise

Started Apr 01, 2026, 03:16 PM UTC· resolved Apr 08, 2026, 07:41 AM UTC

  1. investigating Apr 01, 2026, 03:16 PM UTC

    We are currently investigating degraded performance on Rise Testnet. Customers might experience elevated 5xx error rates and latency.

  2. resolved Apr 08, 2026, 07:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 1, 2026 [Network-Wide] Blast Sepolia Degraded Performance 58d 6h Blast

Started Apr 01, 2026, 03:15 PM UTC· resolved May 29, 2026, 09:23 PM UTC

  1. investigating Apr 01, 2026, 03:15 PM UTC

    We are currently investigating degraded performance on Blast Sepolia. Customers might experience elevated error rates and latency.

  2. investigating Apr 01, 2026, 05:12 PM UTC

    We are continuing to investigate this issue.

Read the full incident report →

Minor March 27, 2026 Fraxtal Mainnet USE1 Degraded Performance 2d 15h Fraxtal

Started Mar 27, 2026, 05:42 PM UTC· resolved Mar 30, 2026, 09:01 AM UTC

  1. investigating Mar 27, 2026, 05:42 PM UTC

    We are currently investigating this issue, customers may experience elevated latency.

  2. resolved Mar 30, 2026, 09:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 26, 2026 Base Data APIs delayed ingestion 6h 15m

Started Mar 26, 2026, 06:05 PM UTC· resolved Mar 27, 2026, 12:21 AM UTC

  1. investigating Mar 26, 2026, 06:05 PM UTC

    We are investigating a delay in our data indexing pipeline. This is resulting in degraded data freshness across the Token, NFT, and Transfers APIs on Base Mainnet.

  2. monitoring Mar 26, 2026, 06:47 PM UTC

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

  3. resolved Mar 27, 2026, 12:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 26, 2026 Sei Mainnet degraded performance 3d 23h SEI

Started Mar 26, 2026, 10:12 AM UTC· resolved Mar 30, 2026, 09:32 AM UTC

  1. investigating Mar 26, 2026, 10:12 AM UTC

    We are currently investigating degraded performance on Sei Mainnet. Customers might experience elevated error rates and latency

  2. resolved Mar 30, 2026, 09:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 25, 2026 Sei Mainnet Degraded Performance 6h 59m SEI

Started Mar 25, 2026, 04:53 PM UTC· resolved Mar 25, 2026, 11:53 PM UTC

  1. investigating Mar 25, 2026, 04:53 PM UTC

    We are currently investigating degraded performance on Sei Mainnet. Customers might experience elevated error rates and latency

  2. resolved Mar 25, 2026, 11:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 25, 2026 Arbitrum Mainnet degraded performance 5h 56m Arbitrum

Started Mar 25, 2026, 03:03 PM UTC· resolved Mar 25, 2026, 09:00 PM UTC

  1. investigating Mar 25, 2026, 03:03 PM UTC

    We are currently investigating elevated latency for archival data on Arbitrum Mainnet

  2. resolved Mar 25, 2026, 11:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 25, 2026 [Network-Wide] Sonic Mainnet stalled 2d 2h Sonic

Started Mar 25, 2026, 10:16 AM UTC· resolved Mar 27, 2026, 12:42 PM UTC

  1. investigating Mar 25, 2026, 10:16 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 25, 2026, 12:18 PM UTC

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

  3. monitoring Mar 25, 2026, 01:40 PM UTC

    An accidental hard fork occurred on the Sonic mainnet due to a consensus-breaking change introduced in Sonic client v2.1.6, related to an upgraded Ethereum library containing CVE security patches. Nodes running older client versions fell out of consensus at block 66,026,364, while the network itself continued producing blocks normally. Our Sonic mainnet RPC nodes were affected. We have upgraded all nodes to v2.1.6 and initiated a full database resync from the latest snapshot. In the interim, traffic is being served through secondary infrastructure with updated binaries. Customers may experience intermittent errors or elevated latencies until primary nodes complete the resync process. The Sonic network remains fully operational -- blocks continue to be produced, transactions are processing, and funds are safe.

  4. monitoring Mar 26, 2026, 12:00 AM UTC

    Our Sonic mainnet RPC nodes are continuing to resync from the latest snapshot. During this process, all traffic is being routed through secondary infrastructure with updated binaries. Websocket connections are unavailable until the resync is complete, and customers may experience elevated latency or intermittent errors on RPC requests. We expect the resync to finish within the next several hours and will provide another update once primary nodes are back online and operating at full capacity.

  5. monitoring Mar 26, 2026, 06:29 PM UTC

    Several nodes in our primary fleet have successfully resynced and are now serving traffic. However, we are not yet back to full capacity; customers may experience elevated latency or an intermittent error rate. We will provide a final update once all nodes are fully back online

  6. resolved Mar 27, 2026, 12:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 25, 2026 X-Layer Testnet stalled 1d 7h X-Layer

Started Mar 25, 2026, 09:39 AM UTC· resolved Mar 26, 2026, 05:10 PM UTC

  1. investigating Mar 25, 2026, 09:39 AM UTC

    We are currently investigating this issue.

  2. identified Mar 25, 2026, 09:54 AM UTC

    The X-Layer team is currently conducting network-level load testing. This is causing intermittent performance issues across multiple RPC nodes. We are in direct communication with their team to mitigate the impact.

  3. resolved Mar 26, 2026, 05:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 24, 2026 Base Mainnet Flashblocks Degraded 8d 1h Base

Started Mar 24, 2026, 12:27 PM UTC· resolved Apr 01, 2026, 01:31 PM UTC

  1. investigating Mar 24, 2026, 12:27 PM UTC

    We are aware of an ongoing issue affecting Base Flashblocks on Mainnet. Base is currently not producing flashblocks. Standard block production on Base is unaffected. This is a chain-wide incident originating with Base. We are monitoring the situation and will provide updates as they become available. For the latest updates from Base directly, see their status page: https://status.base.org/incidents/dg4m8nxd622r

  2. monitoring Mar 30, 2026, 03:20 PM UTC

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

  3. resolved Apr 01, 2026, 01:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 24, 2026 Degraded Performance on Mantle Sepolia 13h 19m Mantle

Started Mar 24, 2026, 04:44 AM UTC· resolved Mar 24, 2026, 06:04 PM UTC

  1. investigating Mar 24, 2026, 04:44 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 24, 2026, 06:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 24, 2026 Unichain Sepolia Stalled 9h 46m Unichain

Started Mar 24, 2026, 12:18 AM UTC· resolved Mar 24, 2026, 10:05 AM UTC

  1. investigating Mar 24, 2026, 04:50 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 24, 2026, 04:53 AM UTC

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

  3. resolved Mar 24, 2026, 10:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 23, 2026 [Network-Wide] ApeChain Mainnet finalized & safe head stalled 1h 38m ApeChain

Started Mar 23, 2026, 07:32 PM UTC· resolved Mar 23, 2026, 09:10 PM UTC

  1. investigating Mar 23, 2026, 07:32 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 24, 2026, 04:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 23, 2026 Mode Sepolia stalled 11h 43m Mode

Started Mar 23, 2026, 07:27 PM UTC· resolved Mar 24, 2026, 07:10 AM UTC

  1. investigating Mar 23, 2026, 07:27 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 24, 2026, 04:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 23, 2026 [Network-Wide] Arbitrum Sepolia Stalled 5h 5m Arbitrum

Started Mar 23, 2026, 04:45 PM UTC· resolved Mar 23, 2026, 09:50 PM UTC

  1. investigating Mar 23, 2026, 05:45 PM UTC

    Arbitrum Sepolia is currently experiencing a network-wide stall. All services that rely on network progress are impacted. We are working closely with the Arbitrum team to resolve this as quickly as possible

  2. investigating Mar 23, 2026, 06:09 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 23, 2026, 08:11 PM UTC

    A bug in Nitro software caused a block divergence on Arbitrum Sepolia, leading to block production being halted as a precaution. This issue is affecting all Arbitrum Orbit rollups that depend on the same Nitro version. Other Impacted networks: Anime Sepolia ApeChain Curtis Mind Testnet Edge Testnet EARNM Testnet Additional Arbitrum-based rollups may also be affected No user funds are at risk. The team is actively working on an infrastructure update and a new Nitro release to restore block production.

  4. resolved Mar 23, 2026, 09:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 22, 2026 Degraded Performance on Sei Mainnet 1d 5h SEI

Started Mar 22, 2026, 08:40 AM UTC· resolved Mar 23, 2026, 02:22 PM UTC

  1. investigating Mar 22, 2026, 08:40 AM UTC

    We are currently investigating degraded performance on Sei Mainnet. Customers might experience elevated error rates and latency. We will share more updates as we have them.

  2. monitoring Mar 22, 2026, 09:10 AM UTC

    A fix has been applied and we are seeing reduction in error rates. We will continue to monitor and confirm full resolution.

  3. resolved Mar 23, 2026, 02:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 20, 2026 ZKsync Era & Abstract Mainnet - Finalized Tag Stalled 1h 46m Abstract, ZKsync

Started Mar 20, 2026, 02:41 PM UTC· resolved Mar 20, 2026, 04:27 PM UTC

  1. investigating Mar 20, 2026, 02:41 PM UTC

    We are currently investigating an issue where the finalized block tag on ZKsync Era and Abstract mainnet has stopped progressing. This appears to be an upstream network issue. We are monitoring for resolution and will provide updates as the situation develops.

  2. resolved Mar 20, 2026, 04:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2026 Abstract Mainnet Degraded Performance 8m Abstract

Started Mar 19, 2026, 08:26 PM UTC· resolved Mar 19, 2026, 08:35 PM UTC

  1. investigating Mar 19, 2026, 08:26 PM UTC

    We are currently investigating an issue affecting Abstract mainnet. The last confirmed block is 46887372. Customers may experience degraded performance or failures across all Abstract mainnet services, including JSON-RPC requests and other dependent functionality. This appears to be a chain-wide issue. We are actively monitoring the situation and working to restore full service.

  2. resolved Mar 19, 2026, 08:35 PM UTC

    This incident has been resolved.

Read the full incident report →