Volt incident
5XX errors and degraded performance in API, messaging, and web platform
Volt experienced a critical incident on July 7, 2025 affecting Messaging App and Core Messaging - Outbound and 1 more component, lasting 1d 10h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 07, 2025, 06:27 PM UTC
We are currently investigating this issue.
- investigating Jul 08, 2025, 01:30 PM UTC
We are continuing to investigate this issue.
- investigating Jul 08, 2025, 02:11 PM UTC
We are continuing to investigate this issue.
- identified Jul 08, 2025, 04:14 PM UTC
The issue has been identified and a fix is being implemented.
- identified Jul 08, 2025, 06:15 PM UTC
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
- monitoring Jul 09, 2025, 12:03 AM UTC
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.
- resolved Jul 09, 2025, 05:04 AM UTC
This incident has been resolved.