Historia awarii Bvoip

July 8, 2026 11:08AM EDT Identified - 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" July 8, 2026 1:24PM EDT Identified - 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. July 8, 2026 2:37PM EDT Monitoring - 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. July 9, 2026 9:23AM EDT Resolved - Closing incident July 9, 2026 12:28PM EDT Investigating - 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. July 9, 2026 1:29PM EDT Monitoring - 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.

July 2, 2026 9:55AM EDT Identified - 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. July 2, 2026 10:57AM EDT Monitoring - All sign-in issue seem to be resolved at this time. Switching this incident to monitoring July 3, 2026 11:46AM EDT Resolved - Closing this incident

June 24, 2026 7:33AM EDT Identified - We are aware and are in the middle of resolving an sign-in issue in our North America control portal region June 24, 2026 7:56AM EDT Monitoring - We have resolved the sign-in issue in North America via all control portal url's. Switching status of this incident to monitoring June 24, 2026 1:19PM EDT 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. June 24, 2026 2:00PM EDT Monitoring - At this time all control portal functions in Virginia are operating normally. We are setting this back to monitoring June 30, 2026 11:34AM EDT Resolved - Closing incident

May 29, 2026 8:26PM EDT Investigating - Our systems are reporting a cluster in our Los Angeles data center has stopped responding. We are investigating May 29, 2026 8:32PM EDT Investigating - We have confirmed we can not reach LACLOUD05. We have reached out to our data center vendor in Los Angeles to investigate May 29, 2026 8:34PM EDT Identified - Our data center vendor has confirmed a power related issue. They are working on restoring. May 29, 2026 8:59PM EDT Identified - It looks like the power issue has been corrected. We are bringing back the affected accounts online now. Will provide more updates shortly May 29, 2026 9:26PM EDT Monitoring - 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. May 29, 2026 10:01PM EDT Investigating - LACLOUD05 is reporting as unreachable again. Contacting our vendor again May 29, 2026 10:29PM EDT Identified - 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. May 29, 2026 11:12PM EDT Monitoring - All systems in our Los Angeles data center are fully operational at this time. Monitoritng May 30, 2026 2:55PM EDT Resolved - All remains functional after last night’s issue in our Los Angeles data center. Closing incident

May 28, 2026 10:44PM EDT Monitoring - We have been alerted and confirmed that our servers in Vancouver became unreachable and then reachable again. We had an earlier incident of the same type earlier today. We are already in touch with our data center vendor and will leave this as monitoring May 30, 2026 2:54PM EDT Resolved - All remains functional in our Vancouver data center from earlier in the week. Closing this incident

May 28, 2026 10:40PM EDT Investigating - We have been alerted and confirm one of our server clusters in the Dallas data center is unreachable. We are investigating May 28, 2026 10:49PM EDT Investigating - We our in touch with our data center vendor in Dallas who is investigating locally May 28, 2026 11:08PM EDT Identified - Our Dallas data center vendor confirms that a failed device needs to be replaced. We are moving forward with equipment swap. May 29, 2026 2:41AM EDT Identified - Equipment replacement has been completed by our Dallas data center vendor. Affected accounts are starting to return back to normal. May 29, 2026 3:27AM EDT Monitoring - All systems in Dallas back to normal. Monitoring May 30, 2026 2:53PM EDT Resolved - All remains functional in our Vancouver Data center from an incident earlier in the week. Closing this incident May 30, 2026 2:54PM EDT Resolved - Apologies, meant to say Dallas here

May 28, 2026 3:26PM EDT Resolved - This is a retroactive post. We had a brief network connectivity disruption in our Vancouver data center. According to our tools the issue started at 2:54pm (New York Time) and everything was online again at 3:09pm. We were in the process of communicating with our data center vendor who confirmed there was an issue and mid call confirmed the issue was already resolved.

May 18, 2026 6:53AM EDT Investigating - We are investigating an issue affecting some customers based out of our Los Angeles Data center. Our systems indicate its specific to one cluster. May 18, 2026 7:39AM EDT Monitoring - All services in Los Angeles are back to normal. We are doing some checking with our data center vendor to review this specific cluster. Monitoring. May 18, 2026 10:56AM EDT Resolved - We have been monitoring our Los Angeles data center cluster for the last 4 hours and all is running as expected. We spoke to our Los Angeles data center vendor and they confirm that other work was being done and one of our underlying servers was accidently affected due to an oversight of a human being on their side. Now that we know this wasn't a technical malfunction, and all remains working, we are proceeding to close this incident

May 14, 2026 11:47AM EDT Scheduled - There has been a public notice about patching certain elements of systems that are in production here at 1Stream. We have reviewed and confirmed that we need to address this public notice. We are posting this as an emergency maintenance due to the short notice. We will be pushing updated to each region in off peak hours. All accounts will experience less then 2 minutes of noticeable useability of web, mobile, desktop, and traffic. We will update this maintenance post as we go through regions. May 14, 2026 11:58AM EDT Active - We are starting our off peak emergency maintenance for Australia / New Zealand / APAC region now. Again, there is a sub two minutes effect to each account where apps and call flow will be impacted. No action is required on the end user part. May 14, 2026 11:06PM EDT Active - We are about to begin our Europe region patching. Reminder, maximum 2 minutes per account where apps and call flow are affected May 15, 2026 5:46AM EDT Active - We are proceeding with North America data centers now. A reminder, up to 2 minutes per account where apps and call flow will be affected . May 15, 2026 6:49AM EDT Completed - All regions have been completed and are operating normally. Closing maintenance

May 4, 2026 3:04PM EDT Investigating - We are looking into a control portal issue specifically in North America. The other regions seem to be working as expected. Access to system management and single sign-on are affected. May 4, 2026 3:12PM EDT Resolved - Control portal back to 100% in North America. All systems are behaving properly for system management and single sign-on