All Systems Operational

Uptime over the past 90 days. View historical uptime.
Messaging Operational
90 days ago
99.7 % uptime
Today
Messaging App ? Operational
90 days ago
99.22 % uptime
Today
Core Messaging - Outbound ? Operational
90 days ago
100.0 % uptime
Today
GraphQL API ? Operational
90 days ago
99.27 % uptime
Today
Core Messaging - Inbound ? Operational
90 days ago
100.0 % uptime
Today
Core Messaging - Webhooks ? Operational
90 days ago
100.0 % uptime
Today
Insights Operational
90 days ago
99.9 % uptime
Today
Insights App ? Operational
90 days ago
99.91 % uptime
Today
Insights Notifications ? Operational
90 days ago
99.79 % uptime
Today
Insights API ? Operational
90 days ago
100.0 % uptime
Today
Register Operational
90 days ago
99.65 % uptime
Today
Register App ? Operational
90 days ago
100.0 % uptime
Today
Register API ? Operational
90 days ago
99.31 % uptime
Today
Call Forwarding ? Operational
90 days ago
99.31 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jul 11, 2025

No incidents reported today.

Jul 10, 2025

No incidents reported.

Jul 9, 2025
Intermittent 5XX errors and degraded performance in API and web platform
Resolved - 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.
Jul 9, 22:38 UTC
Monitoring - A fix has been implemented and we are monitoring the results as our system fully recovers.
Jul 9, 20:15 UTC
Update - 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
Jul 9, 18:37 UTC
Update - 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.
Jul 9, 15:36 UTC
Update - 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.
Jul 9, 14:29 UTC
Identified - 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
Jul 9, 13:03 UTC
5XX errors and degraded performance in API, messaging, and web platform
Resolved - This incident has been resolved.
Jul 9, 05:04 UTC
Monitoring - 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.
Jul 9, 00:03 UTC
Update - 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
Jul 8, 18:15 UTC
Identified - The issue has been identified and a fix is being implemented.
Jul 8, 16:14 UTC
Update - We are continuing to investigate this issue.
Jul 8, 14:11 UTC
Update - We are continuing to investigate this issue.
Jul 8, 13:30 UTC
Investigating - We are currently investigating this issue.
Jul 7, 18:27 UTC
Jul 8, 2025
Jul 7, 2025
Jul 6, 2025

No incidents reported.

Jul 5, 2025

No incidents reported.

Jul 4, 2025

No incidents reported.

Jul 3, 2025

No incidents reported.

Jul 2, 2025

No incidents reported.

Jul 1, 2025

No incidents reported.

Jun 30, 2025

No incidents reported.

Jun 29, 2025

No incidents reported.

Jun 28, 2025

No incidents reported.

Jun 27, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage