Zilliz’s incident blames AWS as the cause. (hop 1, posted +1 h 44 min vs AWS’s own post)
“…e fully recovered. Starting at approximately 07:31 UTC October 20, 2025, customers in the AWS us-east-1 region may experience failures in normal cluster operations as well as accessing their clusters.…”
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
What changed
Struck in red is what Zilliz removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Service disruption
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-10-20 08:54 UTC
AddedResolved time#5
Before: not present
After: 2025-10-20 10:47 UTC
AddedAffected components#6
Before: not present
After: AWS - us-east-1, us-east-1 (Virginia)
AddedUpdateidentified#7
Before: not present
After: Starting at approximately 07:31 UTC October 20, 2025, customers in the AWS us-east-1 region may experience failures in normal cluster operations as well as accessing their clusters. We have identified the issue as an outage in AWS services and are actively working with them to mitigate the problem. We will provide another update as soon as more information is available.
AddedUpdatemonitoring#8
Before: not present
After: We are seeing recovery for affected instances in the region. We will continue to monitor the situation and provider further updates as necessary.
AddedUpdatemonitoring#9
Before: not present
After: We are continuing to monitor for any further issues.