Live / Alchemy / Incident
Alchemy: Base Mainnet - Elevated eth_getLogs Latency
Alchemy · blastapi.ioMinor incidentResolved2026-10-27 00:03 UTC
Public — what happened
Summary
Alchemy reported that some eth_getLogs requests on its Base Mainnet service were slower than normal, affecting its US West and US East regions. The company listed the start as 20:30 UTC on October 26, and its first update came at 22:36 UTC while it was investigating. By 23:34 UTC Alchemy said it had put a fix in place and was watching the results, and it marked the incident resolved at 00:03 UTC on October 27. The company did not state a cause in the text provided.
Affected
Base
Timeline
- Started — 2026-10-26 20:30 UTC
- Investigating — 2026-10-26 22:36 UTC
- Monitoring — 2026-10-26 23:34 UTC
- Resolved — 2026-10-27 00:03 UTC · 3h 33m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Alchemy against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Alchemy: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Alchemy report →
More from Alchemy
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.