Voximplant Outage History

Voximplant is up right now

Voximplant had 63 outages in the last 2 years totaling 299h 24m of downtime — averaging 2.6 incidents per month.

There were 63 Voximplant outages since October 30, 2025 totaling 299h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.voximplant.com

Major March 23, 2026

Very slow platform response or it returns a 502 Bad Gateway

Detected by Pingoru
Mar 23, 2026, 11:00 AM UTC
Resolved
Mar 23, 2026, 11:55 AM UTC
Duration
55m
Affected: Control panelControl panelControl panelControl panelControl panel
Timeline · 4 updates
  1. investigating Mar 23, 2026, 12:13 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 23, 2026, 12:13 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 23, 2026, 03:36 PM UTC

    We are continuing to investigate this issue.

  4. resolved Mar 23, 2026, 03:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 17, 2026

Periodic slow loading of KIT in the US region.

Detected by Pingoru
Mar 17, 2026, 04:40 PM UTC
Resolved
Mar 17, 2026, 11:40 PM UTC
Duration
6h 59m
Affected: Workspace
Timeline · 2 updates
  1. investigating Mar 18, 2026, 06:12 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 18, 2026, 06:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 16, 2026

Slow loading of the personal account; occasional 502 errors in the RU region

Detected by Pingoru
Mar 16, 2026, 10:40 AM UTC
Resolved
Mar 16, 2026, 11:48 AM UTC
Duration
1h 8m
Affected: WebsiteWorkspaceWorkspace
Timeline · 3 updates
  1. investigating Mar 16, 2026, 11:20 AM UTC

    We are currently investigating this issue.

  2. investigating Mar 16, 2026, 11:22 AM UTC

    We are continuing to investigate this issue.

  3. resolved Mar 16, 2026, 01:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 10, 2026

HubSpot integration issues

Detected by Pingoru
Mar 10, 2026, 03:30 PM UTC
Resolved
Mar 10, 2026, 09:09 PM UTC
Duration
5h 38m
Affected: WebchatIntegrationsIntegrations
Timeline · 4 updates
  1. investigating Mar 10, 2026, 08:16 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 11, 2026, 07:21 AM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 11, 2026, 07:21 AM UTC

    We are continuing to investigate this issue.

  4. resolved Mar 12, 2026, 06:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2026

Scenario execution

Detected by Pingoru
Feb 24, 2026, 12:36 PM UTC
Resolved
Feb 26, 2026, 11:34 AM UTC
Duration
1d 22h
Affected: Call EngineCall EngineCall EngineCall EngineCall Engine
Timeline · 2 updates
  1. investigating Mar 02, 2026, 07:08 AM UTC

    Some sessions fail with the error VE - JS error: callback isn't a function or a compilable string.

  2. resolved Mar 02, 2026, 07:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 10, 2026

The problem with the calls for US region.

Detected by Pingoru
Feb 10, 2026, 11:30 PM UTC
Resolved
Feb 11, 2026, 12:42 AM UTC
Duration
1h 11m
Affected: PSTN connectivity - outboundPSTN connectivity - inboundSIP connectivity
Timeline · 3 updates
  1. investigating Feb 11, 2026, 01:06 AM UTC

    We are currently investigating this issue.

  2. investigating Feb 11, 2026, 01:07 AM UTC

    We are continuing to investigate this issue.

  3. resolved Feb 11, 2026, 01:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 21, 2026

Issue with sending A2P SMS messages.

Detected by Pingoru
Jan 21, 2026, 08:25 AM UTC
Resolved
Jan 22, 2026, 02:00 PM UTC
Duration
1d 5h
Affected: SMS
Timeline · 4 updates
  1. investigating Jan 21, 2026, 02:47 PM UTC

    Issue with sending A2P SMS messages. A2P SMS messages remain stuck with the status "Queued" RU region

  2. investigating Jan 21, 2026, 03:14 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jan 22, 2026, 06:39 AM UTC

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

  4. resolved Jan 23, 2026, 07:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 8, 2026

Some calls from Moscow numbers(Russia) may not go through

Detected by Pingoru
Jan 08, 2026, 06:30 AM UTC
Resolved
Jan 08, 2026, 02:16 PM UTC
Duration
7h 46m
Affected: PSTN connectivity - outboundPSTN outboundPSTN outbound
Timeline · 2 updates
  1. investigating Jan 08, 2026, 07:38 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 08, 2026, 02:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 4, 2026

Some statistics are not displayed in the call history (platform). Statistics in live monitoring (KIT) are not working correctly.

Detected by Pingoru
Jan 04, 2026, 06:00 AM UTC
Resolved
Jan 04, 2026, 09:38 AM UTC
Duration
3h 37m
Affected: Historical statisticsLive statisticsIntegrations
Timeline · 2 updates
  1. investigating Jan 04, 2026, 09:38 AM UTC

    We are currently investigating this issue.

  2. resolved Jan 04, 2026, 09:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 15, 2025

Incoming SMS delivery issues in the RU Region

Detected by Pingoru
Dec 15, 2025, 12:00 PM UTC
Resolved
Dec 19, 2025, 10:09 AM UTC
Duration
3d 22h
Affected: SMS
Timeline · 2 updates
  1. investigating Dec 17, 2025, 08:52 AM UTC

    We are currently investigating this issue.

  2. resolved Dec 17, 2025, 09:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 15, 2025

Some calls to\from Nizhny Novgorod numbers(Russia) may not go through or may be with one-way audio.

Detected by Pingoru
Dec 15, 2025, 06:25 AM UTC
Resolved
Dec 16, 2025, 12:50 PM UTC
Duration
1d 6h
Affected: PSTN inboundPSTN inboundPSTN connectivity - outboundPSTN connectivity - inboundPSTN outboundPSTN outbound
Timeline · 3 updates
  1. investigating Dec 15, 2025, 09:28 AM UTC

    We are currently investigating this issue.

  2. investigating Dec 15, 2025, 09:29 AM UTC

    We are continuing to investigate this issue.

  3. resolved Dec 16, 2025, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →