Unichain Mainnet - safe/finalized head stalled in use1

What to do

• Check whether you use Alchemy Unichain in us. 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 6h 14m it lasted.

  Anything that failed between 2026-08-24 12:23 UTC and 2026-08-24 18:37 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 2

1. investigatingAug 24, 2026, 12:23 PM UTC

   We are investigating reports of delayed safe and finalized block tag data on Unichain Mainnet for requests routed through our US East (use1) region. The latest block head and overall API serving are healthy and unaffected. Applications relying on safe/finalized tags (e.g. via eth_getBlockByNumber, eth_getLogs, eth_call) in this region may receive outdated block data. We are actively investigating and will provide updates as we have them!

   provider

2. resolvedAug 24, 2026, 6:37 PM UTC

   A subset of nodes serving Unichain Mainnet in our US East (use1) region experienced stalled safe/finalized block tracking, causing delayed safe/finalized block data for requests routed through that region. The latest block head and overall API serving were unaffected throughout and no elevated error rates were observed. We performed a rolling restart of the affected nodes, which resolved the issue. Safe/finalized data is now current and within normal lag across the region. This incident is resolved!

   provider

Corrections

None so far.

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