SingleStore Outage History

SingleStore is up right now

Pingoru has recorded 13 incidents for SingleStore: 7 in the last 12 months and 0 in the last 90 days.

Source: status.singlestore.com

13incidents recorded
7last 12 months
0last 90 days
13 daystypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking SingleStore in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026267 of 720 (9%)
May 20262156 of 744 (21%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 44 (0%)

Incidents, newest first

Minor May 8, 2026 Operational issue - Amazon Elastic Compute Cloud (N. Virginia) 6d 5h AWS Clusters, AWS Clusters (AWS Clusters — AWS US East 1 (N. Virginia))

Started May 08, 2026, 09:39 AM UTC· resolved May 14, 2026, 02:56 PM UTC

  1. monitoring May 08, 2026, 09:39 AM UTC

    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.

  2. resolved May 14, 2026, 02:56 PM UTC

    Issue has been resolved as notified by AWS

Read the full incident report →

Major May 8, 2026 Singlestore Portal Down 6d 11h Cluster Management, Cluster Management (Cluster Management — Customer Portal)

Started May 08, 2026, 03:21 AM UTC· resolved May 14, 2026, 02:57 PM UTC

  1. investigating May 08, 2026, 03:21 AM UTC

    We are aware that the portal is down and currently investigating.

  2. identified May 08, 2026, 04:20 AM UTC

    We have figured out the issue and currently working on mitigating it.

  3. monitoring May 08, 2026, 05:23 AM UTC

    The issue has been mitigated and we are currently monitoring.

  4. resolved May 14, 2026, 02:57 PM UTC

    Incident resolved

Read the full incident report →

Minor April 25, 2026 Partial Outage detected on status page 1d 21h Overall

Started Apr 25, 2026, 01:16 AM UTC· resolved Apr 26, 2026, 10:38 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 24, 2026 Azure Issues in East US 2d 18h Azure Clusters

Started Apr 24, 2026, 05:40 PM UTC· resolved Apr 27, 2026, 12:08 PM UTC

  1. monitoring Apr 24, 2026, 05:40 PM UTC

    Statement from Microsoft: "Impact Statement: Starting at 11:39 UTC on 24 April 2026, a subset of customers with resources in the East US region may experience failures or delays when provisioning, scaling, or updating Azure resources. This issue initially affected one availability zone in East US; as traffic was automatically rerouted and shared services were involved, some customers in other availability zones may also experience impact. " You can get updates from this page: https://app.azure.com/h/5GP8-W0G/f73961

  2. resolved Apr 27, 2026, 12:08 PM UTC

    Azure reported as Resolved at 4/25/2026, 1:15:00 AM

Read the full incident report →

Minor March 7, 2026 GCP us-west1 region may be impacted for some customers 2h 50m GCP Clusters

Started Mar 07, 2026, 08:46 PM UTC· resolved Mar 07, 2026, 11:37 PM UTC

  1. investigating Mar 07, 2026, 08:46 PM UTC

    We are investigating an issue in GCP us-west1 region. Some customers may have impaired SingleStore clusters.

  2. identified Mar 07, 2026, 10:30 PM UTC

    There is an unplanned maintenance by GCP for K8s cluster. Some customers may see intermittent disruptions on their SingleStore clusters.

  3. resolved Mar 07, 2026, 11:37 PM UTC

    Maintenance has completed.

Read the full incident report →

Major March 2, 2026 AWS UAE multiple services disrupted 73d 7h AWS Clusters, AWS Clusters (AWS Clusters — AWS Middle East 1 (UAE))

Started Mar 02, 2026, 07:28 AM UTC· resolved May 14, 2026, 02:58 PM UTC

  1. identified Mar 02, 2026, 07:28 AM UTC

    AWS is having an ongoing outage in UAE as multiple service are disrupted. Follow AWS updates here - https://health.aws.amazon.com/health/status

  2. resolved May 14, 2026, 02:58 PM UTC

    Issue is resolved by halting deployments to region

Read the full incident report →

Major February 3, 2026 Azure VM availability impacted in East US region 3h 15m Azure Clusters

Started Feb 03, 2026, 03:03 AM UTC· resolved Feb 03, 2026, 06:18 AM UTC

  1. identified Feb 03, 2026, 03:03 AM UTC

    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

  2. resolved Feb 03, 2026, 06:18 AM UTC

    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.

Read the full incident report →

Major October 20, 2025 Degraded performance on AWS us-east-1 16h 53m AWS Clusters

Started Oct 20, 2025, 08:18 AM UTC· resolved Oct 21, 2025, 01:11 AM UTC

  1. identified Oct 20, 2025, 08:18 AM UTC

    Degraded performance on AWS region us-east-1 due to ongoing AWS issues. Please follow AWS status page for more information https://health.aws.amazon.com/health/status

  2. identified Oct 20, 2025, 03:56 PM UTC

    Impact to workspace group and workspace creation/scaling (including autoscale) and intermittent database connectivity in AWS US East (N. Virginia / us-east-1) due to an upstream AWS issue; scheduled and interactive notebooks are also degraded.

  3. identified Oct 20, 2025, 09:12 PM UTC

    Services are recovering from AWS. Currently, we have re-enabled clustering operations for AWS US East 1 region. That includes scaling, suspend/resume, and cluster creation. While the services recover, customers may continue to see intermittent connectivity issues trying to reach the DML/DDL endpoints.

  4. resolved Oct 21, 2025, 01:11 AM UTC

    AWS has restored all services

Read the full incident report →

Minor April 22, 2025 Databases not reachable from SQL editor 29m Cluster Management, AWS Clusters

Started Apr 22, 2025, 09:38 AM UTC· resolved Apr 22, 2025, 10:07 AM UTC

  1. investigating Apr 22, 2025, 09:38 AM UTC

    Databases not reachable from SQL editor inside the Portal and there is loss of customer monitoring. We are investigating the issue

  2. resolved Apr 22, 2025, 10:07 AM UTC

    Issue has been Resolved

Read the full incident report →

Minor February 13, 2025 AWS outage in Stockholm region causing connectivity issues 2h 34m AWS Clusters

Started Feb 13, 2025, 11:45 PM UTC· resolved Feb 14, 2025, 02:19 AM UTC

  1. identified Feb 13, 2025, 11:45 PM UTC

    https://health.aws.amazon.com/health/status See the above update from AWS. An ongoing outage in Stockholm region is causing connectivity and latency issues. We are actively monitoring the incident and will update back with any changes.

  2. identified Feb 14, 2025, 12:05 AM UTC

    Scaling operations are temporarily suspended due to the ongoing connectivity issues with AWS Stockholm

  3. resolved Feb 14, 2025, 02:19 AM UTC

    Issue has been resolved

Read the full incident report →