Search

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

SingleStore: Major incident: Operational issue - Amazon Elastic Compute Cloud (N. Virginia)

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: outage (model (Jev), 66%)Changed Detected Source: status.singlestore.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: Operational issue - Amazon Elastic Compute Cloud (N. Virginia)
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-05-08 09:39 UTC
AddedResolved time#5
Before: not present
After: 2026-05-14 14:56 UTC
AddedAffected components#6
Before: not present
After: AWS Clusters
AddedUpdatemonitoring#7
Before: not present
After: 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.
AddedUpdateresolved#8
Before: not present
After: Issue has been resolved as notified by AWS

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Operational issue - Amazon Elastic Compute Cloud (N. Virginia) (this change)Major incident

All SingleStore changes → · SingleStore profile · Markdown · JSON