Volt Outage History

Volt is up right now

Volt had 12 outages in the last 2 years totaling 54h 21m of downtime — averaging 0.5 incidents per month.

There were 12 Volt outages since July 26, 2024 totaling 54h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.textvolt.com

Minor July 6, 2026

Partial Outage - All Systems

Detected by Pingoru
Jul 06, 2026, 04:49 PM UTC
Resolved
Jul 06, 2026, 04:58 PM UTC
Duration
9m
Affected: Messaging AppInsights AppRegister AppCore Messaging - OutboundInsights NotificationsRegister APIGraphQL APIInsights APICore Messaging - InboundCall ForwardingCore Messaging - Webhooks
Timeline · 3 updates
  1. investigating Jul 06, 2026, 04:49 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 06, 2026, 04:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 06, 2026, 04:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 17, 2026

Messaging API Outage

Detected by Pingoru
Jun 17, 2026, 11:15 PM UTC
Resolved
Jun 17, 2026, 11:15 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 18, 2026, 03:26 AM UTC

    The Volt Messaging API experienced an outage between 7:15 PM EDT and 8:07 EDT. During this period, calls to the API would fail with a error of "failed to create message entity". Messages which failed in this way have not been sent. The issue was fully resolved at 8:07 PM EDT and message process has been fully restored.

Read the full incident report →

Major January 13, 2026

Core Messaging Partial Outage - Outbound & Inbound

Detected by Pingoru
Jan 13, 2026, 03:19 PM UTC
Resolved
Jan 13, 2026, 04:02 PM UTC
Duration
43m
Affected: Core Messaging - OutboundCore Messaging - Inbound
Timeline · 3 updates
  1. identified Jan 13, 2026, 03:19 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Jan 13, 2026, 03:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 13, 2026, 04:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 27, 2025

AWS Outage

Detected by Pingoru
Oct 27, 2025, 04:14 PM UTC
Resolved
Oct 20, 2025, 04:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 27, 2025, 04:14 PM UTC

    An AWS incident affected Volt services, degrading service and reducing availability.

Read the full incident report →

Minor July 9, 2025

Intermittent 5XX errors and degraded performance in API and web platform

Detected by Pingoru
Jul 09, 2025, 01:03 PM UTC
Resolved
Jul 09, 2025, 10:38 PM UTC
Duration
9h 34m
Affected: Messaging AppInsights AppGraphQL APICore Messaging - Webhooks
Timeline · 6 updates
  1. identified Jul 09, 2025, 01:03 PM UTC

    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

  2. identified Jul 09, 2025, 02:29 PM UTC

    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.

  3. identified Jul 09, 2025, 03:36 PM UTC

    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.

  4. identified Jul 09, 2025, 06:37 PM UTC

    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

  5. monitoring Jul 09, 2025, 08:15 PM UTC

    A fix has been implemented and we are monitoring the results as our system fully recovers.

  6. resolved Jul 09, 2025, 10:38 PM UTC

    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.

Read the full incident report →

Critical July 7, 2025

5XX errors and degraded performance in API, messaging, and web platform

Detected by Pingoru
Jul 07, 2025, 06:27 PM UTC
Resolved
Jul 09, 2025, 05:04 AM UTC
Duration
1d 10h
Affected: Messaging AppCore Messaging - OutboundInsights NotificationsRegister APIGraphQL APIInsights APICall ForwardingCore Messaging - Webhooks
Timeline · 7 updates
  1. investigating Jul 07, 2025, 06:27 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 08, 2025, 01:30 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 08, 2025, 02:11 PM UTC

    We are continuing to investigate this issue.

  4. identified Jul 08, 2025, 04:14 PM UTC

    The issue has been identified and a fix is being implemented.

  5. 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

  6. 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.

  7. resolved Jul 09, 2025, 05:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 25, 2025

Degraded performance on web platform

Detected by Pingoru
Jun 25, 2025, 02:23 PM UTC
Resolved
Jun 25, 2025, 05:32 PM UTC
Duration
3h 8m
Affected: Messaging App
Timeline · 3 updates
  1. investigating Jun 25, 2025, 02:23 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 25, 2025, 04:55 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 25, 2025, 05:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 25, 2025

Partial outage affecting API servers and UI

Detected by Pingoru
Jan 25, 2025, 05:11 PM UTC
Resolved
Jan 25, 2025, 07:22 PM UTC
Duration
2h 11m
Affected: Messaging AppInsights AppGraphQL API
Timeline · 5 updates
  1. investigating Jan 25, 2025, 05:11 PM UTC

    We are currently investigating this issue.

  2. identified Jan 25, 2025, 05:16 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jan 25, 2025, 05:44 PM UTC

    We are continuing to work on a fix for this issue. Outbound messages are being temporarily throttled in conjunction with this fix.

  4. monitoring Jan 25, 2025, 06:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jan 25, 2025, 07:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 19, 2024

Delayed core messaging webhooks

Detected by Pingoru
Nov 19, 2024, 02:55 PM UTC
Resolved
Nov 19, 2024, 02:55 PM UTC
Duration
—
Affected: Insights APICore Messaging - Webhooks
Timeline · 1 update
  1. resolved Nov 19, 2024, 02:55 PM UTC

    Volt observed delays in webhook processing within a subset of our messaging beginning from 2024-11-19 07:42 UTC to 2024-11-19 14:44 UTC. A fix has been implemented and we are no longer observing delays.

Read the full incident report →

Minor August 14, 2024

Observed delays in core messaging

Detected by Pingoru
Aug 14, 2024, 03:30 PM UTC
Resolved
Aug 14, 2024, 05:23 PM UTC
Duration
1h 53m
Affected: Core Messaging - Outbound
Timeline · 4 updates
  1. investigating Aug 14, 2024, 03:30 PM UTC

    A subset of customers are currently experiencing delays. We are currently investigating this issue.

  2. identified Aug 14, 2024, 03:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 14, 2024, 04:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 14, 2024, 05:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 26, 2024

Web application delays and partial unavailability

Detected by Pingoru
Jul 26, 2024, 08:28 PM UTC
Resolved
Jul 26, 2024, 08:56 PM UTC
Duration
28m
Affected: Messaging AppInsights App
Timeline · 3 updates
  1. investigating Jul 26, 2024, 08:28 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 26, 2024, 08:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 26, 2024, 08:56 PM UTC

    This incident has been resolved.

Read the full incident report →