Störungsverlauf von 2600hz

1. 21. Oktober 2026 um 13:44 UTCidentified

   Aus einer Fülle von Vorsicht aufgrund anhaltender externer Faktoren haben wir den Provisioner vorübergehend deaktiviert, während unser Team ein Update einführt. Während dieser Zeit ist auch der Kundenzugriff auf das Support-Portal nicht verfügbar. Alle anderen Dienste funktionieren weiterhin normal. Während die Portale nicht verfügbar sind, können Sie dennoch unser Support-Team erreichen: E-Mail: Senden Sie Ihre Anfrage an [email protected] und ein Ticket wird für Sie geöffnet. Telefon: Bei dringenden Problemen akzeptiert unsere Support-Linie wie gewohnt eingehende Anrufe unter 415-886-7950. Wir entschuldigen uns für die Unannehmlichkeiten und werden hier ein Update posten, sobald der Zugriff wiederhergestellt ist. Vielen Dank für Ihre Geduld.

2. 21. Oktober 2026 um 14:51 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 21. Oktober 2026 um 15:27 UTCidentified

   Bitte beachten Sie, dass auch TTS-Server betroffen sind. Obwohl wir glauben, dass wir dies ohne Auswirkungen auf die Kunden gemildert haben. Wenn Sie Probleme beim Erstellen neuer TTS haben, kontaktieren Sie bitte unser Support-Team.

4. 21. Oktober 2026 um 19:10 UTCmonitoring

   Provisioner ist funktionsfähig und wird weiterhin auf Stabilität überwacht. Das Support-Portal bleibt nur per E-Mail verfügbar. Cluster Manager (CM) bleibt zu diesem Zeitpunkt nicht verfügbar. Wir werden bei Bedarf zusätzliche Updates bereitstellen.

5. 21. Oktober 2026 um 20:40 UTCmonitoring

   Derzeit arbeiten wir an der Wiederherstellung des Cluster Managers. Im Rahmen dieser Arbeit werden sich die mit dem Cluster Manager verbundenen IP-Adressen ändern. Kunden mit Firewall-Regeln oder IP-Erlaubnislisten müssen möglicherweise ihre Konfigurationen aktualisieren. Wir werden die neuen IP-Adressen zur Verfügung stellen, sobald sie verfügbar sind. Wir werden weiterhin Updates zur Verfügung stellen, während die Arbeit fortschreitet.

6. 22. Oktober 2026 um 00:05 UTCresolved

   Cluster Manager (CM) ist jetzt wieder verfügbar und voll funktionsfähig. Wenn Sie neue IP-Adressen wünschen, senden Sie bitte eine E-Mail an [email protected]. Neben der Weboberfläche des Support Portals funktionieren alle Dienste normal. Unser Team arbeitet weiter an der Wiederherstellung der Weboberfläche und wir werden ein Update veröffentlichen, sobald es verfügbar ist. In der Zwischenzeit bleibt der Support per E-Mail unter [email protected] oder telefonisch unter 415-886-7950 erreichbar. Vielen Dank für Ihre Geduld.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. August 2026 um 15:58 UTCidentified

   Wir sehen Berichte über Probleme beim Versuch, Yealink-Telefone bereitzustellen. Wir haben die Ursache identifiziert und arbeiten daran, einen Fix zu implementieren.

2. 17. August 2026 um 15:58 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 17. August 2026 um 18:09 UTCresolved

   Ein Fix wurde implementiert und das Problem ist nun behoben. Wir werden weiter beobachten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 15. Juli 2026 um 18:40 UTCinvestigating

   Wir untersuchen mögliche API-Probleme auf dem ZSwitch US-System in der SJC-Zone.

2. 15. Juli 2026 um 18:41 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 15. Juli 2026 um 18:47 UTCidentified

   Wir haben das Problem erkannt und arbeiten daran, es zu lösen.

4. 15. Juli 2026 um 18:57 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

5. 15. Juli 2026 um 19:05 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Juli 2026 um 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. 12. Juli 2026 um 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. 20. Februar 2026 um 18:09 UTCinvestigating

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

2. 20. Februar 2026 um 18:15 UTCinvestigating

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

3. 20. Februar 2026 um 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. 20. Februar 2026 um 19:33 UTCresolved

   This incident has been resolved.

1. 27. Januar 2026 um 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. 28. Januar 2026 um 00:13 UTCmonitoring

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

3. 28. Januar 2026 um 17:23 UTCresolved

   This incident has been resolved.

1. 13. November 2025 um 20:08 UTCinvestigating

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

2. 13. November 2025 um 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. 13. November 2025 um 20:28 UTCinvestigating

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

4. 13. November 2025 um 20:39 UTCmonitoring

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

5. 14. November 2025 um 17:46 UTCresolved

   This incident has been resolved.

1. 2. September 2025 um 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. 2. September 2025 um 19:16 UTCresolved

   This incident has been resolved.

1. 20. August 2025 um 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. 20. August 2025 um 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. 20. August 2025 um 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. 20. August 2025 um 19:30 UTCmonitoring

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

5. 20. August 2025 um 20:17 UTCmonitoring

   We are seeing further degradation in the system and are investigating

6. 20. August 2025 um 20:29 UTCmonitoring

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

7. 20. August 2025 um 21:05 UTCmonitoring

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

8. 20. August 2025 um 22:01 UTCresolved

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

1. 30. September 2024 um 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. 30. September 2024 um 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. 4. Oktober 2024 um 15:42 UTCresolved

   This incident has been resolved.

1. 7. Mai 2024 um 21:24 UTCinvestigating

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

2. 7. Mai 2024 um 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. 7. Mai 2024 um 22:03 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 7. Mai 2024 um 23:23 UTCresolved

   This incident has been resolved.

1. 9. April 2024 um 21:08 UTCinvestigating

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

2. 9. April 2024 um 23:41 UTCmonitoring

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

3. 30. April 2024 um 15:24 UTCresolved

   This incident has been resolved.

1. 27. Februar 2024 um 21:06 UTCinvestigating

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

2. 27. Februar 2024 um 23:53 UTCmonitoring

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

3. 28. Februar 2024 um 00:05 UTCresolved

   This incident has been resolved.

1. 16. Januar 2024 um 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. 16. Januar 2024 um 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. 16. Januar 2024 um 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. 17. Januar 2024 um 01:29 UTCresolved

   This incident has been resolved.

1. 5. Januar 2024 um 14:50 UTCinvestigating

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

2. 5. Januar 2024 um 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. 5. Januar 2024 um 21:59 UTCresolved

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

1. 14. August 2023 um 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. 15. August 2023 um 00: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. 16. August 2023 um 01:53 UTCresolved

   This incident has been resolved.

1. 22. Juni 2023 um 13:22 UTCresolved

   We are currently investigating this issue.

2. 22. Juni 2023 um 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. 15. Juni 2023 um 15:57 UTCinvestigating

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

2. 15. Juni 2023 um 16:54 UTCinvestigating

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

3. 15. Juni 2023 um 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. 15. Juni 2023 um 17:54 UTCresolved

   We have multiple confirmations that our workaround has resolved the issue

1. 2. März 2023 um 17:19 UTCinvestigating

   We are receiving reports of call completion issues in EWR

2. 2. März 2023 um 17:21 UTCmonitoring

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

3. 2. März 2023 um 23:28 UTCresolved

   This incident has been resolved.

1. 1. März 2023 um 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