Volt had 6 outages in the last 2 years totaling 49h 38m of downtime — averaging 0.2 incidents per month.
There were 6 Volt outages since June 25, 2025 totaling 49h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating the issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
An AWS incident affected Volt services, degrading service and reducing availability.
Volt is currently experiencing temporary delays and intermittent 5XX errors as our system fully recovers from yesterday's outage: https://status.textvolt.com/incidents/ms4sppm7n20m A fix is being implemented to mitigate the secondary effects of yesterday's outage. For more details, questions, or concerns related to this incident, you can contact our Customer Success team via chat: https://help.textvolt.com
We are continuing the process of mitigating the effects of this issue. We are temporarily load shedding access to the web platform in order to continue sending and receiving messages successfully. This is intended to be a temporary state which is resolved within the next 1-2 hours. We will continue to update as the situation progresses.
Volt has observed significant delays in core messaging webhooks related to this incident. We are continuing to work on a mitigation for this issue and will provide further updates as they become available.
We have identified that a workflow within AWS infrastructure has become stuck, which is causing the ongoing delays and intermittent 5XX errors. This issue is a secondary effect stemming from yesterday's AWS outage and appears to be related to an underlying software fault within an AWS system. Volt's Engineering team is actively working with AWS Support to resolve the stuck workflow. This issue requires AWS intervention to restore normal functionality, as it stems from their infrastructure. We will continue to provide updates as we work with AWS to resolve this issue. For more details, questions, or concerns related to this incident, you can contact our Customer Success team via chat: https://help.textvolt.com
A fix has been implemented and we are monitoring the results as our system fully recovers.
This incident has been resolved. We intend to share a full post-incident review for this incident and the related outage in the coming days.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
Volt's Engineering team is continuing to work on a fix. A contributing factor to this incident is an issue within the cloud services provider which underlies Volt's core messaging infrastructure, Amazon Web Services (AWS). Volt's Platform Engineering team is currently engaged with the AWS Engineering team as they continue to work on a fix for the issue within their system. Volt Engineering is separately investigating transitioning our core messaging infrastructure to one of our alternative cloud providers. At the moment, we do not have a specific timeline for resolution, but this continues to be our top priority for resolution. We will provide further updates as the situation progresses. For more details, questions, or concerns related to this incident, you can contact our Customer Success team via chat: https://help.textvolt.com
A fix has been implemented for the underlying bug within AWS, and Amazon has begun the process of deployment. AWS uses a global rolling deployment process where regions across the world are updated in stages. We are unable to provide a precise ETA for resolution at this time, but we expect resolution prior to start of business on Wednesday, July 9. We are continuing to engage with Amazon as this deployment process takes place, and we will provide further updates as the situation progresses.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.