Historial de interrupciones de Phoneburner

1. 21 de octubre de 2026 a las 13:43 UTCmonitoring

   Como parte de nuestro compromiso continuo con la seguridad de datos e información, de una gran precaución, estamos desplegando una serie de contramedidas de seguridad en respuesta a la amplia vulnerabilidad de seguridad de Internet anunciada en las últimas 24 horas. Como parte de este rápido esfuerzo de respuesta, algunos usuarios pueden experimentar disponibilidad intermitente de nuestros servicios. Proporcionaremos más actualizaciones cuando este esfuerzo esté completo.

2. 21 de octubre de 2026 a las 15:28 UTCmonitoring

   Continúa el trabajo en respuesta a la conocida vulnerabilidad de seguridad de Internet anunciada en las últimas 24 horas. A medida que nuestros equipos implementan mejoras de seguridad, los usuarios pueden experimentar una experiencia degradada intermitente mientras esos cambios se propagan a través de nuestros servicios. Apreciamos su paciencia ya que seguimos implementando mejoras de seguridad y seguiremos proporcionando actualizaciones.

3. 21 de octubre de 2026 a las 16:25 UTCresolved

   Hemos implementado con éxito nuevos parches de seguridad y actualizado nuestro entorno con nuevas configuraciones de nuestros socios de seguridad. Creemos que los usuarios deben experimentar condiciones de funcionamiento normales. Apreciamos su paciencia ya que hemos trabajado a través de este proceso para asegurar nuestros servicios y aplicaciones.

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

1. 20 de julio de 2026 a las 19:46 UTCidentified

   Estamos investigando los problemas del sitio web. Los ingenieros han identificado la cuestión y están trabajando en una solución.

2. 20 de julio de 2026 a las 19:49 UTCmonitoring

   El asunto está resuelto. Estamos monitoreando

3. 20 de julio de 2026 a las 19:58 UTCresolved

   El sitio está de vuelta a la operación normal.

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

1. 9 de junio de 2026 a las 13:51 UTCinvestigating

   We are investigating a fix.

2. 9 de junio de 2026 a las 14:00 UTCresolved

   This incident has been resolved.

1. 28 de julio de 2025 a las 18:20 UTCinvestigating

   We are investigating performance issues with the website.

2. 28 de julio de 2025 a las 18:23 UTCmonitoring

   Site performance is improving. We're monitoring.

3. 28 de julio de 2025 a las 18:25 UTCresolved

   Site performance is back to normal operation.

1. 23 de julio de 2025 a las 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 de julio de 2025 a las 20:51 UTCidentified

   The vendor is still researching the issues on their end.

3. 23 de julio de 2025 a las 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 de julio de 2025 a las 21:55 UTCresolved

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

1. 9 de julio de 2025 a las 14:36 UTCinvestigating

   We are investigating issues with the site

2. 9 de julio de 2025 a las 14:47 UTCidentified

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

3. 9 de julio de 2025 a las 15:08 UTCmonitoring

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

4. 9 de julio de 2025 a las 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 de junio de 2025 a las 18:42 UTCinvestigating

   We are investigating degraded website performance

2. 18 de junio de 2025 a las 18:56 UTCmonitoring

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

3. 18 de junio de 2025 a las 19:10 UTCresolved

   Site performance has been restored.

1. 16 de mayo de 2025 a las 1:07 UTCinvestigating

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

2. 16 de mayo de 2025 a las 1:34 UTCidentified

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

3. 16 de mayo de 2025 a las 1:41 UTCmonitoring

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

4. 16 de mayo de 2025 a las 1:49 UTCresolved

   The incident is resolved.

1. 3 de abril de 2025 a las 16:41 UTCinvestigating

   We are investigating site performance issues

2. 3 de abril de 2025 a las 16:53 UTCmonitoring

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

3. 3 de abril de 2025 a las 17:03 UTCresolved

   Site performance has been fully restored.

1. 27 de marzo de 2025 a las 1:56 UTCinvestigating

   We are investigating the issue.

2. 27 de marzo de 2025 a las 2:17 UTCinvestigating

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

3. 27 de marzo de 2025 a las 2:36 UTCinvestigating

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

4. 27 de marzo de 2025 a las 2:46 UTCmonitoring

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

5. 27 de marzo de 2025 a las 3:46 UTCresolved

   This incident has been resolved.

1. 14 de marzo de 2025 a las 19:44 UTCinvestigating

   We are investing issues with the site loading slowly.

2. 14 de marzo de 2025 a las 19:48 UTCidentified

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

3. 14 de marzo de 2025 a las 19:58 UTCmonitoring

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

4. 14 de marzo de 2025 a las 20:05 UTCresolved

   The site performance has been restored.

1. 28 de febrero de 2025 a las 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 de febrero de 2025 a las 14:42 UTCmonitoring

   Issue has been identified and resolved. We are monitoring.

3. 28 de febrero de 2025 a las 14:48 UTCresolved

   Systems are fully operational.

1. 24 de octubre de 2024 a las 14:26 UTCinvestigating

   We are currently researching issues related to slow site performance.

2. 24 de octubre de 2024 a las 14:38 UTCidentified

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

3. 24 de octubre de 2024 a las 14:41 UTCmonitoring

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

4. 24 de octubre de 2024 a las 14:46 UTCidentified

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

5. 24 de octubre de 2024 a las 14:56 UTCmonitoring

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

6. 24 de octubre de 2024 a las 15:01 UTCresolved

   Site performance is fully restored and operating normally.

1. 22 de agosto de 2024 a las 12:34 UTCinvestigating

   We are currently investigating an issue with the dialer.

2. 22 de agosto de 2024 a las 12:42 UTCidentified

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

3. 22 de agosto de 2024 a las 12:48 UTCmonitoring

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

4. 22 de agosto de 2024 a las 12:53 UTCresolved

   Dialer has been restored and fully functional.

1. 30 de mayo de 2024 a las 20:49 UTCinvestigating

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

2. 30 de mayo de 2024 a las 21:07 UTCinvestigating

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

3. 30 de mayo de 2024 a las 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 de mayo de 2024 a las 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 de mayo de 2024 a las 20:44 UTCinvestigating

   We are investigating issues with site performance

2. 20 de mayo de 2024 a las 21:13 UTCresolved

   Site access is fully restored.

1. 13 de mayo de 2024 a las 23:23 UTCinvestigating

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

2. 13 de mayo de 2024 a las 23:29 UTCidentified

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

3. 13 de mayo de 2024 a las 23:33 UTCidentified

   Site is recovering as instances are restored.

4. 13 de mayo de 2024 a las 23:51 UTCmonitoring

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

5. 14 de mayo de 2024 a las 0:17 UTCresolved

   Site is fully restored. We will continue to monitor.

1. 13 de mayo de 2024 a las 21:31 UTCinvestigating

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

2. 13 de mayo de 2024 a las 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 de mayo de 2024 a las 21:52 UTCresolved

   Problematic instances are fixed and site is fully operational.

1. 15 de noviembre de 2023 a las 21:13 UTCinvestigating

   We are investigating issues with accessing the site.

2. 15 de noviembre de 2023 a las 21:26 UTCidentified

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

3. 15 de noviembre de 2023 a las 21:49 UTCidentified

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

4. 15 de noviembre de 2023 a las 21:54 UTCmonitoring

   The team has resolved the root cause and is monitoring.

5. 15 de noviembre de 2023 a las 22:02 UTCresolved

   This incident is resolved.

1. 9 de octubre de 2023 a las 16:53 UTCinvestigating

   We are currently experiencing site issues. We're investgiating

2. 9 de octubre de 2023 a las 17:03 UTCidentified

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

3. 9 de octubre de 2023 a las 17:12 UTCmonitoring

   Sites are showing improved performance and we are monitoring.

4. 9 de octubre de 2023 a las 17:27 UTCresolved

   Systems are fully operational.