Bvoip 中断历史

1. 2026年9月1日 UTC 11:23resolved

   2026年8月31日 1:51PM EDT 已确认 - 我们知道微软在网上发布Exchange的外出消息。 你可以看到这正在报道 在几个地方。 https://www.bleeping computer.com/news/microsoft/microsoft-exchange-online-outage-causes-email-faulures-auth-issues/ 互联网档案馆的存檔,存档日期2013-12-11. 1. 如果您正在发邮件 1Stream, 您的留言可能无法联系到我们 销售, 支持等 。 我们的系统是在线的,但电子邮件可能不会堕落。 2. 如果您使用M365从您的 1 Stream 账户中发送的邮件, 如提醒、语音邮件到电子邮件等, 这些信件很可能不会发送 。 2026年8月31日 8:45PM EDT Monitoring - 我们看到今天大约中午东部时间微软365 / Exchange Online断电时, 我们将继续监控微软所有服务恢复到100%。 9月1日 2026 7: 23AM EDT 解决 - 似乎微软昨天的停电事件, 以下是公布的时间表 https://mashable.com/tech/microsoft-out look-outage-aug-31

自动翻译自官方事件更新。

1. 2026年8月23日 UTC 22:00resolved

   2026年7月30日 2:43PM EDT Schedule - 我们的数据中心供应商建议我们悉尼数据中心区域进行以下维护: 互联网档案馆的存檔,存档日期2013-12-02. 作为我们正在进行的网络基础设施升级的一部分,我们已经安排在悉尼的一个交换机中更换硬件。 受影响的服务器在维护窗口期间会遇到长达60分钟的故障. 为了尽量减少对服务的影响,工作将在夜间进行。 他们表示时间窗口为8小时, 8月23日 2:00 PM EDT Active - 计划于悉尼的网络基础设施升级 - 8:24 - 窗口 从8月23日开始 2026 6:00 PM EDT 完成 - 计划于悉尼的网络基础设施升级 - 8:24 - 窗口结束

自动翻译自官方事件更新。

1. 2026年7月27日 UTC 14:11resolved

   2026年7月26日 7:31AM EDT监测 - 这是一个追溯性的事件。 我们洛杉矶的数据中心供应商告诉我们 洛杉矶有部分连接中断 这个问题从晚上11点34分开始 以洛杉矶时间3点04分解决 发行时间共为3小时40分. 这就是我们接到的报告: 事件由服务于受影响服务器的其中一个网络设备的硬件故障所造成. 故障组件被替换,在恢复过程中需要额外的软件调整,才能恢复正常运行. 2026年7月27日 10:11AM EDT解析 - 终结事件

自动翻译自官方事件更新。

1. 2026年7月14日 UTC 13:29resolved

   2026年7月8日 11:08AM EDT 已确认 - 我们收到数起账户报告, 这是一个航母侧面的问题, 我们已经升级到我们的三级升级路径 用bcmone。 我们发现,对于 siptrunk.com ,这些设置的更改提供了一些帮助,从 gw1. siptrunk & gw2. 更改正在使用的网关 。 siptrunk to gw4 and gw5 分别禁用树干设置 选项"PBX送出音频" 2026年7月8日 1:24PM ETT 已识别 - 更新自 siptrunk.com 谢谢你的这个信息。 我进一步将此事升级到我们的发展和工程小组,他们告知,他们目前意识到可能影响到RTP音频流量并阻止音频包正确通过的内部问题。 我们的小组正在积极调查这一问题并审查所报告的症状是否与目前内部观察到的行为相符。 目前,根据现有资料来看,这似乎是最可能的重点领域。 我们将继续密切监测局势并同有关小组进行协调。 一旦我们收到关于根本原因和解决办法的其他调查结果或确认,我将立即向你提供最新情况。 感谢你的耐心和合作 在我们调查期间 July 8, 2026 2: 37PM EDT 监控 - 最新消息出自 siptrunk.com / bcmone 谢谢你的耐心 在我们处理这个间歇性的音频问题时 根本原因特别难以确定,因为受影响的电话正在穿越多个网关,因此很难孤立一个共同因素。 在收集其他客户的更多呼叫实例并将此事升级到我们的发展团队之后,我们确定该问题源于我们的网络。 内部循环导致音频流量消耗过多的端口,导致音频中断的报道. 我们的开发团队在下午1点半对EDT进行了纠正性修改,自从进行了这些更新后,客户报告说电话音频质量有了显著改善。 此时此刻,我们请你继续监测和重新测试你的服务,并告诉我们你是否经历过任何进一步的问题,以便我们确认此事已经完全解决。 7月9日, 2026 9: 23AM EDT 解析 - 结束事件 7月9日, 2026 12: 28PM EDT 调查 - 我们有一个相对安静的早晨, 但我们有一些新的报告 进入呼叫的问题, 我们收集了一些例子,并把它们送回他们的小组审查。 2026年7月9日 1:29PM EDT监测 - 最新消息出自 bcmone / siptrunk.com 我们的发展工程团队通知我,他们实施了额外的内部改革,旨在缓解已经发生的出入境音频问题. 此时,请重新测试并继续监听您的电话,以确认音频现在双向正常通过,问题已经解决. 如果你继续遇到任何问题,请提供新的呼叫例子,我们将乐于进一步调查。 2026年7月14日 9:29AM EDT解析出——自上星期以来未提出更新问题. 结束事件

自动翻译自官方事件更新。

1. 2026年7月3日 UTC 15:46resolved

   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

1. 2026年6月30日 UTC 15:34resolved

   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

1. 2026年5月30日 UTC 18:55resolved

   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

1. 2026年5月30日 UTC 18:54resolved

   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

1. 2026年5月30日 UTC 18:54resolved

   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

1. 2026年5月28日 UTC 19:26resolved

   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.

1. 2026年5月18日 UTC 14:56resolved

   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

1. 2026年5月4日 UTC 19:12resolved

   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