2600hz の障害履歴

1. 2026年8月17日 15:58 UTCidentified

   We are seeing reports of issues when attempting to provision Yealink phones. We have identified the root cause and are working to implement a fix.

2. 2026年8月17日 15:58 UTCidentified

   We are continuing to work on a fix for this issue.

3. 2026年8月17日 18:09 UTCresolved

   A fix has been implemented, and the issue is now fixed. We will continue to monitor.

1. 2026年7月15日 18:40 UTCinvestigating

   SJC ゾーンの ZSwitch US システムに関する潜在的な API の問題点を調査しています.

2. 2026年7月15日 18:41 UTCinvestigating

   今後もこの問題について調査を続けてまいります.

3. 2026年7月15日 18:47 UTCidentified

   問題を特定し、問題解決に取り組んでいます.

4. 2026年7月15日 18:57 UTCmonitoring

   修正を実装し、結果を監視しています.

5. 2026年7月15日 19:05 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月12日 21:51 UTCinvestigating

   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日 23:19 UTCresolved

   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日 18:09 UTCinvestigating

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

2. 2026年2月20日 18:15 UTCinvestigating

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

3. 2026年2月20日 18:35 UTCinvestigating

   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日 19:33 UTCresolved

   This incident has been resolved.

1. 2026年1月27日 20:26 UTCidentified

   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日 0:13 UTCmonitoring

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

3. 2026年1月28日 17:23 UTCresolved

   This incident has been resolved.

1. 2025年11月13日 20:08 UTCinvestigating

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

2. 2025年11月13日 20:14 UTCinvestigating

   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日 20:28 UTCinvestigating

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

4. 2025年11月13日 20:39 UTCmonitoring

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

5. 2025年11月14日 17:46 UTCresolved

   This incident has been resolved.

1. 2025年9月2日 17:11 UTCinvestigating

   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日 19:16 UTCresolved

   This incident has been resolved.

1. 2025年8月20日 10:50 UTCinvestigating

   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日 12:32 UTCinvestigating

   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日 12:32 UTCmonitoring

   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日 19:30 UTCmonitoring

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

5. 2025年8月20日 20:17 UTCmonitoring

   We are seeing further degradation in the system and are investigating

6. 2025年8月20日 20:29 UTCmonitoring

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

7. 2025年8月20日 21:05 UTCmonitoring

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

8. 2025年8月20日 22:01 UTCresolved

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

1. 2024年9月30日 16:03 UTCinvestigating

   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日 16:05 UTCmonitoring

   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日 15:42 UTCresolved

   This incident has been resolved.

1. 2024年5月7日 21:24 UTCinvestigating

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

2. 2024年5月7日 21:27 UTCmonitoring

   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日 22:03 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2024年5月7日 23:23 UTCresolved

   This incident has been resolved.

1. 2024年4月9日 21:08 UTCinvestigating

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

2. 2024年4月9日 23:41 UTCmonitoring

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

3. 2024年4月30日 15:24 UTCresolved

   This incident has been resolved.

1. 2024年2月27日 21:06 UTCinvestigating

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

2. 2024年2月27日 23:53 UTCmonitoring

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

3. 2024年2月28日 0:05 UTCresolved

   This incident has been resolved.

1. 2024年1月16日 21:34 UTCinvestigating

   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日 23:09 UTCidentified

   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日 23:50 UTCmonitoring

   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日 1:29 UTCresolved

   This incident has been resolved.

1. 2024年1月5日 14:50 UTCinvestigating

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

2. 2024年1月5日 21:16 UTCmonitoring

   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日 21:59 UTCresolved

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

1. 2023年8月14日 22:49 UTCinvestigating

   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日 0:10 UTCmonitoring

   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日 1:53 UTCresolved

   This incident has been resolved.

1. 2023年6月22日 13:22 UTCresolved

   We are currently investigating this issue.

2. 2023年6月22日 13:22 UTCpostmortem

   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日 15:57 UTCinvestigating

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

2. 2023年6月15日 16:54 UTCinvestigating

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

3. 2023年6月15日 17:28 UTCidentified

   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日 17:54 UTCresolved

   We have multiple confirmations that our workaround has resolved the issue

1. 2023年3月2日 17:19 UTCinvestigating

   We are receiving reports of call completion issues in EWR

2. 2023年3月2日 17:21 UTCmonitoring

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

3. 2023年3月2日 23:28 UTCresolved

   This incident has been resolved.

1. 2023年3月1日 21:53 UTCresolved

   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

1. 2023年2月16日 21:33 UTCinvestigating

   We are receiving reports of call completion issues in EWR.

2. 2023年2月16日 21:35 UTCmonitoring

   We have paused the EWR zone in full and are redirecting traffic arriving in EWR to ORD in Kamillio. Call completion rates seem to be returning to normal levels

3. 2023年2月16日 21:46 UTCmonitoring

   We have had no further reports of issues and all alerts cleared. Please write into support if you have any example calls after 13:35 PT

4. 2023年2月16日 22:14 UTCresolved

   Multiple clients are reporting no further issues

5. 2023年2月21日 22:35 UTCpostmortem

   On Thursday the 16th of February we experienced a Zswitch outage between 19:25-19:45 GMT.  ‌ As soon as we noticed alerts appearing for disconnects a 911 bridge was started with Support/Operations/Engineering/ the CTO.  ‌ This appeared to be localised to EWR; we therefore paused all EWR servers as a precaution which remediated the issues with calls.  ‌ From here we troubleshooted to determine what could have caused the outage; it was realised compaction was started on the bc003.ewr server only a few minutes beforehand; we could also see that the load was unreasonably high on this server. The compaction was stopped which brought the load down to a stable level. We also noticed that this BigCouch server was delivering DB responses in the 5-6 second range, rather than the below 50ms we would expect. This was due to the server not behaving in the expected manner when compaction was running.  ‌ Further tests were completed which helped us to determine this was an issue with the server itself and put a plan in to migrate it over to new hardware.   ‌ After the migration was complete, we further stress tested the new server to confirm compaction did not cause any issues. It’s clear that this server was major component in the 4 most recent outages. ‌ We have added new alerting which will help us to have higher visibility of response times from all servers to Bigcouch as this will allow us to notice any similar issues before they start to impact. We are also further improving this alerting to exclude crossbar \(API\) calls which will help keep out any false positives, as well as adding similar active testing across all HA Layers in Kazoo.  ‌ During the holiday weekend we staged a “All hands on deck” meeting to go over the outages we’ve seen and the steps we can put in place to improve. We want to convey that the seriousness of the downtime we have seen is understood and we’re continuing to work to prevent any recurrences.  Following this call we have come out with a list of action items that we’ll be undertaking with the highest priority; including the aforementioned monitoring changes, and reprioritising engineering load to speed up the migration over to CouchDB 3 from BigCouch.  ‌ If anyone has any further questions, or you’d like deeper information on what steps we’re taking to prevent further outages please don’t hesitate to get in touch.