Historial de interrupciones de Broadvoice

1. July 14, 2026 at 2:25 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a la recuperación de llamadas estacionadas en b-Hive para un escenario específico en una región. Nuestro equipo de ingeniería está trabajando activamente para identificar la causa raíz y restaurar la funcionalidad normal lo antes posible.

2. July 14, 2026 at 2:40 PM UTCidentified

   Hemos identificado el tema, y nuestro equipo de ingeniería está trabajando activamente para resolverlo.

3. July 14, 2026 at 2:57 PM UTCidentified

   Nuestro equipo de ingeniería ha implementado una solución. El servicio debe ser restaurado y seguimos vigilando la situación.

4. July 14, 2026 at 3:00 PM UTCmonitoring

   Estamos monitoreando activamente el servicio para confirmar que sigue siendo estable y está funcionando como se espera

5. July 14, 2026 at 3:39 PM UTCresolved

   El incidente está resuelto.

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

1. July 13, 2026 at 11:47 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 14, 2026 at 12:05 AM UTCresolved

   Esto fue publicado en error y no hay problemas conocidos en el momento actual.

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

1. January 13, 2026 at 9:57 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. January 13, 2026 at 10:18 PM UTCmonitoring

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

3. January 14, 2026 at 12:36 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. January 7, 2026 at 1:33 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. January 7, 2026 at 1:40 PM UTCidentified

   us-l1-cloud1-g3 no está disponible, por eso tenemos los problemas intermitentes

3. January 7, 2026 at 2:03 PM UTCmonitoring

   El cliente confirmó que el problema está resuelto. Todavía trabajando en us-la-coresite-cloud1-g3-vpn.

4. January 7, 2026 at 2:26 PM UTCresolved

   Recibimos un informe de problemas de acceso intermitente con la plataforma GoContact. Después de la investigación de nuestro equipo de ingeniería, identificamos que uno de los servidores GoContact se había estancado y se había vuelto poco responsable, lo que estaba causando los problemas reportados. El servidor afectado ha sido eliminado de la plataforma, y el sistema ahora está estable sin más interrupciones observadas. En este momento, el incidente no parece estar relacionado con la intervención planeada realizada anteriormente.

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

1. January 5, 2026 at 12:43 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. January 5, 2026 at 12:56 PM UTCidentified

   El problema sólo está sucediendo con el APP móvil. No hubo intervenciones programadas. Hemos identificado a través de las LOGs que algunos usuarios pueden acceder, por lo que no está afectando a todos los clientes. Somos capaces de iniciar sesión con el login de la cuenta de equipo de Soporte.

3. January 5, 2026 at 1:18 PM UTCidentified

   El equipo de soporte es capaz de replicar pero el equipo DEV no es capaz de replicar con el mismo usuario. Vemos el acceso exitoso de varios usuarios. Solicitar pruebas al cliente. Las solicitudes de ingreso del equipo DEV están llegando a NGINX. Las solicitudes del equipo de apoyo no llegan a NGINX. El equipo de soporte recibe el mismo error al intentar con la red 5G. El equipo DEV intentará replicar el dominio para ver LOGs en vivo en la pantalla y compartir los resultados con el equipo una vez que esto se haga.

4. January 5, 2026 at 2:12 PM UTCidentified

   Aún estamos esperando que el equipo DEV repita el dominio para ver las LOGs en vivo en la pantalla y compartir los resultados para que podamos continuar la solución de problemas.

5. January 5, 2026 at 3:16 PM UTCidentified

   El equipo DEV sigue teniendo dificultades para entender la causa raíz, cambiando la aplicación para tener más detalles sobre el error. Las nuevas pruebas han comenzado a intentar reproducir el error mientras que el equipo DEV está tratando de compilar otra versión APP.

6. January 5, 2026 at 4:31 PM UTCidentified

   Los equipos DEV siguen tratando de determinar la causa raíz del problema. Podría estar relacionado con certificados NOS, ya hay una intervención programada para esta noche para actualizar algunos certificados con el fin de fijar los certificados que faltan en la cadena de confianza. Aún no está claro que la intervención de esta noche resolverá este problema actual.

7. January 5, 2026 at 5:55 PM UTCidentified

   Acabamos de actualizar el teléfono móvil Android a la versión 16 y ahora somos capaces de iniciar sesión utilizando el APP móvil en un dispositivo que no era capaz de acceder previamente. Hemos reducido el error... ahora sólo está sucediendo con dispositivos Android con la versión 15 o inferior. Estamos tomando este enfoque como un trabajo alrededor, la intervención de esta noche debe ser capaz de corregir el error en todos los otros dispositivos de lo contrario tendremos que continuar la solución de problemas.

8. January 5, 2026 at 7:47 PM UTCidentified

   Esperando la intervención de esta noche (Noticias de certificados de NOSOTROS) para ver si esto es resolver el problema para dispositivos Android antiguos con la versión 15 o inferior.

9. January 6, 2026 at 9:45 AM UTCmonitoring

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

10. January 6, 2026 at 10:46 AM UTCresolved

    Este incidente ha sido resuelto. La intervención que tuvo lugar para actualizar los certificados NOS solucionó el problema en todos los dispositivos.

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

1. October 20, 2025 at 7:58 PM UTCidentified

   Actualmente estamos monitoreando una amplia salida de AWS que puede afectar el desempeño de algunos de nuestros servicios. Mientras nuestros sistemas siguen funcionando, los clientes pueden experimentar retrasos intermitentes o rendimiento degradado en ciertas áreas. Nuestro equipo de ingeniería está trabajando activamente para mitigar cualquier impacto y está siguiendo de cerca los esfuerzos de recuperación de AWS. Proporcionaremos actualizaciones a medida que se disponga de más información. Apreciamos su paciencia y comprensión.

2. October 21, 2025 at 1:53 AM UTCmonitoring

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

3. October 21, 2025 at 2:37 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 22, 2025 at 2:44 PM UTCinvestigating

   We're currently experiencing issues with the SMS service on B-Hive. Our engineering teams are working to resolve it as quickly as possible.

2. July 22, 2025 at 2:55 PM UTCidentified

   The cause has been determined, and the engineering team is now in the process of fixing it.

3. July 22, 2025 at 3:09 PM UTCidentified

   The resolution is in progress and will be ready soon.

4. July 22, 2025 at 3:12 PM UTCmonitoring

   The issue has been resolved and the fix applied. We’re currently monitoring the service to ensure continued stability.

5. July 22, 2025 at 3:27 PM UTCresolved

   All services are fully operational and stable.

1. April 1, 2025 at 8:30 AM UTCresolved

   Authentication issues in voice and the platform

1. March 28, 2025 at 5:10 PM UTCinvestigating

   We are currently investigating delays in sending and receiving faxes on the Bhive platform.

2. March 28, 2025 at 5:10 PM UTCidentified

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

3. March 28, 2025 at 5:40 PM UTCresolved

   This incident has been resolved.

1. December 17, 2024 at 9:15 PM UTCinvestigating

   We are currently investigating reports of long post dial delay from Bhive..

2. December 18, 2024 at 12:18 AM UTCresolved

   As of 2:35 PM PST today we have resolved the issue with PDD in our network.

1. September 3, 2024 at 6:09 PM UTCidentified

   Orange, one of our telecommunications providers in Spain, is currently experiencing a major voice service outage. We are in direct contact with them and are working to resolve the issue as quickly as possible.

2. September 3, 2024 at 10:04 PM UTCresolved

   We have received confirmation from our provider Orange that the situation has been resolved. After conducting tests, we can confirm that the voice service through Orange is functioning normally.

1. August 8, 2024 at 1:25 PM UTCinvestigating

   We are currently investigating this issue.

2. August 8, 2024 at 1:28 PM UTCinvestigating

   We are continuing to investigate this issue.

3. August 8, 2024 at 1:29 PM UTCmonitoring

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

4. August 8, 2024 at 2:55 PM UTCresolved

   This incident has been resolved.

1. July 24, 2024 at 4:12 PM UTCinvestigating

   Details: We have become aware of a potential issue affecting the quality of service. Our team is currently investigating to determine the cause and scope of this issue. Further updates will be provided as more information becomes available.

2. July 24, 2024 at 6:40 PM UTCidentified

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

3. July 25, 2024 at 2:09 PM UTCmonitoring

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

4. August 1, 2024 at 1:13 PM UTCresolved

   This incident has been resolved.

1. July 23, 2024 at 7:24 PM UTCinvestigating

   Details: An issue impacting Cloud07 has been identified. Current Impact: Cloud Down We are committed to restoring normal service operations as quickly as possible.

2. July 23, 2024 at 7:25 PM UTCidentified

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

3. July 23, 2024 at 7:27 PM UTCmonitoring

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

4. July 23, 2024 at 7:54 PM UTCresolved

   This incident has been resolved.

1. July 12, 2024 at 10:56 PM UTCinvestigating

   Details: We have become aware of a potential issue slowness on GoContact platform at all LATAM Clouds. Our team is currently investigating to determine the cause and scope of this issue. Further updates will be provided as more information becomes available. Initial Impact Assessment: Slowness on GoContact platform Actions Initiated: - Incident Response Team engaged - Initial diagnostics commenced

2. July 12, 2024 at 11:11 PM UTCidentified

   Difficulties were identified with the ISP peering, the traffic was shifted away from that peer. We're still in contact with the ISP.

3. July 22, 2024 at 2:10 PM UTCresolved

   This incident has been resolved.

1. July 9, 2024 at 5:38 PM UTCinvestigating

   "Broadvoice engineers are investigating an incident in which some inbound calls from the AT&T Network, whose destination is an off-network number associated with one of our upstream carriers, may not be completed as expected. The upstream carrier has confirmed they are experiencing intermittent issues and working with AT&T to fully resolve this. They do not currently have an estimated time of resolution but are actively working to ensure it is cared for. We will provide an update within the next two hours or upon receiving an update from the carrier.

2. July 9, 2024 at 11:17 PM UTCidentified

   Our upstream carrier’s engineering teams have identified the source of this incident as an off-network industry condition. They are continuing to engage with their vendors to ensure full resolution. The issue is limited to inbound calls from the AT&T network whose destination is an off-network number associated with the upstream carrier. We will continue to monitor and provide an update upon receiving an update from the carrier.

3. July 12, 2024 at 4:37 PM UTCresolved

   This incident has been resolved.

1. June 25, 2024 at 9:07 PM UTCinvestigating

   Customers utilizing iOS are having issues with receiving inbound calls. Outbound calls are working for these customers.

2. June 25, 2024 at 10:59 PM UTCidentified

   Customers can use the app as long as it is in the foreground and active. We are working to resolve this issue.

3. June 26, 2024 at 6:19 AM UTCidentified

   Our engineering team is continuing to work to fully resolve the issue with push notifications on the iOS mobile application. Customers can use the app as long as it remains in the foreground and is active. We are working to resolve this issue as soon as possible. We appreciate your patience and apologize for any inconvenience.

4. June 26, 2024 at 5:34 PM UTCidentified

   Our engineering team is working to fully resolve the push notification issue on the iOS app. The app will function properly as long as it is open and active. We are addressing this as quickly as possible and appreciate your patience. We apologize for any inconvenience.

5. June 27, 2024 at 4:39 PM UTCresolved

   A new iOS app based on the previous version has been released to the App store. Our internal testing has shown that incoming call push notifications are now working after updating with latest app available (listed as version 21.11.02) in the App store. Please be advised that if only updating the app does not resolve the issue, then proceed to remove and reinstall the app from the App store.

1. June 25, 2024 at 8:21 AM UTCinvestigating

   Details: Dashboards have incoherent information about agent states. Initial Impact Assessment: Dashboards is presenting old information Actions Initiated: - Incident Response Team engaged - Initial diagnostics commenced

2. June 25, 2024 at 8:36 AM UTCresolved

   Resetting the data source for the dashboards has restored everything to normal.

1. June 22, 2024 at 7:44 PM UTCinvestigating

   Details: We have become aware of a potential issue affecting North America :: GoContact [US Cloud4]. Our team is currently investigating to determine the cause and scope of this issue. Further updates will be provided as more information becomes available. Initial Impact Assessment: Client info is not showing in certain calls even after cleaning cookies and incognito mode. We're on call with client at least 3 operations are presenting the same issue. Actions Initiated: - Incident Response Team engaged - Initial diagnostics commenced

2. June 22, 2024 at 7:58 PM UTCresolved

   Degradation in a service instance was causing intermittent issues with loading contact information.

1. June 10, 2024 at 3:05 PM UTCinvestigating

   We are currently investigating an issue where, when using Dial By Name, the caller is hearing multiple beeps instead of the prompt asking to dial the user's name.

2. June 10, 2024 at 4:17 PM UTCmonitoring

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

3. June 20, 2024 at 1:25 AM UTCresolved

   This incident has been resolved.