Voximplant incident

HTTP requests configured in the call script using NET methods periodically do not trigger in Russia, with the error: Code: -8. Error: Resolving timed out

Voximplant experienced a major incident on May 6, 2026 affecting API and Public API and 1 more component, lasting 7h 59m. The incident has been resolved; the full update timeline is below.

Started: May 06, 2026, 02:19 AM UTC
Resolved: May 06, 2026, 10:19 AM UTC
Duration: 7h 59m
Detected by Pingoru: May 06, 2026, 02:19 AM UTC

Affected components

APIPublic APIPublic API

Update timeline

investigating May 06, 2026, 09:58 AM UTC

We are currently investigating this issue.
resolved May 06, 2026, 01:45 PM UTC

This incident has been resolved.

Looking to track Voximplant downtime and outages?

Pingoru polls Voximplant's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Voximplant reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Voximplant alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Voximplant for free

5 free monitors · No credit card required