Histórico de interrupções do 2600hz

1. 21 Here 2026 da 13:44 UTCidentified

   Por uma abundância de cautela devido a fatores externos em curso, desativamos temporariamente o Provisionador enquanto nossa equipe coloca uma atualização no lugar. Durante esse tempo, o acesso do cliente ao Portal de Suporte também não está disponível. Todos os outros serviços continuam a funcionar normalmente. Enquanto os portais não estão disponíveis, você ainda pode alcançar nossa equipe de suporte: Email: Envie seu pedido para [email protected] e um ticket será aberto para você. Telefone: Para questões urgentes, nossa linha de suporte está aceitando chamadas de entrada como de costume em 415-886-7950. Pedimos desculpas pela inconveniência e vamos postar uma atualização aqui assim que o acesso for restaurado. Obrigado pela vossa paciência.

2. 21 Here 2026 da 14:51 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

3. 21 Here 2026 da 15:27 UTCidentified

   Esteja avisado, os servidores TTS também são afetados. Embora acreditemos que temos atenuado isso sem impacto para os clientes. Se você tiver algum problema gerando novos TTS, entre em contato com nossa equipe de suporte.

4. 21 Here 2026 da 19:10 UTCmonitoring

   O fornecedor está operacional e continua a ser monitorizado quanto à estabilidade. O Portal de Suporte permanecerá disponível apenas por e-mail. O gerente de clusters (CM) permanecerá indisponível neste momento. Forneceremos atualizações adicionais conforme necessário.

5. 21 Here 2026 da 20:40 UTCmonitoring

   Estamos atualmente trabalhando em restaurar o gerente de cluster. Como parte deste trabalho, os endereços IP associados ao Cluster Manager estarão mudando. Clientes com regras de firewall ou listas de permissões de IP podem precisar atualizar suas configurações. Forneceremos os novos endereços IP assim que estiverem disponíveis. Continuaremos a fornecer atualizações à medida que o trabalho avança.

6. 22 Here 2026 da 00:05 UTCresolved

   O Cluster Manager (CM) agora está totalmente funcional. Se você quiser novos endereços IP, por favor envie um e-mail [email protected]. Além da interface web do Portal de Suporte, todos os serviços estão funcionando normalmente. Nossa equipe continua trabalhando na restauração da interface web, e publicaremos uma atualização assim que estiver disponível. Enquanto isso, o suporte permanece acessível por e-mail em [email protected] ou por telefone em 415-886-7950. Obrigado pela vossa paciência.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Eost 2026 da 15:58 UTCidentified

   Estamos vendo relatórios de problemas ao tentar fornecer telefones Yealink. Identificamos a causa raiz e estamos trabalhando para implementar uma correção.

2. 17 Eost 2026 da 15:58 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

3. 17 Eost 2026 da 18:09 UTCresolved

   Uma correção foi implementada, e o problema agora está corrigido. Continuaremos a monitorizar.

Traduzido automaticamente da atualização oficial do incidente.

1. 15 Gouere 2026 da 18:40 UTCinvestigating

   Estamos investigando potenciais problemas de API no sistema ZSwitch US na zona SJC.

2. 15 Gouere 2026 da 18:41 UTCinvestigating

   Continuamos a investigar esta questão.

3. 15 Gouere 2026 da 18:47 UTCidentified

   Identificámos a questão e estamos a trabalhar na resolução da questão.

4. 15 Gouere 2026 da 18:57 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

5. 15 Gouere 2026 da 19:05 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 12 Gouere 2026 da 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 Gouere 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 19:33 UTCresolved

   This incident has been resolved.

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

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

3. 28 Genver 2026 da 17:23 UTCresolved

   This incident has been resolved.

1. 13 Du 2025 da 20:08 UTCinvestigating

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

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

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

4. 13 Du 2025 da 20:39 UTCmonitoring

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

5. 14 Du 2025 da 17:46 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

5. 20 Eost 2025 da 20:17 UTCmonitoring

   We are seeing further degradation in the system and are investigating

6. 20 Eost 2025 da 20:29 UTCmonitoring

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

7. 20 Eost 2025 da 21:05 UTCmonitoring

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

8. 20 Eost 2025 da 22:01 UTCresolved

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

1. 30 Gwengolo 2024 da 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 Gwengolo 2024 da 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 Here 2024 da 15:42 UTCresolved

   This incident has been resolved.

1. 7 Mae 2024 da 21:24 UTCinvestigating

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

2. 7 Mae 2024 da 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 Mae 2024 da 22:03 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 7 Mae 2024 da 23:23 UTCresolved

   This incident has been resolved.

1. 9 Ebrel 2024 da 21:08 UTCinvestigating

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

2. 9 Ebrel 2024 da 23:41 UTCmonitoring

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

3. 30 Ebrel 2024 da 15:24 UTCresolved

   This incident has been resolved.

1. 27 Cʼhwevrer 2024 da 21:06 UTCinvestigating

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

2. 27 Cʼhwevrer 2024 da 23:53 UTCmonitoring

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

3. 28 Cʼhwevrer 2024 da 00:05 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 5 Genver 2024 da 14:50 UTCinvestigating

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

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

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

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

   This incident has been resolved.

1. 22 Mezheven 2023 da 13:22 UTCresolved

   We are currently investigating this issue.

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

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

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

   We have multiple confirmations that our workaround has resolved the issue

1. 2 Meurzh 2023 da 17:19 UTCinvestigating

   We are receiving reports of call completion issues in EWR

2. 2 Meurzh 2023 da 17:21 UTCmonitoring

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

3. 2 Meurzh 2023 da 23:28 UTCresolved

   This incident has been resolved.

1. 1 Meurzh 2023 da 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