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

As listed on Alchemy’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Alchemy status & history page.

Related: Alchemy status & history. SquidGrid is not affiliated with Alchemy.