Loading
Applying language and content...
Loading status page
Checking service and reports...
51 Broadvoice incidents · Gwengolo 2021 — official updates, affected components, duration and resolution details.
Estamos actualmente a investigar esta questão.
Isto foi publicado em erro e não há problemas conhecidos no momento atual.
Traduzido automaticamente da atualização oficial do incidente.
Estamos actualmente a investigar esta questão.
Foi implementada uma correção e estamos monitorando os resultados.
Este incidente foi resolvido.
Traduzido automaticamente da atualização oficial do incidente.
Estamos actualmente a investigar esta questão.
us-l1-cloud1-g3 não está disponível, é por isso que temos os problemas intermitentes
O cliente confirmou que o problema está resolvido. Ainda estou a trabalhar na "nós-la-coresite-cloud1-g3-vpn".
Recebemos um relatório de problemas de acesso intermitentes com a plataforma GoContact. Após investigação de nossa equipe de engenharia, identificamos que um dos servidores da GoContact havia parado e ficado sem resposta, o que estava causando os problemas relatados. O servidor afetado foi removido da plataforma, e o sistema agora está estável sem mais interrupções observadas. Nesse momento, o incidente não parece estar relacionado à intervenção planejada realizada anteriormente.
Traduzido automaticamente da atualização oficial do incidente.
Estamos actualmente a investigar esta questão.
O problema só está acontecendo com o APP móvel. Não foram agendadas intervenções. Identificamos através dos LOGs que alguns usuários podem fazer login, por isso não está afetando todos os clientes. Podemos fazer login com o login da conta da equipe de suporte.
A equipe de suporte é capaz de replicar, mas a equipe DEV não é capaz de replicar com o mesmo usuário. Vemos login bem sucedido de vários usuários. Solicitando testes ao cliente. Pedidos de login da equipe DEV estão atingindo NGINX. As solicitações da equipe de suporte não estão alcançando o NGINX. A equipe de suporte recebe o mesmo erro ao tentar com a rede 5G. A equipe de DEV tentará replicar o domínio para ver LOGs ao vivo na tela e compartilhar os resultados com a equipe assim que isso for feito.
Ainda estamos esperando que a equipe de DEV replique o domínio para ver os LOGs ao vivo na tela e compartilhe os resultados para que possamos continuar a solução de problemas.
A equipe de DEV continua tendo dificuldades para entender a causa raiz, mudando o aplicativo para ter mais detalhes sobre o erro. Novos testes começaram a tentar reproduzir o erro enquanto a equipe DEV está tentando compilar outra versão APP.
Equipes de DEV continuam a tentar determinar a causa básica do problema. Pode estar relacionado com certificados NOS, já há uma intervenção programada para esta noite para atualizar alguns certificados, a fim de ter corrigir os certificados em falta na cadeia confiável. Ainda não está claro que a intervenção desta noite irá resolver esta questão actual.
Acabamos de atualizar o celular Android para a versão 16 e agora somos capazes de fazer login usando o APP móvel em um dispositivo que não foi capaz de acessar anteriormente. Reduzimos o erro... agora só está acontecendo com dispositivos Android com versão 15 ou inferior. Estamos tomando esta abordagem como um trabalho ao redor, a intervenção de hoje à noite deve ser capaz de corrigir o erro em todos os outros dispositivos caso contrário, vamos precisar continuar a solução de problemas.
Aguardando a intervenção desta noite (Nos Certificates Updates) para ver se isso está resolvendo o problema para antigos dispositivos Android com a versão 15 ou inferior.
Foi implementada uma correção e estamos monitorando os resultados.
Este incidente foi resolvido. A intervenção que ocorreu para atualizar os Certificados NOS resolveu o problema em todos os dispositivos.
Traduzido automaticamente da atualização oficial do incidente.
Atualmente estamos monitorando uma falha generalizada da AWS que pode estar impactando o desempenho de alguns de nossos serviços. Enquanto nossos sistemas permanecem operacionais, os clientes podem experimentar atrasos intermitentes ou desempenho degradado em determinadas áreas. Nossa equipe de engenharia está trabalhando ativamente para mitigar qualquer impacto e está acompanhando de perto os esforços de recuperação da AWS. Forneceremos atualizações à medida que mais informações estiverem disponíveis. Agradecemos a sua paciência e compreensão.
Foi implementada uma correção e estamos monitorando os resultados.
Este incidente foi resolvido.
Traduzido automaticamente da atualização oficial do incidente.
We're currently experiencing issues with the SMS service on B-Hive. Our engineering teams are working to resolve it as quickly as possible.
The cause has been determined, and the engineering team is now in the process of fixing it.
The resolution is in progress and will be ready soon.
The issue has been resolved and the fix applied. We’re currently monitoring the service to ensure continued stability.
All services are fully operational and stable.
Authentication issues in voice and the platform
We are currently investigating delays in sending and receiving faxes on the Bhive platform.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating reports of long post dial delay from Bhive..
As of 2:35 PM PST today we have resolved the issue with PDD in our network.
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.
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.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Details: An issue impacting Cloud07 has been identified. Current Impact: Cloud Down We are committed to restoring normal service operations as quickly as possible.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
Difficulties were identified with the ISP peering, the traffic was shifted away from that peer. We're still in contact with the ISP.
This incident has been resolved.
"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.
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.
This incident has been resolved.
Customers utilizing iOS are having issues with receiving inbound calls. Outbound calls are working for these customers.
Customers can use the app as long as it is in the foreground and active. We are working to resolve this issue.
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.
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.
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.
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
Resetting the data source for the dashboards has restored everything to normal.
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
Degradation in a service instance was causing intermittent issues with loading contact information.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Details: We are currently receiving some complaints regarding metallic voice quality and performance fluctuations on the platform, and we are currently investigating them.
Details: Services restarted. All servers are operating normally.