- Detected by Pingoru
- Sep 29, 2026, 08:26 AM UTC
- Resolved
- Sep 29, 2026, 11:39 AM UTC
- Duration
- 3h 12m
Affected: Voice (Emergency Services (e911))
Timeline · 2 updates
-
investigating Sep 29, 2026, 08:26 AM UTC
_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 5942 - Puerto Rico 9-1-1 Service Governing Board, PR _Impact of the issue:_ An issue potentially impacting emergency services to the PSAPs listed above has been identified. Our emergency service provider has gathered to investigate. Next update in one hour. _We’ll continue providing updates regularly and as soon as they become available._
-
resolved Sep 29, 2026, 11:39 AM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Sep 28, 2026, 08:09 PM UTC
- Resolved
- Sep 29, 2026, 02:22 PM UTC
- Duration
- 18h 13m
Affected: Voice (Inbound Calls)Voice (Outbound Calls)
Timeline · 2 updates
-
identified Sep 28, 2026, 08:09 PM UTC
One of our major Canada carriers is currently reporting incoming and outgoing issues within the Ontario/Quebec/Atlantic/Western Regions. We are currently monitoring and will provide any relevant updates as they come.
-
resolved Sep 29, 2026, 02:22 PM UTC
Our carrier has advised this situation is fully resolved. Please contact customer support if you continue to experience any issue.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 02:27 PM UTC
- Resolved
- Sep 25, 2026, 06:22 PM UTC
- Duration
- 3h 55m
Affected: Voice (Inbound Calls)Voice (Outbound Calls)
Timeline · 5 updates
-
investigating Sep 25, 2026, 02:27 PM UTC
We are aware of an issue affecting numbers from the Ontario area from receiving incoming calls. We are already in contact with our carrier to get more details and resolve this issue as soon as possible. We apologize for any inconvenience this may cause.
-
investigating Sep 25, 2026, 03:17 PM UTC
Our carrier is now reporting the issue is also affecting outgoing calls for the regions of Ontario and Quebec. We are following this issue closely and will provide updates as soon as they become available.
-
identified Sep 25, 2026, 03:44 PM UTC
We have made a change to route outgoing calls to a backup provider to improve connectivity. We continue to work on this issue.
-
identified Sep 25, 2026, 03:50 PM UTC
Our carrier is reporting that service for both inbound and outbound calls has been restored. You should observe calls connecting now. We are monitoring closely.
-
resolved Sep 25, 2026, 06:22 PM UTC
At this time, we can confirm all issues have been resolved. Incoming and outgoing calls are operating normally. Please contact support if you continue to experience any issue with your calls.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 03:53 PM UTC
- Resolved
- Sep 21, 2026, 06:14 PM UTC
- Duration
- 2h 21m
Affected: Main Website (Customer Portal)
Timeline · 2 updates
-
investigating Sep 21, 2026, 03:53 PM UTC
We are investigating a connectivity issue with the Customer Portal. This issue does not affect calls, SMS, fax or any other active service functionality. Our team is working diligently to resolve this situation as soon as possible. We apologize for any inconvenience this may cause.
-
resolved Sep 21, 2026, 06:14 PM UTC
This incident has been resolved.
Read the full incident report →
Notice September 19, 2026 - Detected by Pingoru
- Sep 19, 2026, 04:30 PM UTC
- Resolved
- Sep 25, 2026, 03:53 PM UTC
- Duration
- 5d 23h
Affected: VoIP.ms Platform (REST API)Reseller Interface (White-label Portal (v1.0))Reseller Interface (White-label Portal (v2.0))Reseller Interface (Hostname (HTTP/HTTPS))
Timeline · 4 updates
-
investigating Sep 19, 2026, 04:30 PM UTC
We have received reports of delays in API response times. Our team is aware of the issue and is actively investigating the situation and working to resolve it as quickly as possible. We appreciate your patience and understanding while we work to restore normal performance.
-
identified Sep 24, 2026, 12:34 AM UTC
As part of our ongoing API maintenance, the service may experience brief, intermittent disruptions during a short maintenance window. Thank you for your understanding, and we apologize for any inconvenience this may cause.
-
monitoring Sep 25, 2026, 03:49 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Sep 25, 2026, 03:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 10, 2026, 07:44 PM UTC
- Resolved
- Sep 10, 2026, 08:24 PM UTC
- Duration
- 40m
Affected: Point of Presence: United States (New York 2, NY)Point of Presence: United States (New York 3, NY)
Timeline · 2 updates
-
investigating Sep 10, 2026, 07:44 PM UTC
Our New York -2 and New York-3 servers are currently unreachable. Our team has engaged the data center to learn more about this issue and we will post updates as they come.
-
resolved Sep 10, 2026, 08:24 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2026, 02:48 PM UTC
- Resolved
- Aug 25, 2026, 07:40 PM UTC
- Duration
- 4d 4h
Affected: Voice (Inbound Calls)
Timeline · 3 updates
-
identified Aug 21, 2026, 02:48 PM UTC
We are aware of an issue preventing incoming calls from Bell Canada and Roger's network from connecting with some Sudbury region numbers. We are working with our carrier to follow the issue and provide updates as soon as possible. We apologize for any inconvenience this may cause.
-
identified Aug 24, 2026, 03:40 PM UTC
Our carrier is still working in resolving this issue with the involved network providers. At this time, there is no ETA for resolution, however, we'll continue monitoring the situation closely to provide updates as they come.
-
resolved Aug 25, 2026, 07:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2026, 12:49 AM UTC
- Resolved
- Aug 20, 2026, 04:23 PM UTC
- Duration
- 2d 15h
Affected: VoIP.ms Platform (Call Detail Records)Point of Presence: International (Sydney 1, AU)
Timeline · 2 updates
-
investigating Aug 18, 2026, 12:49 AM UTC
We are currently experiencing an issue with our SYDNEY-1 CDR causing it to have a delay in the response time and to reflect new calls. Our team is working to repair this as soon as possible. We apologize for any inconvenience this may cause.
-
resolved Aug 20, 2026, 04:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2026, 10:04 PM UTC
- Resolved
- Aug 12, 2026, 10:40 PM UTC
- Duration
- 36m
Affected: Point of Presence: United States (New York 2, NY)Point of Presence: United States (New York 3, NY)
Timeline · 2 updates
-
investigating Aug 12, 2026, 10:04 PM UTC
Our New York -2 and New York-3 servers are currently unreachable for some internet network paths. Our team has engaged the data center to learn more about this issue and we will post updates as they come.
-
resolved Aug 12, 2026, 10:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2026, 09:07 PM UTC
- Resolved
- Aug 12, 2026, 10:40 PM UTC
- Duration
- 1h 33m
Affected: Main Website (Customer Portal)VoIP.ms Platform (Call Detail Records)
Timeline · 2 updates
-
investigating Aug 12, 2026, 09:07 PM UTC
We are investigating an issue with the Customer Portal. This issue does not affect calls.
-
resolved Aug 12, 2026, 10:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 06:28 PM UTC
- Resolved
- Aug 05, 2026, 07:54 PM UTC
- Duration
- 1h 25m
Affected: Voice (Inbound Calls)
Timeline · 2 updates
-
investigating Aug 05, 2026, 06:28 PM UTC
Our upstream carrier is currently experiencing an outage affecting incoming calls into our Sudbudy, ON DIDs. We are in close contact with their team to post updates as soon as possible. We apologize for any inconvenience this may cause.
-
resolved Aug 05, 2026, 07:54 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 07:10 PM UTC
- Resolved
- Jul 27, 2026, 09:21 PM UTC
- Duration
- 2h 10m
Affected: Main Website (Customer Portal)
Timeline · 2 updates
-
investigating Jul 27, 2026, 07:10 PM UTC
We are investigating an issue with the Customer Portal accessibility. This issue does not affect calls, SMS, fax or any other active service functionality. Our team is working diligently to resolve this situation as soon as possible. We apologize for any inconvenience this may cause.
-
resolved Jul 27, 2026, 09:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 08:10 PM UTC
- Resolved
- Jul 07, 2026, 08:21 PM UTC
- Duration
- 11m
Affected: Point of Presence: Canada (Montreal 10, QC)
Timeline · 2 updates
-
investigating Jul 07, 2026, 08:10 PM UTC
We are currently investigating this incident a reroute has been set in place.
-
resolved Jul 07, 2026, 08:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 02:31 PM UTC
- Resolved
- Jul 07, 2026, 06:48 PM UTC
- Duration
- 4h 16m
Affected: Point of Presence: Canada (Montreal 01, QC)Point of Presence: Canada (Montreal 02, QC)Point of Presence: Canada (Montreal 03, QC)Point of Presence: Canada (Montreal 04, QC)Point of Presence: Canada (Montreal 05, QC)Point of Presence: Canada (Montreal 06, QC)Point of Presence: Canada (Montreal 07, QC)Point of Presence: Canada (Montreal 08, QC)Point of Presence: Canada (Montreal 09, QC)Point of Presence: Canada (Montreal 10, QC)
Timeline · 5 updates
-
investigating Jul 07, 2026, 02:31 PM UTC
We are currently aware of a network issue affecting the quality of the calls placed from our Montreal Servers. You may experience issues like dropped calls, choppy voices, silence, busy tone, calls won’t connect, high latency or intermittent connectivity with the server. We reached our provider to learn more about this issue and push for a solution. We’ll provide more updates as soon as they are available.
-
identified Jul 07, 2026, 02:40 PM UTC
At this time, we observe this issue affecting all Montreal Servers. We are continuing to work on a fix for this incident.
-
identified Jul 07, 2026, 02:51 PM UTC
We have rerouted traffic on our servers to ensure calls can continue connecting while we work to fully resolve the issue.
-
resolved Jul 07, 2026, 06:48 PM UTC
This incident has been resolved.
-
resolved Jul 07, 2026, 06:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2026, 09:55 PM UTC
- Resolved
- Jul 03, 2026, 10:40 PM UTC
- Duration
- 44m
Affected: Point of Presence: United States (Tampa 1, FL)
Timeline · 2 updates
-
investigating Jul 03, 2026, 09:55 PM UTC
Our Tampa1 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.
-
resolved Jul 03, 2026, 10:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 03:50 PM UTC
- Resolved
- Jun 05, 2026, 03:50 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 05, 2026, 03:50 PM UTC
Type: Incident Duration: 1 hour and 3 minutes Affected Components: Tampa 2, FL, Tampa 1, FL Jun 5, 15:50:00 GMT+0 - Investigating - 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. Jun 5, 16:52:30 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 02:07 AM UTC
- Resolved
- Jun 04, 2026, 01:23 PM UTC
- Duration
- 11h 15m
Affected: VoIP.ms Platform (Call Detail Records)Point of Presence: United States (San Jose 1, CA)Point of Presence: United States (San Jose 2, CA)
Timeline · 2 updates
-
investigating Jun 04, 2026, 02:07 AM UTC
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.
-
resolved Jun 04, 2026, 01:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 05:48 PM UTC
- Resolved
- May 12, 2026, 06:47 PM UTC
- Duration
- 59m
Affected: Point of Presence: Canada (Toronto 03, ON)
Timeline · 2 updates
-
investigating May 12, 2026, 05:48 PM UTC
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.
-
resolved May 12, 2026, 06:47 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
resolved Apr 25, 2026, 04:28 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 06:33 PM UTC
- Resolved
- Apr 24, 2026, 06:33 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- 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
-
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.
-
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.
-
resolved Apr 21, 2026, 06:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 08:51 PM UTC
- Resolved
- Apr 13, 2026, 08:51 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Mar 24, 2026, 05:30 PM UTC
- Resolved
- Mar 24, 2026, 05:30 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Feb 06, 2026, 10:00 PM UTC
- Resolved
- Feb 06, 2026, 10:00 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Jan 29, 2026, 04:21 PM UTC
- Resolved
- Jan 29, 2026, 04:21 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 29, 2026, 04:21 PM UTC
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.
Read the full incident report →