Historial de interrupciones de Switchco

1. September 3, 2026 at 9:54 AM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. September 3, 2026 at 10:12 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. September 3, 2026 at 10:19 AM UTCidentified

   La cuestión se ha identificado con un transportista de telefonía. Las llamadas de salida se han enrutado alrededor del transportista problemático, pero las llamadas de entrada todavía pueden ser impactadas.

4. September 3, 2026 at 10:27 AM UTCmonitoring

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

5. September 3, 2026 at 10:36 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. September 1, 2026 at 4:05 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

2. September 1, 2026 at 4:44 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

3. September 1, 2026 at 5:14 PM UTCinvestigating

   Seguimos investigando esta cuestión.

4. September 1, 2026 at 6:34 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

5. September 1, 2026 at 6:35 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

6. September 1, 2026 at 7:03 PM UTCmonitoring

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

7. September 1, 2026 at 8:02 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 21, 2026 at 4:21 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

2. August 21, 2026 at 4:42 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados. Los agentes deben refrescar su aplicación para recoger el cambio.

3. August 21, 2026 at 5:09 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 28, 2026 at 4:22 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

2. July 28, 2026 at 4:50 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 7, 2026 at 6:38 PM UTCinvestigating

   Algunos clientes pueden estar experimentando un rendimiento degradado con llamadas IVR. Las llamadas degradadas irán a los contratiempos designados.

2. July 7, 2026 at 7:26 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. July 7, 2026 at 7:33 PM UTCmonitoring

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

4. July 7, 2026 at 8:02 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 30, 2026 at 11:23 PM UTCinvestigating

   Estamos investigando un posible deterioro con la llamada.

2. June 30, 2026 at 11:54 PM UTCmonitoring

   Se ha aplicado una solución. Las operaciones de llamada volvieron a la normalidad.

3. July 1, 2026 at 5:38 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 11, 2026 at 8:55 PM UTCinvestigating

   We are currently investigating this issue.

2. June 11, 2026 at 9:01 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. June 11, 2026 at 9:40 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. June 11, 2026 at 11:42 PM UTCresolved

   This incident has been resolved.

1. June 9, 2026 at 4:34 PM UTCinvestigating

   We are currently investigating this issue.

2. June 9, 2026 at 5:03 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. June 9, 2026 at 5:14 PM UTCresolved

   This incident has been resolved.

1. June 8, 2026 at 10:43 PM UTCinvestigating

   We are currently investigating the issue.

2. June 9, 2026 at 1:02 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. June 9, 2026 at 1:53 AM UTCresolved

   This incident has been resolved.

1. May 20, 2026 at 7:36 PM UTCinvestigating

   We are continuing to investigate this issue.

2. May 20, 2026 at 10:18 PM UTCinvestigating

   We are currently investigating this issue.

3. May 20, 2026 at 11:33 PM UTCidentified

   The issue has been identified and a fix is being implemented.

4. May 20, 2026 at 11:55 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. May 21, 2026 at 12:26 AM UTCresolved

   This incident has been resolved.

1. May 4, 2026 at 3:11 PM UTCinvestigating

   We are currently investigating this issue.

2. May 4, 2026 at 3:19 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. May 4, 2026 at 5:29 PM UTCidentified

   We are continuing to work on a fix for this issue.

4. May 4, 2026 at 5:39 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. May 4, 2026 at 6:17 PM UTCresolved

   This incident has been resolved.

1. April 8, 2026 at 7:17 PM UTCinvestigating

   We are currently investigating this issue.

2. April 8, 2026 at 7:44 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. April 8, 2026 at 9:18 PM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 3:47 PM UTCinvestigating

   We are investigating a potential outage for some customers.

2. March 10, 2026 at 5:29 PM UTCinvestigating

   We are continuing to investigate this issue.

3. March 10, 2026 at 5:31 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. March 12, 2026 at 10:11 PM UTCresolved

   This incident has been resolved.

1. February 13, 2026 at 4:39 PM UTCinvestigating

   We are currently investigating this issue.

2. February 13, 2026 at 4:46 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. February 13, 2026 at 5:31 PM UTCresolved

   This incident has been resolved.

1. February 12, 2026 at 2:47 PM UTCinvestigating

   We are currently investigating this issue.

2. February 12, 2026 at 2:56 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. February 12, 2026 at 3:52 PM UTCresolved

   This incident has been resolved.

1. January 13, 2026 at 5:37 PM UTCinvestigating

   Some customers may be experiencing intermittent issues affecting various platform functions, including inbound/outbound calling, message delivery, and agent status synchronization. Our engineering team is actively working on a resolution. In the meantime, agents can manually update their status by clicking the 'Refresh' button within the application.

2. January 13, 2026 at 5:52 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. January 13, 2026 at 5:58 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. January 13, 2026 at 8:38 PM UTCresolved

   This incident has been resolved.

1. November 18, 2025 at 1:41 PM UTCidentified

   The issue is due to a worldwide CloudFlare service incident: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7. Users can go directly to https://dialpad.com/login to sign in. Calling and messaging are unaffected.

2. November 18, 2025 at 2:01 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. November 18, 2025 at 6:03 PM UTCresolved

   The service is fully recovered.

1. September 30, 2025 at 7:28 PM UTCinvestigating

   We are currently investigating this issue.

2. September 30, 2025 at 7:29 PM UTCinvestigating

   We are continuing to investigate this issue.

3. September 30, 2025 at 8:33 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. September 30, 2025 at 9:27 PM UTCresolved

   This incident has been resolved.

1. August 6, 2025 at 9:42 PM UTCidentified

   The issue has been identified and a fix is being implemented.

2. August 6, 2025 at 11:10 PM UTCresolved

   This incident has been resolved.

1. July 22, 2025 at 2:05 AM UTCresolved

   We are currently investigating this issue.