Skip to main content
Alchemy

Solana getSignatureStatuses and getSignaturesForAddress Degraded Performance

Degraded Lasted 41m · started · Alchemy's page

Level
confirmed
Worst impact
Degraded
Components
Solana
Down Index
26of 100

What to do

  • Check whether you use Alchemy Solana. 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 41m it lasted.

    Anything that failed between 2026-06-24 17:23 UTC and 2026-06-24 18:05 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

  1. investigating

    We are currently investigating an issue with our infrastructure provider, which may result in elevated error rates or latency for the getSignatureStatuses and getSignaturesForAddress methods.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. 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-7167507adc

Is Alchemy still down?

No, this incident was resolved 2026-06-24 18:05 UTC. For Alchemy's live state, see https://down.guide/alchemy.

How long did it last?

41m, from 2026-06-24 17:23 UTC to 2026-06-24 18:05 UTC, by the times Alchemy posted.

What was affected?

Alchemy named Solana.

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.