- Level
- confirmed
- Worst impact
- Degraded
- Components
- Tempo
What to do
Check whether you use Alchemy Tempo. 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 3h 33m it lasted.
Anything that failed between 2026-07-15 13:17 UTC and 2026-07-15 16:50 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
- investigating
We're seeing increased latency and higher block times on Tempo Testnet. This is caused by a planned stress test run by the Tempo network team, not by Alchemy infrastructure. The test window is expected to last up to 2 hours starting 2PM UTC on July 15. Performance should recover once the test concludes. No action is required on your end.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c84b681c1d
Is Alchemy still down?
No, this incident was resolved 2026-07-15 16:50 UTC. For Alchemy's live state, see https://down.guide/alchemy.
How long did it last?
3h 33m, from 2026-07-15 13:17 UTC to 2026-07-15 16:50 UTC, by the times Alchemy posted.
What was affected?
Alchemy named Tempo.
What caused it?
Alchemy hasn't published a root cause. If it does, it shows here.
Where does this come from?
Alchemy's official status page, https://status.alchemy.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.