Is bvoip down?

This is a retroactive incident post. Our data center vendor in Los Angeles advised us there was a partial connectivity outage in Los Angeles has been since been resolved, The issue started at 11:34pm and resolved as 3:04 Los Angeles time. Total duration of the issue was 3 hours and 40 minutes. This is what was reported to us: The incident was caused by a hardware failure in one of the network devices serving the affected servers. The faulty component was replaced, and an additional software adjustment was required during the recovery process before normal operation could be restored.

We have received several reports from accounts using calling plans on siptrunk.com / flowroute / nexvortex. This is a carrier side issue and we have escalated to our tier 3 escalation path with bcmone. We are found that specifically for siptrunk.com these settings changes provide some help Changing the gateways in use from gw1.siptrunk & gw2.siptrunk to gw4 and gw5 respectively Disabling the trunk setting Option "PBX delivers audio"

Update from siptrunk.com Thank you for this information. I have further escalated the matter to our Development and Engineering teams, and they have advised that they are currently aware of internal issues that could potentially be impacting RTP audio traffic and preventing audio packets from passing correctly. Our teams are actively investigating the issue and reviewing whether the reported symptoms align with the behavior currently being observed internally. At this time, this appears to be the most likely area of focus based on the information available. We will continue to monitor the situation closely and coordinate with the appropriate teams. As soon as we receive additional findings or confirmation regarding the root cause and resolution, I will provide you with an update promptly. Thank you for your patience and cooperation while we work through this investigation.

Latest from siptrunk.com / bcmone Thank you for your patience while we worked through this intermittent audio issue. The root cause was particularly challenging to identify because the affected calls were traversing multiple gateways, making it difficult to isolate a common factor. After gathering additional call examples from other customers and escalating the matter to our Development team, we determined that the issue originated within our network. An internal loop was causing audio traffic to consume an excessive number of ports, which resulted in the audio disruptions being reported. Our Development team implemented corrective changes at 1:30 PM EDT, and since those updates were made, customers have reported noticeable improvements in call audio quality. At this time, we ask that you continue to monitor and retest your services and let us know if you experience any further issues so we can confirm the matter has been fully resolved.

Closing incident

We had a relatively quiet morning but we have had some new reports of inbound calling issues that point back to BCM one again. We have captured some examples and sent them back to their team for review.

Update from bcmone / siptrunk.com our Development Engineering team informed me that they have implemented an additional internal change intended to alleviate the inbound and outbound audio issues that have been occurring. At this time, please retest and continue to monitor your calls to confirm that audio is now passing properly in both directions and that the issue has been resolved. If you continue to experience any problems, please provide new call examples and we will be happy to investigate further.

We received some reports of users not being able to sign in via the control portal SSO with User Not Found. We have identified and remediating this issue.

All sign-in issue seem to be resolved at this time. Switching this incident to monitoring

We are aware and are in the middle of resolving an sign-in issue in our North America control portal region

We have resolved the sign-in issue in North America via all control portal url's. Switching status of this incident to monitoring

We are following up from an issue that started earlier today that was originally thought to be all North America accounts but is now narrowed down to just accounts in our Virginia data center. We are looking into a repeat occurrence of errors with the control portal functions specific to that location. We are in the process of re-routing those functions elsewhere to work around the current errors that are being reported.

At this time all control portal functions in Virginia are operating normally. We are setting this back to monitoring

Our systems are reporting a cluster in our Los Angeles data center has stopped responding. We are investigating

We have confirmed we can not reach LACLOUD05. We have reached out to our data center vendor in Los Angeles to investigate

Our data center vendor has confirmed a power related issue. They are working on restoring.

It looks like the power issue has been corrected. We are bringing back the affected accounts online now. Will provide more updates shortly

All affected accounts based out of our Los Angeles data center are fully operational. If you need any help, feel free to contact our support team.

LACLOUD05 is reporting as unreachable again. Contacting our vendor again

This was a second power event in Los Angeles which mimics the original incident earlier. Power has been restored. We are bringing affected accounts online again.

All systems in our Los Angeles data center are fully operational at this time. Monitoritng