Live  /  Alchemy  /  Incident

Alchemy: Monad Mainnet - Degraded archive state requests

Alchemy · blastapi.ioMinor incidentResolved2026-10-29 21:01 UTC
Public — what happened

Summary

Alchemy said that some requests on its Monad Mainnet service were failing or unavailable if they asked for historical data older than the most recent 500,000 blocks. The company reported this beginning on 2026-10-27 at 13:23 UTC, rated it minor, and said it was working to bring full capacity back. Alchemy marked the incident resolved on 2026-10-29 at 21:01 UTC and did not describe a cause in the text provided.

Affected

Monad

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.