">
sevanalysis

SingleStore

Infrastructure. Source: SingleStore status page.

Incidents, last 90 days
0
Median to mitigation
none resolved
Median to resolution
none resolved
p95 to resolution
none resolved
Naming an upstream provider
no incidents
With a postmortem on the status page
no incidents

Incidents per month

All recorded incidents

Operational issue - Amazon Elastic Compute Cloud (N. Virginia) unknown 2026-05-08 09:39 UTC 6d 5h

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. 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.

  2. resolved

    Issue has been resolved as notified by AWS

Excerpts are shortened. Read the full incident on SingleStore's status page.

Singlestore Portal Down unknown 2026-05-08 03:21 UTC 6d 11h

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. investigating

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

  2. identified

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

  3. monitoring

    The issue has been mitigated and we are currently monitoring.

  4. resolved

    Incident resolved

Excerpts are shortened. Read the full incident on SingleStore's status page.

Azure Issues in East US unknown 2026-04-24 17:40 UTC 2d 18h

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Multiple services – Control plane issues in East US.

  1. monitoring

    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...

  2. resolved

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

Excerpts are shortened. Read the full incident on SingleStore's status page.

GCP us-west1 region may be impacted for some customers unknown 2026-03-07 20:46 UTC 2h 51m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

  1. investigating

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

  2. identified

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

  3. resolved

    Maintenance has completed.

Excerpts are shortened. Read the full incident on SingleStore's status page.

AWS UAE multiple services disrupted unknown 2026-03-02 07:28 UTC 73d 7h

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (Bahrain): Region Availability.

Started during AWS: Multiple services (UAE): Region Availability.

  1. identified

    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

    Issue is resolved by halting deployments to region

Excerpts are shortened. Read the full incident on SingleStore's status page.

Azure VM availability impacted in East US region unknown 2026-02-03 03:03 UTC 3h 15m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

  1. 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

  2. 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.

Excerpts are shortened. Read the full incident on SingleStore's status page.

Degraded performance on AWS us-east-1 unknown 2025-10-20 08:18 UTC 16h 53m

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

  1. identified

    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

    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

    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...

  4. resolved

    AWS has restored all services

Excerpts are shortened. Read the full incident on SingleStore's status page.