Skip to main content
SingleStore

Operational issue - Amazon Elastic Compute Cloud (N. Virginia)

Partial outage Lasted 0m · started · SingleStore's page

Level
confirmed
Worst impact
Partial outage

What to do

  • Check whether your product depends on SingleStore. 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 0m it lasted.

    Anything that failed between 2026-05-14 14:56 UTC and 2026-05-14 14:56 UTC may need a replay.
  • Subscribe to SingleStore's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=singlestore works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from SingleStore 1

  1. resolved

    May 8, 2026 9:39AM UTC Monitoring - We are monitoring the current ongoing AWS Outage in N. Virginia. Customers may face Increased Error Rate and Latency with Singlestore services due to the AWS issue. May 14, 2026 2:56PM UTC Resolved - Issue has been resolved as notified by AWS

    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-234fcccf56

Is SingleStore still down?

No, this incident was resolved 2026-05-14 14:56 UTC. For SingleStore's live state, see https://down.guide/singlestore.

How long did it last?

0m, from 2026-05-14 14:56 UTC to 2026-05-14 14:56 UTC, by the times SingleStore posted.

What caused it?

SingleStore hasn't published a root cause. If it does, it shows here.

Where does this come from?

SingleStore's official status page, https://status.singlestore.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.