VoIP.ms Outage History

VoIP.ms is up right now

There were 7 VoIP.ms outages since February 6, 2026 totaling 10h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.voip.ms

Minor April 24, 2026

Toll Free Vanity Search and Order

Detected by Pingoru
Apr 24, 2026, 06:33 PM UTC
Resolved
Apr 25, 2026, 04:28 AM UTC
Duration
9h 55m
Affected: VoIPmsNumbers (Number Searching)Numbers (Number Ordering)
Timeline · 2 updates
  1. investigating Apr 24, 2026, 06:33 PM UTC

    We have identified an issue in our Toll Free Vanity Search and Order process. We are actively working to have it fixed. We apologize for any inconvenience this may cause.

  2. resolved Apr 25, 2026, 04:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2026

Toll Free Vanity Search and Order

Detected by Pingoru
Apr 24, 2026, 06:33 PM UTC
Resolved
Apr 24, 2026, 06:33 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 24, 2026, 06:33 PM UTC

    Type: Incident Duration: 9 hours and 55 minutes Affected Components: Number Ordering, Number Searching Apr 25, 04:28:56 GMT+0 - Resolved - This incident has been resolved. Apr 24, 18:33:29 GMT+0 - Investigating - We have identified an issue in our Toll Free Vanity Search and Order process. We are actively working to have it fixed. We apologize for any inconvenience this may cause.

Read the full incident report →

Major April 21, 2026

Los Angeles 3 Server

Detected by Pingoru
Apr 21, 2026, 05:32 PM UTC
Resolved
Apr 21, 2026, 06:00 PM UTC
Duration
28m
Affected: VoIPmsPoint of Presence: United States (Los Angeles 3, CA)
Timeline · 3 updates
  1. investigating Apr 21, 2026, 05:32 PM UTC

    We are aware of an issue currently affecting the connectivity of incoming and outgoing calls from the LA3 Server. Our team is already working on resolving this issue. We sincerely apologize for the inconvenience.

  2. identified Apr 21, 2026, 05:39 PM UTC

    We have rerouted all traffic from LA3 to LA1 to restore communications. Our team continues working on the situation.

  3. resolved Apr 21, 2026, 06:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 13, 2026

Outgoing Calls Issues from some Servers

Detected by Pingoru
Apr 13, 2026, 08:51 PM UTC
Resolved
Apr 13, 2026, 08:51 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 13, 2026, 08:51 PM UTC

    Type: Incident Duration: 9 hours and 46 minutes Affected Components: Outbound Calls Apr 13, 20:51:40 GMT+0 - Investigating - We are aware of an issue affecting outgoing calls from some servers. Our team is investigating to resolves this situation as soon as possible. We apologize for any inconvenience this may cause. Apr 13, 21:37:26 GMT+0 - Monitoring - This issue has been resolved and our team is further monitoring to make sure the services remain stable. Calls are connecting now. We will provide more details as they become available. Apr 14, 06:37:15 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor March 29, 2026

Emergency Services - PSAP Incident Notification

Detected by Pingoru
Mar 29, 2026, 05:53 PM UTC
Resolved
Mar 29, 2026, 05:53 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 29, 2026, 05:53 PM UTC

    Type: Incident Duration: 22 hours and 25 minutes Affected Components: Emergency Services (e911) Mar 29, 17:53:39 GMT+0 - Investigating - _A service disruption has been identified that potentially affects you or your end users; details can be found below._ _Geographic Area and/or PSAPs Potentially Affected:_ FCC ID 6037 - Cherokee County Department of Communications, SC _Impact of the issue:_ Calls may be failing over to PSAP’s 10-Digit 24x7 administrative line, PSAP unable to display address and/or latitude and longitude data, PSAP unable to retrieve ANI, pANI is not being delivered to the PSAP, preventing the PSAP to bid for location information. _We’ll continue providing updates regularly and as soon as they become available._ Mar 29, 17:56:27 GMT+0 - Identified - Our emergency service provider continues to investigate. Our provider's peering components have been validated to be working as designed. Calls are being delivered via the carrier's tertiary route. No additional affected PSAPs have been identified. Alternate routing is being investigated. Our provider's Incident Command will continue to request hourly updates from the circuit provider(s). The Next update will be provided when more information becomes available. Mar 30, 16:18:18 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor March 24, 2026

Emergency Services - PSAP Incident Notification INC3638883

Detected by Pingoru
Mar 24, 2026, 05:30 PM UTC
Resolved
Mar 24, 2026, 05:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 24, 2026, 05:30 PM UTC

    Type: Incident Duration: 4 hours and 39 minutes Affected Components: Emergency Services (e911) Mar 24, 17:30:59 GMT+0 - Investigating - _A service disruption has been identified that potentially affects you or your end users; details can be found below._ **_Geographic Area and/or PSAPs Potentially Affected:_** FCC ID 8220 - St. Croix 9-1-1 Call Center, VI FCC ID 8221 - St. Thomas 9-1-1 Call Center, VI **_Impact of the issue:_** An issue potentially impacting emergency services to the PSAPs listed above has been identified. _We’ll continue providing updates regularly and as soon as they become available._ Mar 24, 22:09:58 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor February 6, 2026

San Jose-2 recordings

Detected by Pingoru
Feb 06, 2026, 10:00 PM UTC
Resolved
Feb 06, 2026, 10:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 06, 2026, 10:00 PM UTC

    Type: Incident Duration: 2 days and 20 hours Affected Components: Conference Recording, San Jose 2, CA, Call Recording, Conference Transcription, Call Transcription Feb 9, 18:00:43 GMT+0 - Resolved - This incident has been resolved. Feb 6, 22:00:18 GMT+0 - Investigating - We are currently investigating an incident affecting call recordings, conference recordings and transcriptions on POP San Jose-2. Our apologies for any inconvenience you may experience as a result of this incident

Read the full incident report →

Looking to track VoIP.ms downtime and outages?

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

  • Real-time alerts when VoIP.ms reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track VoIP.ms alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring VoIP.ms for free

5 free monitors · No credit card required