2600hz 中断历史

1. 2026年10月21日 UTC 13:44identified

   由于持续的外部因素,我们非常谨慎,暂时使 " 提供者 " 处于瘫痪状态,而我们的团队则进行了更新。 在此期间,客户也无法进入支助门户。 所有其他服务继续正常运作。 虽然没有门户,你仍可以联系我们的支援小组: 电子邮件:发送您的支持@2600hz.com的请求,并将为您打开一张罚单. 电话:紧急问题,我们的支援线照常在415-886-7950接受入境电话. 我们对此不便表示歉意,一旦恢复访问,我们将在此发布最新消息。 谢谢你的耐心.

2. 2026年10月21日 UTC 14:51identified

   我们正在继续努力解决这个问题。

3. 2026年10月21日 UTC 15:27identified

   请注意, TTS 服务器也受到影响 。 虽然我们相信我们已经减轻了这种情况,但没有对客户产生影响。 如果你遇到任何产生新TTS的问题,请联系我们的支援团队.

4. 2026年10月21日 UTC 19:10monitoring

   供应者已开始运作,并继续受到监测,以确保稳定。 支助门户仅通过电子邮件提供。 集群管理器(CM)目前仍然无法使用. 我们将视需要提供补充资料.

5. 2026年10月21日 UTC 20:40monitoring

   我们目前正在恢复集群管理器。 作为这项工作的一部分,与集群管理器相关的IP地址将会被改变. 拥有防火墙规则或IP许可列表的客户可能需要更新其配置. 一旦有了新的IP地址,我们将提供这些地址。 随着工作的进展,我们将继续提供最新情况.

6. 2026年10月22日 UTC 00:05resolved

   集群管理器(CM)现在已备份并充分运作. 如果您想要新的IP地址,请通过电子邮件支持@2600hz.com. 除支持门户网络接口外,所有服务都正常运行. 我们的团队正在继续努力恢复网页界面,一旦有更新,我们将立即张贴。 同时,仍可通过电子邮件在@2600hz.com上或通过电话在415-886-7950上获得支助。 谢谢你的耐心.

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

1. 2026年8月17日 UTC 15:58identified

   我们在试图提供Yealink手机时看到一些问题的报道。 我们已查明了根源,并正在努力执行一个解决办法.

2. 2026年8月17日 UTC 15:58identified

   我们正在继续努力解决这个问题。

3. 2026年8月17日 UTC 18:09resolved

   一项固定措施已经执行,现在问题已经解决。 我们将继续进行监测.

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

1. 2026年7月15日 UTC 18:40investigating

   我们正在调查美国SJC区ZSwitch系统的潜在API问题.

2. 2026年7月15日 UTC 18:41investigating

   我们正在继续调查这一问题.

3. 2026年7月15日 UTC 18:47identified

   我们已查明了这个问题,并正在努力解决这一问题.

4. 2026年7月15日 UTC 18:57monitoring

   一项措施已经执行,我们正在监测结果.

5. 2026年7月15日 UTC 19:05resolved

   这一事件已经得到解决.

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

1. 2026年7月12日 UTC 21:51investigating

   We're currently seeing heightened alerts related to connectivity between zones, we're engaging our infrastructure team to investigate further. We'll update here as soon as we know more, in the meantime please raise a ticket with us if you're experiencing any degradation to service.

2. 2026年7月12日 UTC 23:19resolved

   The issues we saw should now be resolved; this was limited to hosts in the SJC zone. We will send out a full RCA in due course, please let us know if you experience any further issues.

1. 2026年2月20日 UTC 18:09investigating

   We are currently investigating Zabbix alerts/reports of outages affecting portal/calls. We will send out an update as ASAP.

2. 2026年2月20日 UTC 18:15investigating

   This appears to a problem with Level3 currently; our infrastructure team is investigating implementing routing changes to workaround the issue.

3. 2026年2月20日 UTC 18:35investigating

   Cloudflare appears to have stopped advertising our 8.X addresses causing this outage; we have now re-enabled them. We're working with CloudFlare to investigate the root cause but are seeing issues resolve from our side.

4. 2026年2月20日 UTC 19:33resolved

   This incident has been resolved.

1. 2026年1月27日 UTC 20:26identified

   We are seeing degraded performance and intermittent issues in the ORD zone due to a Cloudflare issue: https://www.cloudflarestatus.com/ We are monitoring the situation. Users who are experiencing issues can route away from the ORD zone by cutting over to the east or west zones.

2. 2026年1月28日 UTC 00:13monitoring

   Cloudflare has reported a fix has been implemented. We are monitoring for issues.

3. 2026年1月28日 UTC 17:23resolved

   This incident has been resolved.

1. 2025年11月13日 UTC 20:08investigating

   We are investigating an issue with a partial outage due to loss of connectivity to one of our zones.

2. 2025年11月13日 UTC 20:14investigating

   We are experiencing uptime issues with our San Jose datacenter and are working to resolve it. Phones that are properly configured to register to SRV/NAPTR records should fail over to the other zones.

3. 2025年11月13日 UTC 20:28investigating

   We are seeing a fiber related issue in our San Jose datacenter and are working to resolve it.

4. 2025年11月13日 UTC 20:39monitoring

   We have resolved the issue and believe we are operational at this time. We are monitoring the incident.

5. 2025年11月14日 UTC 17:46resolved

   This incident has been resolved.

1. 2025年9月2日 UTC 17:11investigating

   We've observed issues with Inbound/Outbound SMS and MMS and have confirmed this appears to be consistently impacting all of ZSwitch.

2. 2025年9月2日 UTC 19:16resolved

   This incident has been resolved.

1. 2025年8月20日 UTC 10:50investigating

   We are currently investigating an issue with Zswitch US' database services. We have engaged our engineering and operations team to work this as highest priority. We will update this page as soon as we know more.

2. 2025年8月20日 UTC 12:32investigating

   This issue has now been resolved and the database services are operating as expected. We are working on a full RCA and will update this statuspage with it in due course. If you have any questions in the meantime please contact support using the normal methods.

3. 2025年8月20日 UTC 12:32monitoring

   This issue has now been resolved and the database services are operating as expected. We are working on a full RCA and will update this statuspage with it in due course. If you have any questions in the meantime please contact support using the normal methods. We will continue to monitor throughout the day.

4. 2025年8月20日 UTC 19:30monitoring

   We've stabilized services and are continuing to monitor the situation.

5. 2025年8月20日 UTC 20:17monitoring

   We are seeing further degradation in the system and are investigating

6. 2025年8月20日 UTC 20:29monitoring

   We have identified a database system outage and are working with our engineers to restore the system.

7. 2025年8月20日 UTC 21:05monitoring

   We have brought services back online and are continuing to monitor for stability.

8. 2025年8月20日 UTC 22:01resolved

   This incident has been resolved. We will continue to monitor for stability.

1. 2024年9月30日 UTC 16:03investigating

   Please be advised that we are currently hearing of widespread ISP issues across the country. Major media outlets are reporting Verizon-related outages, but we suspect the impact is at least somewhat wider. No 2600Hz services are directly impacted at this time. However, resellers can expect to see increased reports from clients, especially Verizon clients

2. 2024年9月30日 UTC 16:05monitoring

   Please be advised that we are currently hearing of widespread ISP issues across the country. Major media outlets are reporting Verizon-related outages, but we suspect the impact is at least somewhat wider. No 2600Hz services are directly impacted at this time. However, resellers can expect to see increased reports from clients, especially Verizon clients

3. 2024年10月4日 UTC 15:42resolved

   This incident has been resolved.

1. 2024年5月7日 UTC 21:24investigating

   We are currently investigating reports of issues with loading Call Center in our UI and comm.land.

2. 2024年5月7日 UTC 21:27monitoring

   We have identified that we were receiving alerts from two of our apps servers having issues connecting to each other. We've restarted Kazoo Apps on both servers. We've received confirmation from some customers that this is resolved, we've received no new reports, and we've been unable to replicate since the restarts. We're monitoring to ensure this is resolved.

3. 2024年5月7日 UTC 22:03monitoring

   We are continuing to monitor for any further issues.

4. 2024年5月7日 UTC 23:23resolved

   This incident has been resolved.

1. 2024年4月9日 UTC 21:08investigating

   We are investigating reports of degraded call services in our EWR zone

2. 2024年4月9日 UTC 23:41monitoring

   We have mitigated the issue and our engineers are working to identify the root cause

3. 2024年4月30日 UTC 15:24resolved

   This incident has been resolved.

1. 2024年2月27日 UTC 21:06investigating

   We are receiving reports of call completion issues on EWR. We are investigating.

2. 2024年2月27日 UTC 23:53monitoring

   We have mitigated the issue and are monitoring the system for any further issues.

3. 2024年2月28日 UTC 00:05resolved

   This incident has been resolved.

1. 2024年1月16日 UTC 21:34investigating

   We are seeing increasing reports of semi-attended transfers not reaching the recipient's voice mail if the recipient does not answer. This is impacting our Hosted Platform only and we are currently investigating the issue.

2. 2024年1月16日 UTC 23:09identified

   We believe we have identified the issue. We have deployed a patch to the SJC zone and are currently testing before we deploy to ORD and EWR.

3. 2024年1月16日 UTC 23:50monitoring

   Testing has been successful so far and we've deployed the patch to all remaining Hosted Platform servers. We believe this to be fixed now, but will continue monitoring for any further issues.

4. 2024年1月17日 UTC 01:29resolved

   This incident has been resolved.

1. 2024年1月5日 UTC 14:50investigating

   We are receiving reports of call completion issues over web sockets registered devices including comm.land phones

2. 2024年1月5日 UTC 21:16monitoring

   At this time we believe this issue affected clients that were using comm.land AND immediately updated their comm.land software this morning. This issue should now be resolved, we are monitoring the situation to validate.

3. 2024年1月5日 UTC 21:59resolved

   We've had multiple customer reports that this issue is now resolved

1. 2023年8月14日 UTC 22:49investigating

   Presently, a concern has arisen wherein one out of the three Kamailio servers located in EWR is encountering difficulty in processing SIP registrations. It's important to note that this issue is not expected to affect our services, as phones that are appropriately configured will automatically attempt registration through alternate SBCs and/or zones. If you're currently facing challenges with phone registrations, we encourage you to reach out to our support team. This way, we can assist you in enhancing your phone's configuration to proactively avoid similar issues moving forward.

2. 2023年8月15日 UTC 00:10monitoring

   We would like to inform you that several clients have reported successful phone registrations after we implemented a TCP traffic block to and from this specific SBC. This leads us to believe that the issue is currently fully mitigated. In light of this, we are intentionally leaving this SBC in a degraded state to facilitate thorough investigation by our engineering teams as required. Our intention is to conduct a server reboot tomorrow evening. We will keep this incident active until that time to facilitate full transparency into the issue.

3. 2023年8月16日 UTC 01:53resolved

   This incident has been resolved.

1. 2023年6月22日 UTC 13:22resolved

   We are currently investigating this issue.

2. 2023年6月22日 UTC 13:22postmortem

   After investigation Kamailio was restarted which resolved the issue - Please let us know if you encounter any further disruption. We are working on investigating the root cause.

1. 2023年6月15日 UTC 15:57investigating

   We are receiving increased Reports Of One Way Audio Issues in EWR datacenter

2. 2023年6月15日 UTC 16:54investigating

   At this time we do believe this is isolated to clients on a single ISP. We are continuing to investigate

3. 2023年6月15日 UTC 17:28identified

   We do believe this issue is with a particular peer. We are advertising new BGP routes to attempt to work around this issue

4. 2023年6月15日 UTC 17:54resolved

   We have multiple confirmations that our workaround has resolved the issue

1. 2023年3月2日 UTC 17:19investigating

   We are receiving reports of call completion issues in EWR

2. 2023年3月2日 UTC 17:21monitoring

   We have paused the EWR zone and are monitoring for any further issues

3. 2023年3月2日 UTC 23:28resolved

   This incident has been resolved.

1. 2023年3月1日 UTC 21:53resolved

   At 13:13:56 PT we received alerts that multiple BGP sessions had dropped in our US-West datacenter. This included our backhaul between US-East and US-West, as well as one of our outbound ISPs. The backhaul traffic failed over to the secondary by 13:14:03 PT, and the session with the outbound ISP recovered by 13:25:21 PT. We believe there was no impact on inbound, or outbound traffic to/from the 2600Hz network during this incident. We have engaged our providers to get more information on what occurred, but all seems to have recovered by 13:25:21 PT. Thank you, 2600Hz Infrastructure