- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use SingleStore in us. 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-02-03 06:18 UTC and 2026-02-03 06:18 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
- resolved
February 3, 2026 3:03AM UTC Identified - Azure is having a service issue impacting availability of VM's in East US region: see update here from azure: https://azure.status.microsoft/en-us/status February 3, 2026 6:18AM UTC Resolved - Azure has mitigated the issue. We have run tests to confirm the ability to create new VM's across subscriptions in Azure East US region.
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-1b3eafafd0
Is SingleStore still down?
No, this incident was resolved 2026-02-03 06:18 UTC. For SingleStore's live state, see https://down.guide/singlestore.
How long did it last?
0m, from 2026-02-03 06:18 UTC to 2026-02-03 06:18 UTC, by the times SingleStore posted.
What was affected?
SingleStore named in us.
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.