Voximplant Outage History

Voximplant is up right now

Pingoru has recorded 126 incidents for Voximplant: 126 in the last 12 months and 49 in the last 90 days.

Source: status.voximplant.com

126incidents recorded
126last 12 months
49last 90 days
21 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct26
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct72%
Pingoru began tracking Voximplant in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026945 of 720 (6%)
May 20261120 of 744 (3%)
June 20268104 of 720 (14%)
July 202612161 of 744 (22%)
August 20267299 of 744 (40%)
September 20269112 of 720 (16%)
October 202626427 of 593 (72%)

Incidents, newest first

Major December 2, 2025 AMD is not working in Russia 2h 11m Call Engine

Started Dec 02, 2025, 10:00 AM UTC· resolved Dec 02, 2025, 12:12 PM UTC

  1. investigating Dec 02, 2025, 11:40 AM UTC

    We are currently investigating this issue.

  2. resolved Dec 02, 2025, 12:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 28, 2025 The issue with outgoing calls in RU region 26m PSTN connectivity - outbound, PSTN outbound, PSTN outbound

Started Nov 28, 2025, 06:30 AM UTC· resolved Nov 28, 2025, 06:57 AM UTC

  1. investigating Nov 28, 2025, 07:40 AM UTC

    We are currently investigating this issue.

  2. resolved Nov 28, 2025, 07:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 26, 2025 Some outgoing calls may be failed affecting some customers in Russia 14h 5m PSTN outbound, PSTN outbound

Started Nov 26, 2025, 09:00 PM UTC· resolved Nov 27, 2025, 11:05 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor October 30, 2025 Some incoming calls to Moscow Russia numbers may not go through 31d 18h PSTN inbound, PSTN inbound, PSTN connectivity - inbound

Started Oct 30, 2025, 02:00 PM UTC· resolved Dec 01, 2025, 08:20 AM UTC

  1. investigating Dec 01, 2025, 07:48 AM UTC

    We are currently investigating this issue.

  2. resolved Dec 01, 2025, 08:38 AM UTC

    This incident has been resolved.

Read the full incident report →