[Network-Wide] Base Mainnet Safe Head Delayed

What to do

• Check whether you use Alchemy Base. 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 2h 6m it lasted.

  Anything that failed between 2026-07-28 13:26 UTC and 2026-07-28 15:33 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 3

1. investigatingJul 28, 2026, 1:26 PM UTC

   We are investigating a network-wide stall affecting safe and finalized blocks on Base Mainnet.

   provider

2. identifiedJul 28, 2026, 1:32 PM UTC

   This is a network-wide issue on Base Mainnet, not specific to Alchemy. The Safe head is delayed because data batching to Ethereum L1 is lagging. New block production on Base Mainnet is progressing normally, and requests against the latest block are unaffected. Only queries and workflows that depend on the safe or finalized block tag will see staleness. Refer to the Base status page for the latest updates: https://status.base.org/incidents/j6y12tshwkcg

   provider

3. resolvedJul 28, 2026, 3:33 PM UTC

   This is resolved. Base Mainnet's Safe head has caught up and data batching to Ethereum L1 is back to normal. Block production was unaffected throughout. See the Base status page for their full update: https://status.base.org/incidents/j6y12tshwkcg

   provider

Corrections

None so far.

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