Last updated: November 15, 2026
Is Alchemy down? User reports show problems with Alchemy
Alchemy gives developers the pipes and tools that blockchain apps run on, from API endpoints to webhooks and debug screens. Builders land here when Alchemy down reports climb or requests start failing across many apps at once. The live Alchemy status above shows if the fault sits with Alchemy or with one chain.
Report a problem !
Select which issue applies
Alchemy problems reported in the last 24 hours
Most reported problems
All quiet. No issues reported in the last 24 hours.
Your feedback
How would you rate Alchemy over the past 3 months?
Most reported locations
Where Alchemy reports are coming from in the last 24 hours.
No problem locations to show yet. Alchemy looks fine right now. Locations appear here as soon as users submit reports.
Latest Alchemy user reports
No reports yet — be the first to report a problem above.
Alchemy outage history
Our latest check and the live report status for Alchemy.
✓ Our latest check (13 November 2026, 10:19 PM PKT): alchemy.com answered normally in 446 ms.
Good news. Alchemy has no reported problems right now. If it is not working for you, report it above and your report will appear here.
Alchemy uptime and reports
Live report counts and the day by day record for the last 30 days.
User reports received in each period.
Last 30 days, day by day: 16 October 2026 to 14 November 2026
Green: up. Red: outage. Amber: some checks failed. Grey: no record yet.
The daily record builds from today as our checks run. Grey days have no saved record yet. A red day marks a confirmed outage.
Get Alchemy down alerts
Leave your email and we will tell you when Alchemy is having problems, and when it is back up. No spam.
Alchemy on social media
An early signal from outside our site, watched in rotation.
Posts on Bluesky saying Alchemy is down. Checked 14 November 2026, 3:55 AM PKT.
Quiet right now. Nobody on Bluesky is saying Alchemy is down.
Guides that can fix it
Step by step fixes for the problems people report most.
→ An App Is Not Working? Fixes for Android and iPhone
→ Login Problems That Are Not an Outage
→ How to Clear the Cache in Firefox, Safari and Edge
Is Alchemy down right now?
Check the live status at the top of this page first. It shows the current Alchemy status with fresh reports from other developers. When dashboards and endpoints fail across many apps at the same time, the fault sits on the platform side. Teams shipping on this platform often study how people use the finished app inside Heap.
One failing app tells a narrower story. If your other apps answer fine on the same account, your keys, limits or code hold the fault. Compare your errors with the report graph before you rewrite anything.
Is Alchemy down for me or everyone?
Call one endpoint for a second chain from the dashboard tools. If every chain fails the same way, you are likely inside a wider Alchemy outage. If one chain fails while others answer, that chain or its node pool is the problem, and waiting is the right move.
What do developers use Alchemy for?
Alchemy gives apps a fast door into blockchains. Instead of running their own nodes, apps read balances, send transactions and watch events through Alchemy endpoints. Wallets, marketplaces and games lean on it around the clock.
The dashboard ties the pieces together. You create apps, copy keys, watch usage and set webhooks there. Debug tools show why a call failed, down to the exact request. When the dashboard will not load, the endpoints often still run.
How can you tell an Alchemy fault from a chain fault?
Chains halt on their own when their networks hit trouble. Test the same chain through a public explorer. If the explorer stalls too, the chain is at fault. If the explorer moves while your endpoint times out, the problem sits between you and Alchemy.
When do webhooks arrive late?
Webhooks queue up when event volume spikes or your server answers slowly. Alchemy retries failed deliveries, so a busy spell arrives as a late burst rather than a loss. A webhook that never lands at all points at a wrong address or a dead server on your side.
Does a rate limit mean the service is down?
No. A 429 error means your app passed its plan limit, and the service is up but closed to you until the window resets. An outage looks different: calls fail with server errors across apps and chains at once. The fixes below sort the two apart.
Common Alchemy Problems and Fixes
Most Alchemy faults sit with keys, limits or one chain. Run these checks before you touch your code.
Test a second chain
Call the same method on another chain from the dashboard. A pass there clears your account and keys. The fault then sits with the first chain or its endpoint, and you can wait with proof.
Check your usage against the limit
Open the usage screen and compare today calls with your plan cap. A flat line at the cap explains 429 errors at once. Spread calls out, cache reads, or raise the plan for busy apps.
Rotate a rejected key
A key pasted with a space or copied from an old app fails quietly. Copy the key fresh from the app page in the dashboard. If it still fails, make a new key and retire the old one.
Point at a fresh endpoint address
Old endpoint addresses linger in config files long after an app moves. Copy the current address from the dashboard and update every config that calls it. Restart the app so it picks the new address up.
Answer webhooks faster
Slow servers make webhook queues grow. Return a success code at once, then do the heavy work in the background. Deliveries even out and retries drop within the hour.
Having a problem with Alchemy?
Comments are public and help others understand the issue.
Frequently Asked Questions
Is Alchemy down or is my app broken?
Check the status above, then call an endpoint for a second chain. If that call passes, your app or its key holds the fault. If every chain fails while reports climb, the outage is shared.
Why do my requests return 429 errors?
Your app passed its plan limit for this window. The service is up, but it refuses extra calls until the limit resets. Cache repeat reads and spread heavy jobs out to stay under the cap.
How do I check which chain has the problem?
Run the same call on two or three chains from the dashboard tools. The chain that fails alone carries the fault. A public explorer for that chain confirms it within a minute.
What does it mean when an endpoint times out?
The endpoint took too long to answer, so your app gave up waiting. Busy chains and heavy queries cause most timeouts. Ask for less data per call and retry with a short pause.
Can I test on a testnet while the main network struggles?
Yes. Testnets run apart from the main network, so your tests keep moving. Ask the faucet for test funds and point your app at the testnet endpoint. Switch back once the main network settles.
Does the dashboard show usage for each app?
Yes. Each app page breaks down calls, errors and heavy methods. A single loud method usually explains a sudden limit problem. Fix that call pattern and the errors fall away.