- Detected by Pingoru
- May 16, 2026, 04:14 PM UTC
- Resolved
- May 16, 2026, 04:40 PM UTC
- Duration
- 26m
Affected: ViiBE
Timeline · 4 updates
-
investigating May 16, 2026, 04:14 PM UTC
We are currently investigating this issue.
-
identified May 16, 2026, 04:37 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved May 16, 2026, 04:40 PM UTC
This incident has been resolved.
-
postmortem May 16, 2026, 04:43 PM UTC
During a routine Kubernetes cluster upgrade activity, a critical workload dependency impacting RabbitMQ availability failed to initialize successfully. Investigation determined the issue was caused by the removal of an upstream container image from Docker Hub, preventing the cluster from pulling the required image during workload startup. The issue was identified quickly, and service was restored by updating the workload configuration to reference an alternate trusted image source containing the same image artifact. Total impact duration was minimal, and no data loss occurred. This incident highlighted a broader software supply chain dependency risk associated with externally hosted container images. As a result, we are reviewing additional safeguards around image provenance, availability, and internal artifact mirroring to further reduce exposure to upstream registry changes.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 03:01 AM UTC
- Resolved
- Apr 20, 2026, 04:43 AM UTC
- Duration
- 1h 42m
Affected: iOSAndroid
Timeline · 2 updates
-
identified Apr 20, 2026, 03:01 AM UTC
We are aware of an issue causing MobileConnect devices to register with an incorrect suffix, and we have escalated it with our partners. In the meantime, for any call queue users utilizing MobileConnect, the “m” device must be added to the queue to ensure they can receive queue calls until the issue is resolved.
-
resolved Apr 20, 2026, 04:43 AM UTC
The incident has been resolved. If you experience any issues receiving calls on the MobileConnect app, please log out of the app and then log back in.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 02:51 PM UTC
- Resolved
- Apr 08, 2026, 02:51 PM UTC
- Duration
- —
Affected: Manager PortalNJ2 Core Server
Timeline · 1 update
-
resolved Apr 08, 2026, 02:51 PM UTC
The Core2-NJ portal became unavailable due to an invalid Apache certificate. The certificate was promptly removed, and service was restored within minutes.
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 08:12 PM UTC
- Resolved
- Dec 02, 2025, 08:12 PM UTC
- Duration
- —
Affected: FL Core Server
Timeline · 1 update
-
resolved Dec 02, 2025, 08:12 PM UTC
At approximately 2:46 PM EST, the core1-TPA server experienced a crash but recovered quickly and is now fully operational. Any calls handled by this server at the time of the crash would have failed.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 03:05 PM UTC
- Resolved
- Nov 21, 2025, 04:03 PM UTC
- Duration
- 58m
Affected: iOSAndroidWindowsMacOS
Timeline · 4 updates
-
investigating Nov 21, 2025, 03:05 PM UTC
We are aware of an issue affecting new registrations and outbound calls for Mobile Connect users. Our engineers are actively working to resolve it.
-
identified Nov 21, 2025, 03:26 PM UTC
We discovered an issue in the Mobile Connect middleware update deployed last night. To prevent any disruption to your service, we are rolling back to the last known stable version. Our team is actively monitoring the process and will share updates as soon as they are available.
-
monitoring Nov 21, 2025, 03:37 PM UTC
The rollback has been completed and registrations for mobile connect are starting to show as valid. We are monitoring progress. Please open and close the mobile connect application if you experience an issue to force re-registration.
-
resolved Nov 21, 2025, 04:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 10, 2025, 09:02 PM UTC
- Resolved
- Nov 11, 2025, 12:38 AM UTC
- Duration
- 3h 35m
Affected: NJ2 Core ServerLV Core Server
Timeline · 3 updates
-
investigating Nov 10, 2025, 09:02 PM UTC
At about 3:40 pm est our NJ and LV core crashed for a unknown reason, and we dropped about 1k live calls. The server auto recovered and is operational again. We are currently investigating the cause for this crash and will take necessary corrective action.
-
resolved Nov 11, 2025, 12:38 AM UTC
This incident has been resolved.
-
postmortem Nov 11, 2025, 12:39 AM UTC
The crash condition observed has been identified as a bug by NetSapiens related to v44. They have tagged it with Jira NMS-3558 in which a rare condition causes the sipbx service to crash. We are actively working with the vendor to implement a patch as soon as one is available.
Read the full incident report →
- Detected by Pingoru
- Oct 13, 2025, 03:29 PM UTC
- Resolved
- Oct 13, 2025, 03:37 PM UTC
- Duration
- 8m
Affected: Manager Portal
Timeline · 2 updates
-
investigating Oct 13, 2025, 03:29 PM UTC
We are currently investigating the issue and working to restore service
-
resolved Oct 13, 2025, 03:37 PM UTC
Portal service should be restored at this time.
Read the full incident report →
- Detected by Pingoru
- Sep 29, 2025, 08:14 PM UTC
- Resolved
- Sep 29, 2025, 08:29 PM UTC
- Duration
- 15m
Affected: Manager PortalNJ2 Core Server
Timeline · 3 updates
-
investigating Sep 29, 2025, 08:14 PM UTC
We are currently investigating reports of portal degradation, or slowness.
-
monitoring Sep 29, 2025, 08:18 PM UTC
We have identified a load spike at 4PM, we have it contained, and we are monitoring system health.
-
resolved Sep 29, 2025, 08:29 PM UTC
We are currently investigating the source of the spike at 4PM. At this time, we are monitoring all systems. Services are restored, and no further impact is expected.
Read the full incident report →
Notice September 27, 2025 - Detected by Pingoru
- Sep 27, 2025, 11:46 AM UTC
- Resolved
- Sep 27, 2025, 05:30 PM UTC
- Duration
- 5h 44m
Affected: NJ2 Core Server
Timeline · 7 updates
-
investigating Sep 27, 2025, 11:46 AM UTC
We are currently investing a portal outage occurring with our NJ server.
-
identified Sep 27, 2025, 11:51 AM UTC
Our NJ Data Center is experiencing an outage. We are following up with the data center on status and an ETR.
-
identified Sep 27, 2025, 12:30 PM UTC
Our rack in the data center is experiencing a power outage and we are being told that worst case scenario on restoration is 1PM EST. We are diverting portal traffic to Florida and will provide the next update at 1PM or sooner if we receive word from the DC that power has been restored.
-
identified Sep 27, 2025, 12:51 PM UTC
Portal traffic has been fully diverted to Florida and the portal should be available now. Further updates on this incident will be provided by 1PM or sooner.
-
identified Sep 27, 2025, 03:51 PM UTC
Our engineers are still working on restoring service and have confirmed that the portal, web phone, and SIP trunks should be operational at this time. They are still seeing Mobile Connect down and are working to restore that as soon as possible. Further updates regarding Mobile Connect will be posted as soon as they become available.
-
monitoring Sep 27, 2025, 04:27 PM UTC
All services have been restored. If you are still having issues with the web phone, please refresh the page or log out and back in. Complete RCA will be forthcoming within 5-7 business days.
-
resolved Sep 27, 2025, 05:30 PM UTC
all services have been restore
Read the full incident report →
Notice September 18, 2025 - Detected by Pingoru
- Sep 18, 2025, 05:05 PM UTC
- Resolved
- Sep 18, 2025, 07:50 PM UTC
- Duration
- 2h 44m
Affected: Manager PortalNew Jersey Data Center
Timeline · 7 updates
-
investigating Sep 18, 2025, 05:05 PM UTC
We are currently observing a degradation of portal service we are actively investigating and working on a solution
-
investigating Sep 18, 2025, 05:23 PM UTC
We are actively pursuing the cause of the incident and have engaged our engineering partners. We are actively working to stabilize the portal, and the NJ core. updates to follow as we continue investigation.
-
investigating Sep 18, 2025, 05:42 PM UTC
We are working on redirecting traffic to improve service
-
investigating Sep 18, 2025, 05:48 PM UTC
We are seeing the system recovering and performance should be improving
-
monitoring Sep 18, 2025, 05:54 PM UTC
System performance should be improved we we are continuing to monitor
-
monitoring Sep 18, 2025, 06:50 PM UTC
We are still investigating the cause of the incident. Service should be restored at this time
-
resolved Sep 18, 2025, 07:50 PM UTC
We are continuing to investigate the cause of the issue and continuing to monitor portal performance. We will be publishing RCA once we have completed our investigation
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 04:23 PM UTC
- Resolved
- Aug 19, 2025, 04:52 PM UTC
- Duration
- 28m
Affected: FL2 Core ServerNJ2 Core Server
Timeline · 4 updates
-
investigating Aug 19, 2025, 04:23 PM UTC
We are currently experiencing an issue effecting SBUS queueing relating to both NJ and FL cores. Our team is actively working to resolve this issue. We are engaging with our Platform Engineering team to diagnose. We will give more informed updates as information becomes available. Impact: Customers may experience delays with CDR's, VM's, Email issues, and possible QOS issues if GEO-Calling is present.
-
identified Aug 19, 2025, 04:37 PM UTC
Team, We have identified the structural issue, and after testing, the VM function is working as intended. Please re-test the VM functionality and update your tickets as needed.
-
resolved Aug 19, 2025, 04:52 PM UTC
Good afternoon Everyone, After Platform Engineering implemented structural solutions, this issue has been resolved. Please notify all customers impacted, and we will post a more in-depth Post-Modem to the status page.
-
postmortem Aug 29, 2025, 04:22 PM UTC
Our engineering team identified a configuration error in the dial translation for the Cloud PBX voicemail feature, which prevented calls from being routed to the correct location. The issue was quickly corrected, and additional safeguards are being implemented to prevent this from occurring in the future. During this time, regular SBUS queueing also occurred and quickly subsided, though no correlation between the two issues has been determined.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2025, 02:21 PM UTC
- Resolved
- Aug 14, 2025, 12:17 PM UTC
- Duration
- 21h 56m
Affected: Manager Portal
Timeline · 4 updates
-
investigating Aug 13, 2025, 02:21 PM UTC
Our zeus portal is currently unresponsive, we are currently investigating and re-routing
-
investigating Aug 13, 2025, 02:33 PM UTC
Update: We have re-routed traffic to NJ to restore services to the Zeus portal Internal Reference: Jira Ticket: KIT-47 Next Update: We are actively investigating the cause of the issue and have implemented a temporary solution
-
monitoring Aug 13, 2025, 02:44 PM UTC
Update: We have re-routed traffic to NJ to restore services to the Zeus portal Internal Reference: Jira Ticket: KIT-47 Next Update: We are continuing to investigate and will provide a RCA when we have completed our investigation
-
resolved Aug 14, 2025, 12:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2025, 07:04 PM UTC
- Resolved
- Aug 06, 2025, 07:40 PM UTC
- Duration
- 36m
Affected: FL2 Core Server
Timeline · 4 updates
-
investigating Aug 06, 2025, 07:04 PM UTC
We have noticed connectivity micro cut in Florida and it has recovered. We are still monitoring.
-
monitoring Aug 06, 2025, 07:06 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Aug 06, 2025, 07:08 PM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 06, 2025, 07:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2025, 06:04 PM UTC
- Resolved
- Aug 05, 2025, 12:35 AM UTC
- Duration
- 6h 30m
Affected: Florida Data Center
Timeline · 3 updates
-
investigating Aug 04, 2025, 06:04 PM UTC
We are currently investigating an issue affecting the Apollo Florida Lumen circuit. Updates to follow.
-
monitoring Aug 04, 2025, 06:18 PM UTC
The Lumen circuit has stabilized, and traffic has returned to the Florida datacenter. We will continue to monitor the circuit and provide updates as needed.
-
resolved Aug 05, 2025, 12:35 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2025, 04:53 PM UTC
- Resolved
- Jul 24, 2025, 05:09 PM UTC
- Duration
- 15m
Affected: FL2 Core Server
Timeline · 2 updates
-
investigating Jul 24, 2025, 04:53 PM UTC
We have identified an issue with Florida server. The engineers are actively investigating at the moments. More updates will follow.
-
resolved Jul 24, 2025, 05:09 PM UTC
A power issue affected the Core2-FL server but has since been resolved. Traffic automatically failed over to the Las Vegas core shortly after the outage occurred. Service has now been fully restored on Core2-FL. A detailed postmortem will be provided at a later time.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2025, 08:49 PM UTC
- Resolved
- Jul 24, 2025, 06:47 PM UTC
- Duration
- 1d 21h
Affected: FL2 Core Server
Timeline · 7 updates
-
identified Jul 22, 2025, 08:49 PM UTC
Devices registered to the core2-fl Apollo core will not capture recordings, unless the happens to be a GEO call. We have escalated the issue with Netsapiens and will provide an update soon.
-
identified Jul 22, 2025, 11:35 PM UTC
We will be implementing changes on our recording servers based on recommendations from NetSapiens. Further updates will be provided once the changes have been applied and tested.
-
monitoring Jul 23, 2025, 01:21 AM UTC
We’ve implemented configuration changes based on NetSapiens’ recommendations and are actively monitoring the system to assess their impact.
-
monitoring Jul 23, 2025, 01:28 PM UTC
We are seeing calls successfully recording on Core2-FL. We will continue to monitor and provide updates throughout the day.
-
monitoring Jul 23, 2025, 07:04 PM UTC
We are seeing significant improvements and will continue to monitor the issue. Updates to follow.
-
monitoring Jul 24, 2025, 02:40 PM UTC
We are continuing to see improvements in call recording conversion speed and reliability. Updates to follow.
-
resolved Jul 24, 2025, 06:47 PM UTC
The issue has been resolved. Calls on Core2-FL are now being recorded reliably and within standard timing expectations.
Read the full incident report →
- Detected by Pingoru
- Jul 22, 2025, 05:52 PM UTC
- Resolved
- Jul 22, 2025, 08:46 PM UTC
- Duration
- 2h 54m
Timeline · 4 updates
-
investigating Jul 22, 2025, 05:52 PM UTC
Our engineers are currently working on an issue we are experiencing with unassigned numbers hosted in Bandwidth. Updates to follow.
-
monitoring Jul 22, 2025, 06:24 PM UTC
We are implementing a change at the carrier level that should resolve the issues we are seeing with unassigned numbers in Bandwidth. Updates to follow.
-
monitoring Jul 22, 2025, 07:22 PM UTC
We are continuing to monitor the impact of the recent changes. Updates to follow.
-
resolved Jul 22, 2025, 08:46 PM UTC
Bandwidth implemented changes to our trunk to reduce forced retries for inactive or disabled numbers. We expect to see continued improvements moving forward.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2025, 03:21 PM UTC
- Resolved
- Jul 23, 2025, 01:25 AM UTC
- Duration
- 1d 10h
Affected: LV Recording Server
Timeline · 2 updates
-
investigating Jul 21, 2025, 03:21 PM UTC
Following the maintenance performed on Friday night, we observed significant improvement in the performance of recording-LV. However, we’ve recently identified that the service has begun exhibiting intermittent issues again. This will mostly impact calls processed in core2-FL & LV. Our engineering team is actively investigating the root cause with the highest priority to restore full stability as quickly as possible. We appreciate your patience and will continue to provide updates as we learn more.
-
resolved Jul 23, 2025, 01:25 AM UTC
This issue is related to the ongoing Florida Recording incident. We are closing this incident, and all updates will be provided under the active incident record.
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2025, 03:06 PM UTC
- Resolved
- Jul 14, 2025, 06:09 PM UTC
- Duration
- 3h 3m
Affected: Manager PortalNJ2 Core ServerLV Core Server
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Jul 12, 2025, 12:24 PM UTC
- Resolved
- Jul 13, 2025, 01:24 AM UTC
- Duration
- 13h
Affected: NJ2 Core ServerRecording NJ
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 03:37 PM UTC
- Resolved
- Jun 30, 2025, 01:25 PM UTC
- Duration
- 2d 21h
Affected: Recording FL
Timeline · 6 updates
-
investigating Jun 27, 2025, 03:37 PM UTC
Viirtue engineers will be performing an emergency maintenance on the Florida Recording server to prevent a possible issue. Some recordings may be unavailable or missing during this short window.
-
investigating Jun 27, 2025, 05:31 PM UTC
Our engineers are actively working to restore full functionality to the recording server. We’ll share further updates as progress is made.
-
investigating Jun 27, 2025, 06:52 PM UTC
The issue affecting the recording server has been identified. Our team is now implementing the necessary fixes to restore normal operation.
-
investigating Jun 27, 2025, 08:50 PM UTC
Our team has made meaningful headway in the investigation and continues to work through targeted areas of the system. We’ll provide further updates as we progress through the next stages.
-
investigating Jun 27, 2025, 10:13 PM UTC
The recording server issue has been resolved and functionality has been restored. We appreciate your patience while our team worked through the incident.
-
resolved Jun 30, 2025, 01:25 PM UTC
This incident was resolved on Friday. Correcting statuspage.
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2025, 07:19 PM UTC
- Resolved
- Jun 20, 2025, 09:51 PM UTC
- Duration
- 2h 31m
Affected: Florida Data CenterFL2 Core Server
Timeline · 5 updates
-
identified Jun 20, 2025, 07:19 PM UTC
We have identified a Lumen outage in Southern Florida that is causing network connectivity issues in our Florida datacenter. Updates to follow.
-
identified Jun 20, 2025, 07:22 PM UTC
Due to the minor packet loss in the Florida datacenter, we will be 503'ing the core2-fl server and moving traffic to our Las Vegas core.
-
monitoring Jun 20, 2025, 08:03 PM UTC
Our monitoring tools indicate that the packet loss has subsided. However, the 503 will remain in effect until we receive confirmation from Lumen that the issue has been fully resolved.
-
monitoring Jun 20, 2025, 09:12 PM UTC
The network congestion has been reported resolved by lumen, our team will reroute traffic back to this data center shortly. Lumen Ticket: 2025-06-20 21:05:31 GMT - The Lumen NOC has confirmed that backbone links are progressively restoring as fiber repairs are completed. Key transport paths have recovered, alleviating congestion. Services have stabilized as of 20:30 GMT. A final update will follow shortly. 2025-06-20 20:52:52 GMT - Multiple unrelated fiber incidents are currently affecting Florida markets, resulting in significant congestion across several areas. As restoration efforts progress in each location, congestion levels are beginning to ease. The Lumen Network Operations Center (NOC) will continue to monitor the situation closely to ensure stability throughout the repair process.
-
resolved Jun 20, 2025, 09:51 PM UTC
The 503 has been removed from the Florida core. Service has been fully restored to the Florida datacenter.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 03:34 PM UTC
- Resolved
- Jun 18, 2025, 02:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 18, 2025, 03:34 PM UTC
At approximately 10:13 AM EST on June 18, our core system in New Jersey experienced an unexpected crash. Our platform’s self-healing mechanisms immediately detected the issue and automatically restored service with no sustained downtime. Our engineering team is actively investigating the root cause in collaboration with our vendor. While services remain stable, we are continuing to monitor the system closely to ensure ongoing reliability.
Read the full incident report →
- Detected by Pingoru
- May 28, 2025, 01:54 PM UTC
- Resolved
- May 28, 2025, 07:22 PM UTC
- Duration
- 5h 28m
Affected: FL SIP Trunk Cluster Core
Timeline · 2 updates
-
investigating May 28, 2025, 01:54 PM UTC
The Class 4 SIP trunk core in Florida is unavailable at the moment. We are working to restore service there.
-
resolved May 28, 2025, 07:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 13, 2025, 04:24 PM UTC
- Resolved
- May 13, 2025, 07:40 PM UTC
- Duration
- 3h 16m
Affected: FL2 Core Server
Timeline · 4 updates
-
investigating May 13, 2025, 04:23 PM UTC
We are currently investigating this issue.
-
investigating May 13, 2025, 04:24 PM UTC
We noticed a possible issue in the Florida datacenter and we’re working to remediate the issue. This has cleared without service impact.
-
monitoring May 13, 2025, 07:32 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 13, 2025, 07:40 PM UTC
This incident has been resolved.
Read the full incident report →
