Resolved after 3 hours 35 minutes, affecting NJ2 Core Server and LV Core Server, on November 10, 2025.
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.
Affected components
Update timeline
- 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.
Your product runs on more than Viirtue
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services