Störungsverlauf von Envoy

1. 4. September 2026 um 12:13 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 4. September 2026 um 12:14 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 4. September 2026 um 12:17 UTCidentified

   Wir haben die Ursache als Problem mit unserem Drittanbieter von E-Mails identifiziert, dessen Nachrichten an von Microsoft gehostete E-Mail-Dienste derzeit gedrosselt werden. Dies betrifft E-Mails von Envoy, die an Empfänger von Microsoft-Diensten wie Microsoft 365 und Outlook gesendet werden - einschließlich E-Mails zur Anmeldeüberprüfung, Einladung und Besucherbenachrichtigung. Betroffene Nachrichten werden automatisch in die Warteschlange gestellt und wiederholt, anstatt verloren zu gehen, und sollten ankommen, sobald die normale Lieferung wiederhergestellt ist. Nach unserer Untersuchung ist die E-Mail an alle anderen Empfänger unberührt und es sind keine Maßnahmen von Kunden erforderlich. Unser Anbieter untersucht aktiv; Wir werden innerhalb einer Stunde oder früher ein weiteres Update veröffentlichen, wenn sich etwas ändert.

4. 4. September 2026 um 14:06 UTCmonitoring

   Unser Drittanbieter von E-Mail-Zustellung meldet die Wiederherstellung bei der Lieferung an von Microsoft gehostete E-Mail-Dienste. Wir überwachen aktiv die Zustellung und werden bestätigen, sobald wir überprüft haben, dass Nachrichten normal fließen.

5. 4. September 2026 um 14:55 UTCresolved

   Dieses Problem ist gelöst

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. August 2026 um 17:48 UTCidentified

   Ein Problem, das Verzögerungen in der Auto Sign-in-Pipeline verursacht, wurde identifiziert und behoben. Wir arbeiten daran, die Verarbeitung zu überwachen und zu beschleunigen, um die Verarbeitung in Kürze wieder in Echtzeit zu bringen.

2. 27. August 2026 um 19:11 UTCmonitoring

   Wir sehen, dass Ereignisse in Echtzeit aufholen.

3. 27. August 2026 um 20:32 UTCresolved

   Die automatische Anmeldung wurde in Echtzeit verarbeitet und ist stabil geblieben. Dieser Vorfall ist gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. Juli 2026 um 20:19 UTCinvestigating

   Wir haben derzeit ein CSS-bezogenes Problem, das viele Seiten im Dashboard betrifft. Aufgrund dieses Problems sind Seitenlayouts defekt, was sich auf die Benutzerfreundlichkeit und die Anzeige von UI-Elementen auswirken kann. Unser Team hat das Problem identifiziert und arbeitet aktiv an einem Fix. Wir werden Updates bereitstellen, sobald weitere Informationen verfügbar sind.

2. 29. Juli 2026 um 20:26 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 29. Juli 2026 um 20:33 UTCresolved

   Wir haben das Problem identifiziert und behoben. Die Seite wird jetzt wie erwartet gerendert, und wir überwachen weiterhin.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 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. Juli 2026 um 14:04 UTCinvestigating

   We are continuing to investigate this issue.

3. 2. Juli 2026 um 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. Juli 2026 um 12:46 UTCinvestigating

   Wir haben derzeit ein Problem, bei dem E-Mails nicht zugestellt werden. Unser Team untersucht aktiv und wird Updates teilen, wenn wir mehr erfahren.

2. 2. Juli 2026 um 14:14 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 2. Juli 2026 um 14:19 UTCresolved

   Gelöst: Das E-Mail-Zustellungsproblem wurde behoben. E-Mails werden jetzt erfolgreich gesendet, und Benutzer sollten wie erwartet neue E-Mail-Benachrichtigungen erhalten.

4. 15. Juli 2026 um 21:35 UTCpostmortem

   Am 2. Juli 2026, beginnend um 1:30 Uhr PDT, trat der Benachrichtigungsdienst in einen gestörten Zustand ein und verzögerte die Zustellung von Notfallbenachrichtigungen, Besprechungseinladungen und anderen Transaktionsnachrichten. Ein kürzliches Software-Update führte einen Konfigurationsfehler ein, der verhinderte, dass der Dienst ausgehende Nachrichten korrekt verarbeitete, und es entstand ein erheblicher Rückstand über mehrere Stunden. Die Überwachung hat das Problem kurz nach dem Eintreffen der Berichte erkannt, und das Engineering hat es durch die Rückkehr zur vorherigen stabilen Version behoben. Alle Warteschlangen Benachrichtigungen wurden von 7:13 Uhr PDT geliefert Ein interner Post-Mortem wurde organisiert, um den Vorfall zu analysieren und wichtige Erkenntnisse und Aktionspunkte zu notieren. Wenn Sie Fragen haben oder zusätzliche Informationen benötigen, zögern Sie bitte nicht, unser Kundensupport-Team unter [[email protected]] (mailto:[email protected]) zu kontaktieren oder Ihren dedizierten Account Manager zu kontaktieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juni 2026 um 14:35 UTCinvestigating

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

2. 22. Juni 2026 um 14:47 UTCresolved

   This incident has been resolved.

1. 11. Juni 2026 um 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. Juni 2026 um 14:15 UTCmonitoring

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

3. 11. Juni 2026 um 15:00 UTCresolved

   This incident has been resolved.

4. 15. Juni 2026 um 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. Mai 2026 um 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. Mai 2026 um 18:02 UTCinvestigating

   We are continuing to investigate this issue.

3. 11. Mai 2026 um 18:03 UTCresolved

   This incident has been resolved.

4. 15. Mai 2026 um 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. Mai 2026 um 01:16 UTCinvestigating

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

2. 8. Mai 2026 um 01:40 UTCmonitoring

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

3. 8. Mai 2026 um 01:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 8. Mai 2026 um 03:17 UTCresolved

   This incident has been resolved.

5. 21. Mai 2026 um 01: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. März 2026 um 14:51 UTCinvestigating

   We are investigating issues impacting auto-sign in.

2. 12. März 2026 um 15:13 UTCidentified

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

3. 12. März 2026 um 16:01 UTCresolved

   This incident has been resolved.

4. 18. Mai 2026 um 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. Januar 2026 um 16:50 UTCinvestigating

   We are currently investigating the issue.

2. 27. Januar 2026 um 17:34 UTCmonitoring

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

3. 27. Januar 2026 um 17:34 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 27. Januar 2026 um 17:59 UTCresolved

   This incident has been resolved.

1. 27. Januar 2026 um 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. Januar 2026 um 16:55 UTCinvestigating

   We are currently investigating this issue.

2. 26. Januar 2026 um 16:56 UTCinvestigating

   We are continuing to investigate this issue.

3. 26. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 02: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. Januar 2026 um 02: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. Januar 2026 um 22:32 UTCresolved

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

1. 16. Januar 2026 um 12:58 UTCinvestigating

   We are currently investigating this issue.

2. 16. Januar 2026 um 13:21 UTCidentified

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

3. 16. Januar 2026 um 13:43 UTCmonitoring

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

4. 16. Januar 2026 um 14:43 UTCresolved

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

1. 15. Januar 2026 um 17:41 UTCresolved

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

1. 2. Januar 2026 um 17:57 UTCinvestigating

   We are currently investigating this issue.

2. 2. Januar 2026 um 19:43 UTCinvestigating

   We are continuing to investigate this issue.

3. 2. Januar 2026 um 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. Januar 2026 um 00:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 3. Januar 2026 um 00:18 UTCresolved

   This incident has been resolved.

1. 5. Dezember 2025 um 09: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. Dezember 2025 um 09:09 UTCinvestigating

   We are continuing to investigate this issue.

3. 5. Dezember 2025 um 09:14 UTCmonitoring

   We are seeing some portions of the site recover.

4. 5. Dezember 2025 um 09:19 UTCmonitoring

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

5. 5. Dezember 2025 um 09:32 UTCresolved

   This incident has been resolved.

1. 17. November 2025 um 16:16 UTCinvestigating

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

2. 17. November 2025 um 16:22 UTCidentified

   We have identified the issue and provided a fix.

3. 17. November 2025 um 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. November 2025 um 03:15 UTCinvestigating

   We are currently investigating the issue.

2. 14. November 2025 um 03:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 14. November 2025 um 03:47 UTCidentified

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

4. 14. November 2025 um 03:58 UTCmonitoring

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

5. 14. November 2025 um 04:07 UTCresolved

   The issue with rooms devices has been resolved.