[Network Wide] Arbitrum Mainnet & Arbitrum Based Rollups - Degraded Performance Across Multiple Regions

What to do

• Check whether you use Alchemy Arbitrum. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 24m it lasted.

  Anything that failed between 2026-05-20 20:10 UTC and 2026-05-20 20:34 UTC may need a replay.

• Subscribe to Alchemy's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=alchemy works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Alchemy 4

1. investigatingMay 20, 2026, 7:59 PM UTC

   We are currently investigating this issue.

   provider

2. investigatingMay 20, 2026, 8:10 PM UTC

   We are investigating an elevated rate of 503 and API errors affecting Arbitrum Mainnet. This is a network wide incident and we're working closely with Arbitrum team to restore full service. We will provide updates as more information becomes available!

   provider

3. monitoringMay 20, 2026, 8:20 PM UTC

   Arbitrum Mainnet nodes have stabilized. This was a network-wide issue affecting multiple providers, caused by instability with the Arbitrum relayer. The Arbitrum team has addressed the issue on their end. We are continuing to monitor but performance has returned to normal!

   provider

4. resolvedMay 20, 2026, 8:34 PM UTC

   The Arbitrum Mainnet degraded performance issue has been resolved!

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.