Histórico de interrupções do Phoneburner

1. 21 Here 2026 da 13:43 UTCmonitoring

   Como parte de nosso compromisso contínuo com a segurança de dados e informações, por uma abundância de cautela, estamos implementando uma série de contramedidas de segurança em resposta à vulnerabilidade de segurança amplamente relatada na internet anunciada nas últimas 24 horas. Como parte desse esforço de resposta rápida, alguns usuários podem experimentar a disponibilidade intermitente de nossos serviços. Forneceremos novas atualizações quando este esforço estiver completo.

2. 21 Here 2026 da 15:28 UTCmonitoring

   O trabalho continua em resposta à conhecida vulnerabilidade de segurança da internet divulgada nas últimas 24 horas. À medida que nossas equipes implementam melhorias de segurança, os usuários podem experimentar uma experiência degradada intermitente, enquanto essas mudanças se propagam através de nossos serviços. Agradecemos a sua paciência ao continuarmos a implantar melhorias de segurança e continuaremos a fornecer atualizações.

3. 21 Here 2026 da 16:25 UTCresolved

   Implantamos com sucesso novos patches de segurança e atualizamos nosso ambiente com novas configurações de nossos parceiros de segurança. Acreditamos que os usuários devem experimentar condições operacionais normais. Agradecemos a sua paciência, pois trabalhamos neste processo para garantir nossos serviços e aplicações.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Gouere 2026 da 19:46 UTCidentified

   Estamos a investigar questões do website. Os engenheiros identificaram o problema e estão a trabalhar numa solução.

2. 20 Gouere 2026 da 19:49 UTCmonitoring

   O problema está resolvido. Estamos a acompanhar

3. 20 Gouere 2026 da 19:58 UTCresolved

   O local voltou à operação normal.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Mezheven 2026 da 13:51 UTCinvestigating

   We are investigating a fix.

2. 9 Mezheven 2026 da 14:00 UTCresolved

   This incident has been resolved.

1. 28 Gouere 2025 da 18:20 UTCinvestigating

   We are investigating performance issues with the website.

2. 28 Gouere 2025 da 18:23 UTCmonitoring

   Site performance is improving. We're monitoring.

3. 28 Gouere 2025 da 18:25 UTCresolved

   Site performance is back to normal operation.

1. 23 Gouere 2025 da 20:31 UTCidentified

   We have identified an intermittent issue with the dialer where the buttons don't work as expected. We have identified it as an issue with one of our vendors. We're working closely with them to resolve the issue.

2. 23 Gouere 2025 da 20:51 UTCidentified

   The vendor is still researching the issues on their end.

3. 23 Gouere 2025 da 21:49 UTCmonitoring

   We have started the process of moving all the usage away from the problematic vendor. We are monitoring. We recommend any users experiencing the issues log out of your account and login again to ensure you pickup the new configurations.

4. 23 Gouere 2025 da 21:55 UTCresolved

   Traffic is migrated away from the problematic vendor and we'll continue monitoring.

1. 9 Gouere 2025 da 14:36 UTCinvestigating

   We are investigating issues with the site

2. 9 Gouere 2025 da 14:47 UTCidentified

   We've identified the source of the issue and we're remediating. We're starting to see performance improvements.

3. 9 Gouere 2025 da 15:08 UTCmonitoring

   We are seeing full site performance recovery. We are monitoring.

4. 9 Gouere 2025 da 15:39 UTCresolved

   Site performance has been restored. We've determined that an upstream provider was having performance issues that degraded some aspects of our site. We have mitigated those issue and the site is performing well. We'll continue monitoring.

1. 18 Mezheven 2025 da 18:42 UTCinvestigating

   We are investigating degraded website performance

2. 18 Mezheven 2025 da 18:56 UTCmonitoring

   Engineers have identified the issue and we're seeing performance recover. We're monitoring.

3. 18 Mezheven 2025 da 19:10 UTCresolved

   Site performance has been restored.

1. 16 Mae 2025 da 01:07 UTCinvestigating

   We have identified the issue and are working on a resolution.

2. 16 Mae 2025 da 01:34 UTCidentified

   Engineering team has identified a fix and an update and/or fix should be deployed shortly.

3. 16 Mae 2025 da 01:41 UTCmonitoring

   Calls are completing successfully. We are monitoring the make sure the system is stable.

4. 16 Mae 2025 da 01:49 UTCresolved

   The incident is resolved.

1. 3 Ebrel 2025 da 16:41 UTCinvestigating

   We are investigating site performance issues

2. 3 Ebrel 2025 da 16:53 UTCmonitoring

   We are observing improved performance. The team is continuing to monitor.

3. 3 Ebrel 2025 da 17:03 UTCresolved

   Site performance has been fully restored.

1. 27 Meurzh 2025 da 01:56 UTCinvestigating

   We are investigating the issue.

2. 27 Meurzh 2025 da 02:17 UTCinvestigating

   The team continues to investigate the issue. A new update will come shortly.

3. 27 Meurzh 2025 da 02:36 UTCinvestigating

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

4. 27 Meurzh 2025 da 02:46 UTCmonitoring

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

5. 27 Meurzh 2025 da 03:46 UTCresolved

   This incident has been resolved.

1. 14 Meurzh 2025 da 19:44 UTCinvestigating

   We are investing issues with the site loading slowly.

2. 14 Meurzh 2025 da 19:48 UTCidentified

   We have identified the source of the issue and the team is working on resolution.

3. 14 Meurzh 2025 da 19:58 UTCmonitoring

   We're observing site performance improvements. We're monitoring.

4. 14 Meurzh 2025 da 20:05 UTCresolved

   The site performance has been restored.

1. 28 Cʼhwevrer 2025 da 14:26 UTCidentified

   We have identified an issue with some outbound calls through the dialer. This includes call transfers as well. Engineers are actively working through the issues.

2. 28 Cʼhwevrer 2025 da 14:42 UTCmonitoring

   Issue has been identified and resolved. We are monitoring.

3. 28 Cʼhwevrer 2025 da 14:48 UTCresolved

   Systems are fully operational.

1. 24 Here 2024 da 14:26 UTCinvestigating

   We are currently researching issues related to slow site performance.

2. 24 Here 2024 da 14:38 UTCidentified

   We have identified the source of the issue and are deploying a fix.

3. 24 Here 2024 da 14:41 UTCmonitoring

   A fix has been implemented and performance is recovering. We are monitoring.

4. 24 Here 2024 da 14:46 UTCidentified

   Issues are not resolved. We are triaging a deployment issue.

5. 24 Here 2024 da 14:56 UTCmonitoring

   Fixes are confirmed in good working order. We are monitoring performance.

6. 24 Here 2024 da 15:01 UTCresolved

   Site performance is fully restored and operating normally.

1. 22 Eost 2024 da 12:34 UTCinvestigating

   We are currently investigating an issue with the dialer.

2. 22 Eost 2024 da 12:42 UTCidentified

   We have identified the issue and are working on a fix.

3. 22 Eost 2024 da 12:48 UTCmonitoring

   We are actively resolving the issue and we're starting to see recovery.

4. 22 Eost 2024 da 12:53 UTCresolved

   Dialer has been restored and fully functional.

1. 30 Mae 2024 da 20:49 UTCinvestigating

   We are currently investigating reports of a slow and/or unresponsive site.

2. 30 Mae 2024 da 21:07 UTCinvestigating

   The team is still researching. We'll update again shortly.

3. 30 Mae 2024 da 22:47 UTCmonitoring

   The team believes there is a performance problem with some in-browser integrations. We have disabled that integration and are monitoring performance. We also believe this does not impact everyone.

4. 30 Mae 2024 da 23:16 UTCresolved

   The team has confirmed that the 3rd party library in the browser is in fact driving high CPU and making the browser window unresponsive. The integration has been disabled, and the site is in working as expected. We are closing the incident and the team will continue to monitor.

1. 20 Mae 2024 da 20:44 UTCinvestigating

   We are investigating issues with site performance

2. 20 Mae 2024 da 21:13 UTCresolved

   Site access is fully restored.

1. 13 Mae 2024 da 23:23 UTCinvestigating

   We are experiencing issues the site. The team is researching.

2. 13 Mae 2024 da 23:29 UTCidentified

   We have identified the db instances in the cluster and are fixing.

3. 13 Mae 2024 da 23:33 UTCidentified

   Site is recovering as instances are restored.

4. 13 Mae 2024 da 23:51 UTCmonitoring

   Site is recovered with some indications of degraded performance. The team is still researching and monitoring.

5. 14 Mae 2024 da 00:17 UTCresolved

   Site is fully restored. We will continue to monitor.

1. 13 Mae 2024 da 21:31 UTCinvestigating

   We have noticed degraded performance on the site. The team is researching.

2. 13 Mae 2024 da 21:38 UTCidentified

   The team has identified some problematic instances in out the database cluster. A fix is being worked on now. There is no impact on data - just on site performance.

3. 13 Mae 2024 da 21:52 UTCresolved

   Problematic instances are fixed and site is fully operational.

1. 15 Du 2023 da 21:13 UTCinvestigating

   We are investigating issues with accessing the site.

2. 15 Du 2023 da 21:26 UTCidentified

   The team has identified a potential source cause. We are investigating further.

3. 15 Du 2023 da 21:49 UTCidentified

   The team is still researching. Nothing new to report at the moment.

4. 15 Du 2023 da 21:54 UTCmonitoring

   The team has resolved the root cause and is monitoring.

5. 15 Du 2023 da 22:02 UTCresolved

   This incident is resolved.

1. 9 Here 2023 da 16:53 UTCinvestigating

   We are currently experiencing site issues. We're investgiating

2. 9 Here 2023 da 17:03 UTCidentified

   We have a identified a resource issue and are working on a fix.

3. 9 Here 2023 da 17:12 UTCmonitoring

   Sites are showing improved performance and we are monitoring.

4. 9 Here 2023 da 17:27 UTCresolved

   Systems are fully operational.