- Detected by Pingoru
- Oct 20, 2026, 04:25 PM UTC
- Resolved
- Oct 20, 2026, 05:13 PM UTC
- Duration
- 48m
Affected: VoIP.ms Platform (Call Detail Records)
Timeline · 2 updates
-
investigating Oct 20, 2026, 04:25 PM UTC
We are aware of an issue affecting CDR updates. At this time, CDR data is not being updated as expected. Our team is actively investigating the root cause and working diligently to resolve the issue as soon as possible. Call services continue to operate normally and are not affected. Thank you for your patience and understanding.
-
resolved Oct 20, 2026, 05:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2026, 03:28 PM UTC
- Resolved
- Oct 20, 2026, 05:09 PM UTC
- Duration
- 1h 41m
Affected: Point of Presence: United States (Los Angeles 1, CA)
Timeline · 2 updates
-
investigating Oct 20, 2026, 03:28 PM UTC
A new network issue has been detected affecting the Los Angeles-1 server. To prevent further service disruption, we have rerouted the affected traffic through an alternative server. Our team is monitoring the situation and will provide further updates as needed. We apologize for the inconvenience and appreciate your patience and understanding.
-
resolved Oct 20, 2026, 05:09 PM UTC
**Incident Resolved: Los Angeles-1** We have worked closely with our provider and confirmed that the network issues have been resolved. Service has been fully restored to its normal operating state, and traffic has been returned to its original routing. We sincerely appreciate your patience and understanding throughout this incident. Thank you for your patience while we worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2026, 07:46 AM UTC
- Resolved
- Oct 20, 2026, 03:11 PM UTC
- Duration
- 7h 25m
Affected: Point of Presence: United States (Los Angeles 1, CA)
Timeline · 3 updates
-
investigating Oct 20, 2026, 07:46 AM UTC
The Los Angeles-1 server is currently unreachable. Our team is actively investigating the issue to identify the root cause and restore connectivity. In the meantime, traffic has been temporarily rerouted through an alternative server to minimize service disruption and maintain service continuity. We apologize for any inconvenience this may cause and will provide further updates as more information becomes available. Thank you for your patience and understanding.
-
identified Oct 20, 2026, 02:44 PM UTC
**Service Restoration in Progress** We have identified and resolved the underlying issue affecting the service. Over the next hour, you may experience a brief interruption in communications as we complete the necessary steps to fully restore normal service. We appreciate your patience and understanding as we finalize the recovery process. We apologize for any inconvenience this may cause and will provide further updates as needed.
-
resolved Oct 20, 2026, 03:11 PM UTC
**Incident Resolved: Service Fully Restored** The issue was caused by a problem at our provider’s facilities, which resulted in a brief service interruption. To prevent prolonged disruption, our team promptly rerouted the affected traffic. We are pleased to confirm that **all services have returned to normal operation**. We sincerely appreciate your patience and understanding while we worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Oct 18, 2026, 03:24 PM UTC
- Resolved
- Oct 18, 2026, 05:01 PM UTC
- Duration
- 1h 36m
Affected: VoIP.ms Platform (Call Detail Records)
Timeline · 2 updates
-
investigating Oct 18, 2026, 03:24 PM UTC
Call Detail Records are not being updated. We are investigating this issue.
-
resolved Oct 18, 2026, 05:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 16, 2026, 03:06 PM UTC
- Resolved
- Oct 16, 2026, 09:25 PM UTC
- Duration
- 6h 19m
Affected: Voice (Inbound Calls)Voice (Outbound Calls)
Timeline · 3 updates
-
investigating Oct 16, 2026, 03:06 PM UTC
One of our upstream carriers is currently experiencing an issue affecting outgoing and incoming calls to Toronto, ON service area. You may experience issues like silence, dropped calls or connectivity issues while making calls. We are diligently working with them in order to restore the service.
-
identified Oct 16, 2026, 03:46 PM UTC
The issue has been identified as a fiber-optic cable fault, and the teams have already been dispatched to carry out the necessary repairs.
-
resolved Oct 16, 2026, 09:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2026, 07:36 PM UTC
- Resolved
- Oct 07, 2026, 08:29 PM UTC
- Duration
- 52m
Affected: Voice (Inbound Calls)
Timeline · 3 updates
-
investigating Oct 07, 2026, 07:36 PM UTC
One of our Canadian providers is currently experiencing one-way audio for inbound calls received by Ontario, Canada DID numbers. Our provider is working on it as a High Priority. We'll provide additional updates once they're available.
-
identified Oct 07, 2026, 08:25 PM UTC
Our carrier was able to narrow down the issue to some Bell Circuits. They have rerouted traffic from their circuits until the issue is fully resolved. Calls are operating normally at this time.
-
resolved Oct 07, 2026, 08:29 PM UTC
Our provider confirmed that the issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 05:09 PM UTC
- Resolved
- Oct 06, 2026, 05:31 PM UTC
- Duration
- 22m
Affected: Main Website (Customer Portal)
Timeline · 3 updates
-
investigating Oct 06, 2026, 05:09 PM UTC
We are investigating an 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.
-
identified Oct 06, 2026, 05:17 PM UTC
Our team has identified the issue affecting the Customer Portal and is actively working on implementing a fix. We are closely monitoring the situation and will provide further updates as soon as more information becomes available. We appreciate your patience and understanding while we work to restore full functionality.
-
resolved Oct 06, 2026, 05:31 PM UTC
The issue has been resolved. Thank you for your patience and understanding while our team worked to address it. We will continue monitoring the Customer Portal to help ensure that the issue does not recur.
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 08:38 AM UTC
- Resolved
- Oct 06, 2026, 10:53 AM UTC
- Duration
- 2h 15m
Affected: Voice (Emergency Services (e911))
Timeline · 2 updates
-
investigating Oct 06, 2026, 08:38 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 Oct 06, 2026, 10:53 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 05, 2026, 07:07 PM UTC
- Resolved
- Oct 06, 2026, 07:52 PM UTC
- Duration
- 1d
Affected: Messaging (Inbound Messaging)Messaging (Outbound Messaging)Messaging (Messaging Center)Messaging (Short Message Peer-to-Peer (SMPP))
Timeline · 4 updates
-
investigating Oct 05, 2026, 07:07 PM UTC
We are aware of an issue affecting the SMS/MMS service via SIP (softphone applications) and SMPP. The messaging service is still available via email, web portal and API. Our engineering team is already working to fix this issue as soon as possible. We apologize for any inconvenience this may cause.
-
monitoring Oct 05, 2026, 09:24 PM UTC
We identified a problem with our SMS/MMS SIP service that could cause delayed or failed outbound messages and brief service disruption. We applied a fix and confirmed is working again. We are monitoring the service closely.
-
monitoring Oct 06, 2026, 06:59 PM UTC
We are scheduling emergency maintenance to apply an important update to our systems. We will post updates on this page as needed. Thank you for your patience.
-
resolved Oct 06, 2026, 07:52 PM 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 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, 04:52 PM UTC
- Duration
- 1h 2m
Affected: Point of Presence: United States (Tampa 1, FL)Point of Presence: United States (Tampa 2, FL)
Timeline · 2 updates
-
investigating Jun 05, 2026, 03:50 PM UTC
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.
-
resolved Jun 05, 2026, 04:52 PM UTC
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 →