Viirtue experienced a minor incident on August 19, 2025 affecting FL2 Core Server and NJ2 Core Server, lasting 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.