Resolved after 26 minutes, affecting ViiBE, on May 16, 2026.
During a routine Kubernetes cluster upgrade activity, a critical workload dependency impacting RabbitMQ availability failed to initialize successfully. Investigation determined the issue was caused by the removal of an upstream container image from Docker Hub, preventing the cluster from pulling the required image during workload startup. The issue was identified quickly, and service was restored by updating the workload configuration to reference an alternate trusted image source containing the same image artifact. Total impact duration was minimal, and no data loss occurred. This incident highlighted a broader software supply chain dependency risk associated with externally hosted container images. As a result, we are reviewing additional safeguards around image provenance, availability, and internal artifact mirroring to further reduce exposure to upstream registry changes.
Affected components
Update timeline
- investigating May 16, 2026, 04:14 PM UTC
We are currently investigating this issue.
- identified May 16, 2026, 04:37 PM UTC
The issue has been identified and a fix is being implemented.
- resolved May 16, 2026, 04:40 PM UTC
This incident has been resolved.
- postmortem May 16, 2026, 04:43 PM UTC
During a routine Kubernetes cluster upgrade activity, a critical workload dependency impacting RabbitMQ availability failed to initialize successfully. Investigation determined the issue was caused by the removal of an upstream container image from Docker Hub, preventing the cluster from pulling the required image during workload startup. The issue was identified quickly, and service was restored by updating the workload configuration to reference an alternate trusted image source containing the same image artifact. Total impact duration was minimal, and no data loss occurred. This incident highlighted a broader software supply chain dependency risk associated with externally hosted container images. As a result, we are reviewing additional safeguards around image provenance, availability, and internal artifact mirroring to further reduce exposure to upstream registry changes.
Your product runs on more than Viirtue
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services