2600hz driftsforstyrrelser

1. 21. oktober 2026 kl. 13.44 UTCidentified

   Ud af en overflod af forsigtighed på grund af igangværende eksterne faktorer, har vi midlertidigt deaktiveret Provisioneren, mens vores team sætter en opdatering på plads. I denne periode er kundeadgang til Support Portal også ikke tilgængelig. Alle andre tjenester fungerer fortsat normalt. Mens portaler er utilgængelige, kan du stadig nå vores Support team: E-mail: Send din anmodning til support @ 2600hz.com og en billet vil blive åbnet for dig. Telefon: For presserende spørgsmål, vores support linje accepterer indgående opkald som sædvanlig på 415-886-7950. Vi undskylder ulejligheden og vil sende en opdatering her, så snart adgangen er genoprettet. Tak for din tålmodighed.

2. 21. oktober 2026 kl. 14.51 UTCidentified

   Vi fortsætter med at arbejde på en løsning på dette problem.

3. 21. oktober 2026 kl. 15.27 UTCidentified

   Vær opmærksom, TTS servere er også påvirket. Selvom vi mener, at vi har afbødet dette uden konsekvenser for kunderne. Hvis du oplever problemer med at generere nye TTS, bedes du kontakte vores support team.

4. 21. oktober 2026 kl. 19.10 UTCmonitoring

   Provisioneren er operationel og overvåges fortsat for stabilitet. Support Portalen vil kun være tilgængelig via e-mail. Cluster Manager (CM) vil forblive utilgængelig på dette tidspunkt. Vi vil levere yderligere opdateringer efter behov.

5. 21. oktober 2026 kl. 20.40 UTCmonitoring

   Vi arbejder i øjeblikket på at genoprette Cluster Manager. Som en del af dette arbejde, vil IP-adresser forbundet med Cluster Manager ændre sig. Kunder med firewall regler eller IP allolists kan være nødt til at opdatere deres konfigurationer. Vi vil give de nye IP-adresser, når de er tilgængelige. Vi vil fortsat levere opdateringer, efterhånden som arbejdet skrider frem.

6. 22. oktober 2026 kl. 00.05 UTCresolved

   Cluster Manager (CM) er nu tilbage op og fuldt funktionel. Hvis du ønsker nye IP-adresser, bedes du e-mail support @ 2600hz.com. Bortset fra Support Portal web interface, alle tjenester fungerer normalt. Vores team fortsætter med at arbejde på at genoprette web-interface, og vi vil sende en opdatering, så snart den er tilgængelig. I mellemtiden er support stadig tilgængelig via e-mail på support @ 2600hz.com eller via telefon på 415-886- 7950. Tak for din tålmodighed.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. august 2026 kl. 15.58 UTCidentified

   Vi ser rapporter om problemer, når vi forsøger at levere Yealink telefoner. Vi har identificeret årsagen og arbejder på at gennemføre en rettelse.

2. 17. august 2026 kl. 15.58 UTCidentified

   Vi fortsætter med at arbejde på en løsning på dette problem.

3. 17. august 2026 kl. 18.09 UTCresolved

   Et fix er blevet gennemført, og problemet er nu rettet. Vi vil fortsat overvåge.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. juli 2026 kl. 18.40 UTCinvestigating

   Vi undersøger potentielle API problemer på ZSwitch US system i SJC zone.

2. 15. juli 2026 kl. 18.41 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 15. juli 2026 kl. 18.47 UTCidentified

   Vi har identificeret spørgsmålet og arbejder på at løse det.

4. 15. juli 2026 kl. 18.57 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

5. 15. juli 2026 kl. 19.05 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 12. juli 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 19.33 UTCresolved

   This incident has been resolved.

1. 27. januar 2026 kl. 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 kl. 00.13 UTCmonitoring

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

3. 28. januar 2026 kl. 17.23 UTCresolved

   This incident has been resolved.

1. 13. november 2025 kl. 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 kl. 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 kl. 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 kl. 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 kl. 17.46 UTCresolved

   This incident has been resolved.

1. 2. september 2025 kl. 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 kl. 19.16 UTCresolved

   This incident has been resolved.

1. 20. august 2025 kl. 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 kl. 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 kl. 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 kl. 19.30 UTCmonitoring

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

5. 20. august 2025 kl. 20.17 UTCmonitoring

   We are seeing further degradation in the system and are investigating

6. 20. august 2025 kl. 20.29 UTCmonitoring

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

7. 20. august 2025 kl. 21.05 UTCmonitoring

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

8. 20. august 2025 kl. 22.01 UTCresolved

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

1. 30. september 2024 kl. 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 kl. 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 kl. 15.42 UTCresolved

   This incident has been resolved.

1. 7. maj 2024 kl. 21.24 UTCinvestigating

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

2. 7. maj 2024 kl. 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. maj 2024 kl. 22.03 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 7. maj 2024 kl. 23.23 UTCresolved

   This incident has been resolved.

1. 9. april 2024 kl. 21.08 UTCinvestigating

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

2. 9. april 2024 kl. 23.41 UTCmonitoring

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

3. 30. april 2024 kl. 15.24 UTCresolved

   This incident has been resolved.

1. 27. februar 2024 kl. 21.06 UTCinvestigating

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

2. 27. februar 2024 kl. 23.53 UTCmonitoring

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

3. 28. februar 2024 kl. 00.05 UTCresolved

   This incident has been resolved.

1. 16. januar 2024 kl. 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 kl. 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 kl. 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 kl. 01.29 UTCresolved

   This incident has been resolved.

1. 5. januar 2024 kl. 14.50 UTCinvestigating

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

2. 5. januar 2024 kl. 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 kl. 21.59 UTCresolved

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

1. 14. august 2023 kl. 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 kl. 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 kl. 01.53 UTCresolved

   This incident has been resolved.

1. 22. juni 2023 kl. 13.22 UTCresolved

   We are currently investigating this issue.

2. 22. juni 2023 kl. 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 kl. 15.57 UTCinvestigating

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

2. 15. juni 2023 kl. 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 kl. 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 kl. 17.54 UTCresolved

   We have multiple confirmations that our workaround has resolved the issue

1. 2. marts 2023 kl. 17.19 UTCinvestigating

   We are receiving reports of call completion issues in EWR

2. 2. marts 2023 kl. 17.21 UTCmonitoring

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

3. 2. marts 2023 kl. 23.28 UTCresolved

   This incident has been resolved.

1. 1. marts 2023 kl. 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