Historial de interrupciones de Envoy

1. 4 de septiembre de 2026 a las 12:13 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 4 de septiembre de 2026 a las 12:14 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 4 de septiembre de 2026 a las 12:17 UTCidentified

   Hemos identificado la causa como un problema con nuestro proveedor de correo electrónico de terceros, cuyos mensajes a los servicios de correo de Microsoft están siendo frustrados. Esto afecta a los correos electrónicos enviados a los destinatarios en servicios de Microsoft, como Microsoft 365 y Outlook, incluyendo los correos electrónicos de verificación de entrada, invitación y notificación de visitantes. Los mensajes afectados son apagados y retrigados automáticamente en lugar de perdidos, y deben llegar una vez que se restablezca la entrega normal. Según nuestra investigación, el correo electrónico a todos los demás destinatarios no es afectado, y no se requiere ninguna acción de los clientes. Nuestro proveedor está investigando activamente; publicaremos otra actualización dentro de la hora o antes si algo cambia.

4. 4 de septiembre de 2026 a las 14:06 UTCmonitoring

   Nuestro proveedor de correo electrónico de terceros está reportando la recuperación en la entrega a los servicios de correo de Microsoft. Estamos monitoreando activamente la entrega y confirmaremos una vez que hayamos comprobado que los mensajes están fluyendo normalmente.

5. 4 de septiembre de 2026 a las 14:55 UTCresolved

   Esta cuestión se ha resuelto

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

1. 27 de agosto de 2026 a las 17:48 UTCidentified

   Se ha identificado y corregido un problema que causa retrasos en el oleoducto de entrada automática. Estamos trabajando para monitorear y acelerar el procesamiento para traer el procesamiento de vuelta a tiempo real, en breve.

2. 27 de agosto de 2026 a las 19:11 UTCmonitoring

   Estamos viendo que los eventos lleguen a tiempo real.

3. 27 de agosto de 2026 a las 20:32 UTCresolved

   El registro automático ha sido procesado en tiempo real y ha permanecido estable. Este incidente está resuelto.

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

1. 29 de julio de 2026 a las 20:19 UTCinvestigating

   Actualmente estamos experimentando un problema relacionado con CSS que afecta muchas páginas en el panel de control. Debido a este problema, los diseños de páginas se rompen, lo que puede afectar la usabilidad y la visualización de elementos de la interfaz de usuario. Nuestro equipo ha identificado el tema y está trabajando activamente en una solución. Proporcionaremos actualizaciones a medida que se disponga de más información.

2. 29 de julio de 2026 a las 20:26 UTCidentified

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

3. 29 de julio de 2026 a las 20:33 UTCresolved

   Identificamos y arreglamos la cuestión. La página ahora está renderizando como se espera, y seguimos monitoreando.

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

1. 2 de julio de 2026 a las 14:03 UTCinvestigating

   We are currently investigating an issue that is causing the Envoy dashboard to be unavailable. Our team is working to identify the root cause. We apologize for the inconvenience and appreciate your patience while our team works on restoring the functionality. For any further questions, please contact Envoy Support via [email protected]

2. 2 de julio de 2026 a las 14:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 de julio de 2026 a las 14:20 UTCresolved

   Resolved: The dashboard outage has been resolved. Dashboard access and functionality have been restored, and users should now be able to load dashboards and perform dashboard-related actions normally.

1. 2 de julio de 2026 a las 12:46 UTCinvestigating

   Actualmente estamos experimentando un problema donde los correos electrónicos no están siendo entregados. Nuestro equipo está investigando activamente y compartirá actualizaciones a medida que aprendamos más.

2. 2 de julio de 2026 a las 14:14 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 2 de julio de 2026 a las 14:19 UTCresolved

   Resuelto: Se ha resuelto el problema de la entrega de correo electrónico. Los correos electrónicos están siendo enviados con éxito, y los usuarios deben recibir cualquier nueva notificación de correo electrónico como se espera.

4. 15 de julio de 2026 a las 21:35 UTCpostmortem

   El 2 de julio de 2026, comenzando alrededor de las 1:30 AM PDT, el servicio de notificación entró en un estado degradado, retrasando la entrega de notificaciones de emergencia, invitaciones de reuniones y otros mensajes transaccionales. Una actualización reciente de software introdujo un error de configuración que impidió que el servicio procesara correctamente los mensajes salientes, y un atraso significativo construido durante varias horas. El monitoreo captó el tema poco después de que los informes entraran, y la ingeniería lo resolvió revertiendo a la versión estable anterior. Todas las notificaciones solicitadas fueron entregadas por 7:13 AM PDT Se ha organizado un post mortem interno para analizar el incidente y tomar nota de aprendizajes clave y temas de acción. Si tiene alguna pregunta o necesita información adicional, no dude en ponerse en contacto con nuestro equipo de Atención al Cliente a través de [[email protected]](mailto:[email protected]) o ponerse en contacto con su gestor de cuenta dedicado.

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

1. 22 de junio de 2026 a las 14:35 UTCinvestigating

   We are currently investigating a low amount of elevated errors on dashboard.envoy.com.

2. 22 de junio de 2026 a las 14:47 UTCresolved

   This incident has been resolved.

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

   We are currently investigating an issue that is causing the Envoy dashboard to be unavailable. Our team is working to identify the root cause. We apologize for the inconvenience and appreciate your patience while our team works on restoring the functionality. For any further questions, please contact Envoy Support via [email protected]

2. 11 de junio de 2026 a las 14:15 UTCmonitoring

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

3. 11 de junio de 2026 a las 15:00 UTCresolved

   This incident has been resolved.

4. 15 de junio de 2026 a las 17:18 UTCpostmortem

   On June 11, 2026, at around 6:37 AM PDT, a backend database reached its storage capacity, causing the customer dashboard and mobile applications to become unresponsive. The outage was caused by a data synchronization task that failed to clear old logs, leading to a steady buildup that eventually saturated the database volume. Our engineering team restored service by manually expanding the database storage and clearing the stalled synchronization task to reclaim space. While the dashboard recovered quickly, mobile app access was restored shortly after once the system status was fully cleared. We have since implemented more aggressive alerting for database storage levels to ensure our teams are paged immediately if a similar buildup occurs.  An internal post-mortem has been organized to analyze the incident and note key learnings and action items. If you have any questions or require additional information, please don't hesitate to contact our Customer Support team via [[email protected]](mailto:[email protected]) or contact your dedicated account manager.

1. 11 de mayo de 2026 a las 17:35 UTCinvestigating

   We are currently investigating an issue causing intermittent slow performance with the Envoy dashboard. Some users may experience delays or difficulty accessing certain features. Our team is actively working to identify the root cause and implement a fix. We apologize for the inconvenience and appreciate your patience while we work to restore full functionality. For any further questions, please contact Envoy Support via [email protected]

2. 11 de mayo de 2026 a las 18:02 UTCinvestigating

   We are continuing to investigate this issue.

3. 11 de mayo de 2026 a las 18:03 UTCresolved

   This incident has been resolved.

4. 15 de mayo de 2026 a las 19:42 UTCpostmortem

   On May 11 at around 10:21 AM PDT, a scheduled background job combined with high traffic patterns pushed our application database past its capacity, causing a performance bottleneck that made the Envoy Dashboard slow and unresponsive. Our team identified the responsible job and optimized and scaled the database to restore dashboard performance. An internal post-mortem has been organized to analyze the incident and note key learnings and action items. If you have any questions or require additional information, please don't hesitate to contact our Customer Support team via [[email protected]](mailto:[email protected]) or contact your dedicated account manager.

1. 8 de mayo de 2026 a las 1:16 UTCinvestigating

   We are currently looking into the issue to identify the root cause.

2. 8 de mayo de 2026 a las 1:40 UTCmonitoring

   The issue has been identified, and we’re seeing improvements across all product functionality.

3. 8 de mayo de 2026 a las 1:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 8 de mayo de 2026 a las 3:17 UTCresolved

   This incident has been resolved.

5. 21 de mayo de 2026 a las 1:39 UTCpostmortem

   On May 7, 2026, at around 5:36 PM PDT, a thermal event at an AWS data center caused a power loss to the hardware in one of the regions where we host our database. AWS continued to report the database as healthy despite it being unavailable, causing our application to repeatedly attempt connections to an unreachable database, which brought the Envoy Dashboard down. Our team restored service by rerouting database traffic to a healthy region. An internal post-mortem has been organized to analyze the incident and note key learnings and action items. If you have any questions or require additional information, please don't hesitate to contact our Customer Support team via [[email protected]](mailto:[email protected]) or contact your dedicated account manager.

1. 12 de marzo de 2026 a las 14:51 UTCinvestigating

   We are investigating issues impacting auto-sign in.

2. 12 de marzo de 2026 a las 15:13 UTCidentified

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

3. 12 de marzo de 2026 a las 16:01 UTCresolved

   This incident has been resolved.

4. 18 de mayo de 2026 a las 19:16 UTCpostmortem

   On March 11 at around 11:24 AM PST, an authentication issue caused sign-in events from integrations like WiFi, badge readers, and SSO to be queued instead of processed. Our team resolved the issue and replayed the queued events to ensure all impacted data was recovered. An internal post-mortem has been organized to analyze the incident and note key learnings and action items. If you have any questions or require additional information, please don't hesitate to contact our Customer Support team via [[email protected]](mailto:[email protected]) or contact your dedicated account manager.

1. 27 de enero de 2026 a las 16:50 UTCinvestigating

   We are currently investigating the issue.

2. 27 de enero de 2026 a las 17:34 UTCmonitoring

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

3. 27 de enero de 2026 a las 17:34 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 27 de enero de 2026 a las 17:59 UTCresolved

   This incident has been resolved.

1. 27 de enero de 2026 a las 16:47 UTCresolved

   We are currently experiencing slower loading time with our Maps. Our engineering team is currently investigating the root cause of the issue.

1. 26 de enero de 2026 a las 16:55 UTCinvestigating

   We are currently investigating this issue.

2. 26 de enero de 2026 a las 16:56 UTCinvestigating

   We are continuing to investigate this issue.

3. 26 de enero de 2026 a las 17:59 UTCresolved

   We are currently experiencing slower loading time with our . Our engineering team is currently investigating the root cause of the issue.

1. 23 de enero de 2026 a las 23:07 UTCinvestigating

   We are currently investigating issues related to Visitors device connectivity that may be impacting badge printing functionality for some customers. Our team is actively working to identify the root cause and assess for a resolution; updates will be shared as more information becomes available. We appreciate your understanding - for any additional questions or feedback, please contact the Customer Support team via live chat or [email protected]!

2. 24 de enero de 2026 a las 2:24 UTCinvestigating

   We continue to investigate reports of customers experiencing difficulties printing badges in the Envoy Kiosk App. Our team has identified a potential code issue that may be contributing to this behavior and is working to confirm the root cause. We will provide another update as soon as we have more information.

3. 25 de enero de 2026 a las 2:35 UTCmonitoring

   Envoy Kiosk v5.59.0 has been released to the App Store with changes aimed at stabilizing the printer functionality issues. We are monitoring the situation to confirm the fix is working as expected.

4. 28 de enero de 2026 a las 22:32 UTCresolved

   The issue has been resolved, and printer functionality has been stable with the new update.

1. 16 de enero de 2026 a las 12:58 UTCinvestigating

   We are currently investigating this issue.

2. 16 de enero de 2026 a las 13:21 UTCidentified

   Team has identified the problem and is working on the solution.

3. 16 de enero de 2026 a las 13:43 UTCmonitoring

   A fix has been deployed, and room devices are gradually returning online.

4. 16 de enero de 2026 a las 14:43 UTCresolved

   The issue has been resolved. Rooms devices are up and running and Envoy dashboard is operational.

1. 15 de enero de 2026 a las 17:41 UTCresolved

   Engineers have identified the root cause and deployed the fix. The issue was fully resolved at 9:35am

1. 2 de enero de 2026 a las 17:57 UTCinvestigating

   We are currently investigating this issue.

2. 2 de enero de 2026 a las 19:43 UTCinvestigating

   We are continuing to investigate this issue.

3. 2 de enero de 2026 a las 19:45 UTCmonitoring

   We have deployed version 4.55.2 of the Envoy Visitors Kiosk to the App Store. Updating to this version of the app should fix the problem.

4. 3 de enero de 2026 a las 0:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 3 de enero de 2026 a las 0:18 UTCresolved

   This incident has been resolved.

1. 5 de diciembre de 2025 a las 9:03 UTCinvestigating

   We are seeing elevated error rates on attempting to access the Envoy site. We are currently investigating issues with Cloudflare: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q We will update when we have more information.

2. 5 de diciembre de 2025 a las 9:09 UTCinvestigating

   We are continuing to investigate this issue.

3. 5 de diciembre de 2025 a las 9:14 UTCmonitoring

   We are seeing some portions of the site recover.

4. 5 de diciembre de 2025 a las 9:19 UTCmonitoring

   We are seeing the site recover to full operational status. We will continue monitoring.

5. 5 de diciembre de 2025 a las 9:32 UTCresolved

   This incident has been resolved.

1. 17 de noviembre de 2025 a las 16:16 UTCinvestigating

   We are experiencing issues with our Slack integration. Both installation and notification sending via Slack are currently unavailable.

2. 17 de noviembre de 2025 a las 16:22 UTCidentified

   We have identified the issue and provided a fix.

3. 17 de noviembre de 2025 a las 16:26 UTCresolved

   The issue with our Slack integration has been resolved. Customers should now be able to install Slack on Envoy and use the notification feature.

1. 14 de noviembre de 2025 a las 3:15 UTCinvestigating

   We are currently investigating the issue.

2. 14 de noviembre de 2025 a las 3:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 14 de noviembre de 2025 a las 3:47 UTCidentified

   We’ve identified a potential root cause. Rooms devices are gradually recovering and should automatically re-pair.

4. 14 de noviembre de 2025 a las 3:58 UTCmonitoring

   We’ve deployed a fix and are monitoring for all devices to fully recover.

5. 14 de noviembre de 2025 a las 4:07 UTCresolved

   The issue with rooms devices has been resolved.