Historial de interrupciones de 2600hz

1. 21 de octubre de 2026 a las 13:44 UTCidentified

   De una gran precaución debido a factores externos en curso, hemos discapacitado temporalmente al Proveedor mientras nuestro equipo pone en marcha una actualización. Durante este tiempo, el acceso al cliente al Portal de Soporte también no está disponible. Todos los demás servicios siguen funcionando normalmente. Mientras los portales no están disponibles, todavía puede llegar a nuestro equipo de soporte: Correo electrónico: Enviar su solicitud a [email protected] y se abrirá un ticket para usted. Teléfono: Para problemas urgentes, nuestra línea de soporte está aceptando llamadas entrantes como de costumbre en 415-886-7950. Nos disculpamos por la molestia y publicaremos una actualización aquí tan pronto como se restablezca el acceso. Gracias por su paciencia.

2. 21 de octubre de 2026 a las 14:51 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

3. 21 de octubre de 2026 a las 15:27 UTCidentified

   Tenga en cuenta que los servidores TTS también están impactados. Aunque creemos que hemos mitigado esto sin impacto para los clientes. Si experimenta algún problema generando nuevos TTS, póngase en contacto con nuestro equipo de soporte.

4. 21 de octubre de 2026 a las 19:10 UTCmonitoring

   El proveedor está en funcionamiento y sigue siendo supervisado para la estabilidad. El Portal de Soporte permanecerá disponible solo por correo electrónico. Cluster Manager (CM) permanecerá indisponible en este momento. Proporcionaremos actualizaciones adicionales según sea necesario.

5. 21 de octubre de 2026 a las 20:40 UTCmonitoring

   Actualmente estamos trabajando en la restauración de Cluster Manager. Como parte de este trabajo, las direcciones IP asociadas con Cluster Manager cambiarán. Los clientes con reglas de cortafuegos o habilitadores IP pueden necesitar actualizar sus configuraciones. Proporcionaremos las nuevas direcciones IP cuando estén disponibles. Seguiremos proporcionando actualizaciones a medida que avance el trabajo.

6. 22 de octubre de 2026 a las 0:05 UTCresolved

   Cluster Manager (CM) está ahora de vuelta y totalmente funcional. Si desea nuevas direcciones IP, envíe un correo electrónico a [email protected]. Aparte de la interfaz web del Portal de Soporte, todos los servicios funcionan normalmente. Nuestro equipo continúa trabajando en la restauración de la interfaz web, y publicaremos una actualización tan pronto como esté disponible. Mientras tanto, el soporte sigue siendo accesible por correo electrónico a [email protected] o por teléfono al 415-886-7950. Gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de agosto de 2026 a las 15:58 UTCidentified

   Estamos viendo informes de problemas al intentar proporcionar teléfonos Yealink. Hemos identificado la causa raíz y estamos trabajando para implementar una solución.

2. 17 de agosto de 2026 a las 15:58 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

3. 17 de agosto de 2026 a las 18:09 UTCresolved

   Se ha aplicado una solución, y la cuestión está ahora fijada. Seguiremos vigilando.

Traducido automáticamente desde la actualización oficial del incidente.

1. 15 de julio de 2026 a las 18:40 UTCinvestigating

   Estamos investigando posibles problemas de API en el sistema ZSwitch US en la zona SJC.

2. 15 de julio de 2026 a las 18:41 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 15 de julio de 2026 a las 18:47 UTCidentified

   Hemos identificado la cuestión y estamos trabajando para resolver la cuestión.

4. 15 de julio de 2026 a las 18:57 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. 15 de julio de 2026 a las 19:05 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 12 de julio de 2026 a las 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 de julio de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 19:33 UTCresolved

   This incident has been resolved.

1. 27 de enero de 2026 a las 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 de enero de 2026 a las 0:13 UTCmonitoring

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

3. 28 de enero de 2026 a las 17:23 UTCresolved

   This incident has been resolved.

1. 13 de noviembre de 2025 a las 20:08 UTCinvestigating

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

2. 13 de noviembre de 2025 a las 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 de noviembre de 2025 a las 20:28 UTCinvestigating

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

4. 13 de noviembre de 2025 a las 20:39 UTCmonitoring

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

5. 14 de noviembre de 2025 a las 17:46 UTCresolved

   This incident has been resolved.

1. 2 de septiembre de 2025 a las 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 de septiembre de 2025 a las 19:16 UTCresolved

   This incident has been resolved.

1. 20 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 19:30 UTCmonitoring

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

5. 20 de agosto de 2025 a las 20:17 UTCmonitoring

   We are seeing further degradation in the system and are investigating

6. 20 de agosto de 2025 a las 20:29 UTCmonitoring

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

7. 20 de agosto de 2025 a las 21:05 UTCmonitoring

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

8. 20 de agosto de 2025 a las 22:01 UTCresolved

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

1. 30 de septiembre de 2024 a las 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 de septiembre de 2024 a las 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 de octubre de 2024 a las 15:42 UTCresolved

   This incident has been resolved.

1. 7 de mayo de 2024 a las 21:24 UTCinvestigating

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

2. 7 de mayo de 2024 a las 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 de mayo de 2024 a las 22:03 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 7 de mayo de 2024 a las 23:23 UTCresolved

   This incident has been resolved.

1. 9 de abril de 2024 a las 21:08 UTCinvestigating

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

2. 9 de abril de 2024 a las 23:41 UTCmonitoring

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

3. 30 de abril de 2024 a las 15:24 UTCresolved

   This incident has been resolved.

1. 27 de febrero de 2024 a las 21:06 UTCinvestigating

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

2. 27 de febrero de 2024 a las 23:53 UTCmonitoring

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

3. 28 de febrero de 2024 a las 0:05 UTCresolved

   This incident has been resolved.

1. 16 de enero de 2024 a las 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 de enero de 2024 a las 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 de enero de 2024 a las 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 de enero de 2024 a las 1:29 UTCresolved

   This incident has been resolved.

1. 5 de enero de 2024 a las 14:50 UTCinvestigating

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

2. 5 de enero de 2024 a las 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 de enero de 2024 a las 21:59 UTCresolved

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

1. 14 de agosto de 2023 a las 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 de agosto de 2023 a las 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. 16 de agosto de 2023 a las 1:53 UTCresolved

   This incident has been resolved.

1. 22 de junio de 2023 a las 13:22 UTCresolved

   We are currently investigating this issue.

2. 22 de junio de 2023 a las 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 de junio de 2023 a las 15:57 UTCinvestigating

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

2. 15 de junio de 2023 a las 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 de junio de 2023 a las 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 de junio de 2023 a las 17:54 UTCresolved

   We have multiple confirmations that our workaround has resolved the issue

1. 2 de marzo de 2023 a las 17:19 UTCinvestigating

   We are receiving reports of call completion issues in EWR

2. 2 de marzo de 2023 a las 17:21 UTCmonitoring

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

3. 2 de marzo de 2023 a las 23:28 UTCresolved

   This incident has been resolved.

1. 1 de marzo de 2023 a las 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