Istoricul incidentelor 2600hz

1. 21 octombrie 2026 la 13:44 UTCidentified

   Dintr-o abundență de precauție din cauza factorilor externi în curs de desfășurare, am dezactivat temporar Furnizorul în timp ce echipa noastră pune o actualizare în vigoare. În acest timp, accesul clienților la portalul de sprijin nu este disponibil. Toate celelalte servicii continuă să funcționeze în mod normal. În timp ce portalurile sunt indisponibile, puteți ajunge încă echipa noastră de sprijin: E-mail: Trimite cererea ta la [email protected] și un bilet va fi deschis pentru tine. Telefon: Pentru probleme urgente, linia noastră de sprijin acceptă apelurile de intrare ca de obicei la 415-886-7950. Ne cerem scuze pentru inconveniente și va posta o actualizare aici de îndată ce accesul este restabilit. Mulţumesc pentru răbdare.

2. 21 octombrie 2026 la 14:51 UTCidentified

   Continuăm să lucrăm la o soluție pentru această problemă.

3. 21 octombrie 2026 la 15:27 UTCidentified

   Vă rugăm să fiţi atenţi, serverele TTS sunt de asemenea afectate. Deşi credem că am atenuat asta fără impact asupra clienţilor. Dacă aveţi probleme care generează noi TTS, vă rugăm să contactaţi echipa noastră de sprijin.

4. 21 octombrie 2026 la 19:10 UTCmonitoring

   Furnizorul este operațional și continuă să fie monitorizat pentru stabilitate. Portalul de suport va rămâne disponibil doar prin e-mail. Cluster Manager (CM) va rămâne indisponibil în acest moment. Vom furniza actualizări suplimentare, după cum este necesar.

5. 21 octombrie 2026 la 20:40 UTCmonitoring

   În prezent lucrăm la restaurarea managerului de clustere. Ca parte a acestei lucrări, adresele IP asociate cu Cluster Manager se vor schimba. Clientii cu reguli firewall sau permise IP pot avea nevoie pentru a actualiza configuratiile lor. Vom furniza noile adrese IP odată ce acestea sunt disponibile. Vom continua să oferim actualizări pe măsură ce activitatea progresează.

6. 22 octombrie 2026 la 00:05 UTCresolved

   Cluster Manager (CM) este acum complet funcţional. Dacă doriți noi adrese IP, vă rugăm să trimiteți email [email protected]. În afară de interfața web portal de sprijin, toate serviciile funcționează în mod normal. Echipa noastră continuă să lucreze la restaurarea interfeței web, și vom posta o actualizare de îndată ce este disponibil. Între timp, Suportul rămâne accesibil prin e-mail la [email protected] sau prin telefon la 415-886-7950. Mulţumesc pentru răbdare.

Traducere automată din actualizarea oficială a incidentului.

1. 17 august 2026 la 15:58 UTCidentified

   Vedem rapoarte de probleme atunci când încearcă să furnizeze telefoane Yealink. Am identificat cauza principală și lucrăm la implementarea unei soluții.

2. 17 august 2026 la 15:58 UTCidentified

   Continuăm să lucrăm la o soluție pentru această problemă.

3. 17 august 2026 la 18:09 UTCresolved

   A fost pusă în aplicare o soluţie, iar problema este acum rezolvată. Vom continua să monitorizăm.

Traducere automată din actualizarea oficială a incidentului.

1. 15 iulie 2026 la 18:40 UTCinvestigating

   Investigăm potențiale probleme API pe sistemul ZSwitch SUA în zona SJC.

2. 15 iulie 2026 la 18:41 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 15 iulie 2026 la 18:47 UTCidentified

   Am identificat problema și lucrăm la soluționarea problemei.

4. 15 iulie 2026 la 18:57 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

5. 15 iulie 2026 la 19:05 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 12 iulie 2026 la 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 iulie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 19:33 UTCresolved

   This incident has been resolved.

1. 27 ianuarie 2026 la 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 ianuarie 2026 la 00:13 UTCmonitoring

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

3. 28 ianuarie 2026 la 17:23 UTCresolved

   This incident has been resolved.

1. 13 noiembrie 2025 la 20:08 UTCinvestigating

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

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

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

4. 13 noiembrie 2025 la 20:39 UTCmonitoring

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

5. 14 noiembrie 2025 la 17:46 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

5. 20 august 2025 la 20:17 UTCmonitoring

   We are seeing further degradation in the system and are investigating

6. 20 august 2025 la 20:29 UTCmonitoring

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

7. 20 august 2025 la 21:05 UTCmonitoring

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

8. 20 august 2025 la 22:01 UTCresolved

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

1. 30 septembrie 2024 la 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 septembrie 2024 la 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 octombrie 2024 la 15:42 UTCresolved

   This incident has been resolved.

1. 7 mai 2024 la 21:24 UTCinvestigating

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

2. 7 mai 2024 la 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 la 22:03 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 7 mai 2024 la 23:23 UTCresolved

   This incident has been resolved.

1. 9 aprilie 2024 la 21:08 UTCinvestigating

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

2. 9 aprilie 2024 la 23:41 UTCmonitoring

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

3. 30 aprilie 2024 la 15:24 UTCresolved

   This incident has been resolved.

1. 27 februarie 2024 la 21:06 UTCinvestigating

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

2. 27 februarie 2024 la 23:53 UTCmonitoring

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

3. 28 februarie 2024 la 00:05 UTCresolved

   This incident has been resolved.

1. 16 ianuarie 2024 la 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 ianuarie 2024 la 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 ianuarie 2024 la 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 ianuarie 2024 la 01:29 UTCresolved

   This incident has been resolved.

1. 5 ianuarie 2024 la 14:50 UTCinvestigating

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

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

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

1. 14 august 2023 la 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 la 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 la 01:53 UTCresolved

   This incident has been resolved.

1. 22 iunie 2023 la 13:22 UTCresolved

   We are currently investigating this issue.

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

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

2. 15 iunie 2023 la 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 iunie 2023 la 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 iunie 2023 la 17:54 UTCresolved

   We have multiple confirmations that our workaround has resolved the issue

1. 2 martie 2023 la 17:19 UTCinvestigating

   We are receiving reports of call completion issues in EWR

2. 2 martie 2023 la 17:21 UTCmonitoring

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

3. 2 martie 2023 la 23:28 UTCresolved

   This incident has been resolved.

1. 1 martie 2023 la 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