bvoip Outage History
bvoip is up right nowPingoru has recorded 13 incidents for bvoip: 13 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 5 | 45 of 744 (6%) |
| June 2026 | 1 | 148 of 720 (21%) |
| July 2026 | 3 | 195 of 744 (26%) |
| August 2026 | 2 | 35 of 744 (5%) |
| September 2026 | 0 | 11 of 720 (2%) |
| October 2026 | 2 | 41 of 557 (7%) |
Incidents, newest first
Minor October 13, 2026 VACLOUD15 Connectivity Issue - OCT 13 18h 50m Cloud UC Platform, SBC Layer (SBC Layer — DP: ASHBURN, VA)
Started Oct 13, 2026, 10:41 PM UTC· resolved Oct 14, 2026, 05:31 PM UTC
- investigating Oct 13, 2026, 10:41 PM UTC
Our systems are reporting a cluster in our Virginia data center is not reachable. We are investigating
- identified Oct 13, 2026, 10:47 PM UTC
We have found access to our cluster in Virginia VACLOUD15 is back. Services should be restoring for affected accounts on this cluster.
- monitoring Oct 13, 2026, 11:07 PM UTC
All services in our Virginia Data Center are back to normal. Switching this incident to monitoring.
Minor October 7, 2026 Call Parking Issues - Chicago / Los Angeles - Oct 7 22h 31m Cloud UC Platform, SBC Layer, SBC Layer (SBC Layer — DP: LOS ANGELES, CA), SBC Layer (SBC Layer — DP: CHICAGO, IL)
Started Oct 07, 2026, 06:01 PM UTC· resolved Oct 08, 2026, 04:32 PM UTC
- identified Oct 07, 2026, 06:01 PM UTC
We have had several reports of parked calls not being able to be un-parked from accounts based in our Chicago and Los Angeles data centers. We have identified the issue and working on remediation.
- monitoring Oct 07, 2026, 06:38 PM UTC
Looks like we have a confirmed fix in place at this time. Monitoring
Major August 31, 2026 Microsoft 365 Email / Exchange Online Outage 17h 32m Aux Services, Aux Services (Aux Services — MS Office365 Email), Aux Services (Aux Services — Support Ticketing System), Aux Services (Aux Services — Cloud SMTP Delivery Service)
Started Aug 31, 2026, 05:51 PM UTC· resolved Sep 01, 2026, 11:24 AM UTC
- identified Aug 31, 2026, 05:51 PM UTC
We are aware of a Microsoft posted outage for Exchange online. You can see this is being reported in several places. https://www.bleepingcomputer.com/news/microsoft/microsoft-exchange-online-outage-causes-email-failures-auth-issues/ 1. If you are emailing 1Stream, it is likely your messages are not reaching us for sales, support, etc. Our systems are online but email is likely not being deliveed. 2. If you use M365 for outbound email from your 1Stream account for things like alerts, voicemail-to-email, etc it is likely that those messages are not being sent.
- monitoring Sep 01, 2026, 12:45 AM UTC
We are seeing delayed email starting to pour in from approx noon eastern time today when the Microsoft 365 / Exchange Online outage started. We will continue to monitor has all Microsoft services are back to 100%.
Minor August 26, 2026 1Stream Integration Services North America - Aug 26 1d 4h IQ Integration Platform, IQ Integration Platform (IQ Integration Platform — IQ Integration Services - North America)
Started Aug 26, 2026, 11:50 AM UTC· resolved Aug 27, 2026, 04:22 PM UTC
- monitoring Aug 26, 2026, 11:50 AM UTC
We were notified by several there were experiencing login loops when trying to sign-in within the last 30 minutes. We also received some reports that certain portal pages were not responding. We have refreshed all systems and all should be working properly. You may need to refresh your browser sessions CTRL + R.
Minor July 26, 2026 LACLOUD05 Connectivity Issue 1d 2h Cloud UC Platform, SBC Layer (SBC Layer — DP: LOS ANGELES, CA)
Started Jul 26, 2026, 11:31 AM UTC· resolved Jul 27, 2026, 02:21 PM UTC
- monitoring Jul 26, 2026, 11:31 AM UTC
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.
Minor July 8, 2026 Intermittent Dead air / no audio on siptrunk.com - bcmone 5d 22h North American Voice & Messaging Carriers, North American Voice & Messaging Carriers (North American Voice & Messaging Carriers — siptrunk.com), North American Voice & Messaging Carriers (North American Voice & Messaging Carriers — nexvortex), North American Voice & Messaging Carriers (North American Voice & Messaging Carriers — flowroute)
Started Jul 08, 2026, 03:08 PM UTC· resolved Jul 14, 2026, 01:40 PM UTC
- identified Jul 08, 2026, 03:08 PM UTC
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"
- identified Jul 08, 2026, 05:24 PM UTC
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.
- monitoring Jul 08, 2026, 06:37 PM UTC
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.
- resolved Jul 09, 2026, 01:23 PM UTC
Closing incident
- investigating Jul 09, 2026, 04:28 PM UTC
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.
- monitoring Jul 09, 2026, 05:29 PM UTC
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.
Minor July 2, 2026 Control Portal Sign In Issues 1d 1h Control - Multi-Tenant Management Portal, Control - Multi-Tenant Management Portal (Control - Multi-Tenant Management Portal — 1Stream Control Portal - Central Services - North America)
Started Jul 02, 2026, 01:55 PM UTC· resolved Jul 03, 2026, 03:54 PM UTC
- identified Jul 02, 2026, 01:55 PM UTC
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.
- monitoring Jul 02, 2026, 02:57 PM UTC
All sign-in issue seem to be resolved at this time. Switching this incident to monitoring
Minor June 24, 2026 Control Portal - Sign-in Issues - Virginia 6d 4h Control - Multi-Tenant Management Portal, Control - Multi-Tenant Management Portal (Control - Multi-Tenant Management Portal — 1Stream Control Portal - Central Services - North America)
Started Jun 24, 2026, 11:33 AM UTC· resolved Jun 30, 2026, 03:44 PM UTC
- identified Jun 24, 2026, 11:33 AM UTC
We are aware and are in the middle of resolving an sign-in issue in our North America control portal region
- monitoring Jun 24, 2026, 11:56 AM UTC
We have resolved the sign-in issue in North America via all control portal url's. Switching status of this incident to monitoring
- monitoring Jun 24, 2026, 05:19 PM UTC
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.
- monitoring Jun 24, 2026, 06:00 PM UTC
At this time all control portal functions in Virginia are operating normally. We are setting this back to monitoring
Minor May 30, 2026 LACLOUD05 Unreachable 18h 31m Cloud UC Platform, SBC Layer (SBC Layer — DP: LOS ANGELES, CA)
Started May 30, 2026, 12:26 AM UTC· resolved May 30, 2026, 06:57 PM UTC
- investigating May 30, 2026, 12:26 AM UTC
Our systems are reporting a cluster in our Los Angeles data center has stopped responding. We are investigating
- investigating May 30, 2026, 12:32 AM UTC
We have confirmed we can not reach LACLOUD05. We have reached out to our data center vendor in Los Angeles to investigate
- identified May 30, 2026, 12:34 AM UTC
Our data center vendor has confirmed a power related issue. They are working on restoring.
- identified May 30, 2026, 12:59 AM UTC
It looks like the power issue has been corrected. We are bringing back the affected accounts online now. Will provide more updates shortly
- monitoring May 30, 2026, 01:26 AM UTC
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.
- investigating May 30, 2026, 02:01 AM UTC
LACLOUD05 is reporting as unreachable again. Contacting our vendor again
- identified May 30, 2026, 02:29 AM UTC
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.
- monitoring May 30, 2026, 03:12 AM UTC
All systems in our Los Angeles data center are fully operational at this time. Monitoritng
Minor May 29, 2026 Vancouver connectivity issue 1d 16h Cloud UC Platform, SBC Layer (SBC Layer — DP: VANCOUVER, CANADA)
Started May 29, 2026, 02:44 AM UTC· resolved May 30, 2026, 06:57 PM UTC
- monitoring May 29, 2026, 02:44 AM UTC
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
Minor May 29, 2026 DALCLOUD07 Cluster connectivity issue 1d 16h Cloud UC Platform, SBC Layer (SBC Layer — DP: DALLAS, TX)
Started May 29, 2026, 02:40 AM UTC· resolved May 30, 2026, 06:57 PM UTC
- investigating May 29, 2026, 02:40 AM UTC
We have been alerted and confirm one of our server clusters in the Dallas data center is unreachable. We are investigating
- investigating May 29, 2026, 02:49 AM UTC
We our in touch with our data center vendor in Dallas who is investigating locally
- identified May 29, 2026, 03:08 AM UTC
Our Dallas data center vendor confirms that a failed device needs to be replaced. We are moving forward with equipment swap.
- identified May 29, 2026, 06:41 AM UTC
Equipment replacement has been completed by our Dallas data center vendor. Affected accounts are starting to return back to normal.
- monitoring May 29, 2026, 07:27 AM UTC
All systems in Dallas back to normal. Monitoring
Minor May 18, 2026 Issue with some accounts in LA Data Center 4h 4m Cloud UC Platform, SBC Layer (SBC Layer — DP: LOS ANGELES, CA)
Started May 18, 2026, 10:53 AM UTC· resolved May 18, 2026, 02:57 PM UTC
- investigating May 18, 2026, 10:53 AM UTC
We are investigating an issue affecting some customers based out of our Los Angeles Data center. Our systems indicate its specific to one cluster.
- monitoring May 18, 2026, 11:39 AM UTC
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.
Minor May 4, 2026 Control Portal North America 13m Control - Multi-Tenant Management Portal, Control - Multi-Tenant Management Portal (Control - Multi-Tenant Management Portal — 1Stream Control Portal - Central Services - North America)
Started May 04, 2026, 07:04 PM UTC· resolved May 04, 2026, 07:17 PM UTC
- investigating May 04, 2026, 07:04 PM UTC
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.