Skip to main content
SingleStore

GCP us-west1 region may be impacted for some customers

Maintenance Lasted 0m · started · SingleStore's page

Level
confirmed
Worst impact
Maintenance
Regions
us, us-west1

What to do

  • Check whether you use SingleStore in us, us-west1. 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.
  • Check that everything you run on SingleStore came back after the window closed 2026-03-07 23:37 UTC.

  • 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

    March 7, 2026 8:46PM UTC Investigating - We are investigating an issue in GCP us-west1 region. Some customers may have impaired SingleStore clusters. March 7, 2026 10:30PM UTC Identified - There is an unplanned maintenance by GCP for K8s cluster. Some customers may see intermittent disruptions on their SingleStore clusters. March 7, 2026 11:37PM UTC Resolved - Maintenance has completed.

    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-32bde9be6e

Is this SingleStore maintenance still going on?

No, it ended 2026-03-07 23:37 UTC.

How long did it last?

0m, from 2026-03-07 23:37 UTC to 2026-03-07 23:37 UTC, by the times SingleStore posted.

What was affected?

SingleStore named in us, us-west1.

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.