VoIP.ms had 19 outages in the last 2 years totaling 23h 40m of downtime — averaging 0.8 incidents per month.
There were 19 VoIP.ms outages since October 20, 2025 totaling 23h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.
Our Tampa1 and Tampa 2 server are currently unreachable. Our team has engaged the data center to learn more about this issue and we will post updates as they come. In the meantime, we have routed all the traffic to a backup server.
This incident has been resolved.
We are investigating a network issue affecting the Call Detail Records report on San Jose 1 & 2 servers. You may experience delay in seeing your calls reflected. This issue does not affect the calls service or connectivity. Our team is working diligently to resolve this situation as soon as possible. We apologize for any inconvenience this may cause.
This incident has been resolved.
We are currently aware of a network issue affecting the quality of the calls for Toronto 3 Server You may experience issues like dropped calls, choppy voices, silence, busy tone, high latency or intermittent connectivity with the server. Our team is already working on a solution. We’ll provide more updates as soon as they are available.
This incident has been resolved.
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.
This incident has been resolved.
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.
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.
We have rerouted all traffic from LA3 to LA1 to restore communications. Our team continues working on the situation.
This incident has been resolved.
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.
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.
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
Type: Incident Duration: 1 day, 4 hours and 18 minutes Affected Components: New York 4, NY Jan 30, 20:39:04 GMT+0 - Resolved - This incident has been resolved. Jan 29, 16:21:19 GMT+0 - Investigating - Our New York 4 server is currently unreachable. Our team has engaged the data center to learn more about this issue and we will post updates as they come. In the meantime, we have routed all the traffic to a backup server.