Störungsverlauf von Doxyme

1. 1. September 2026 um 14:28 UTCinvestigating

   Wir untersuchen ein Problem mit E-Mail-Einladungen, die über doxy.me mit Invite Via gesendet werden. Einige Einladungen können sich verzögern oder nicht zugestellt werden. Dies ist ein bekanntes Problem im Zusammenhang mit einer Störung mit Mandrill, unserem Drittanbieter von E-Mail-Zustellung. Sowohl unser Team als auch das Team von Mandrill arbeiten aktiv daran, es zu lösen. Doxy.me bleibt verfügbar, und Sie können Ihren Zimmerlink weiterhin auf andere Weise teilen. Wir werden Updates bereitstellen, wenn wir mehr erfahren.

2. 1. September 2026 um 15:34 UTCidentified

   Wir haben bestätigt, dass das Problem mit E-Mail-Einladungen, die mit Invite Via gesendet werden, mit einer Störung mit Mandrill zusammenhängt. Beide Teams arbeiten aktiv daran, die E-Mail-Zustellung wiederherzustellen.

3. 1. September 2026 um 18:46 UTCmonitoring

   Mandrill hat einen Fix implementiert. Wir überwachen E-Mail-Einladungen, die mit Invite Via gesendet werden, um zu bestätigen, dass sie wie erwartet geliefert werden.

4. 1. September 2026 um 18:48 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

5. 1. September 2026 um 19:12 UTCresolved

   Die Störung mit Mandrill wurde behoben. E-Mail-Einladungen, die mit Invite Via gesendet werden, werden nun wie erwartet zugestellt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 08:10 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das eine teilweise Serviceunterbrechung verursacht. Während die Website weiterhin zugänglich ist, funktionieren einige Funktionen nicht wie erwartet, einschließlich Authentifizierung und Anmeldung. Unser Team arbeitet aktiv mit unserem Upstream-Anbieter zusammen, um die Ursache zu identifizieren und die volle Funktionalität so schnell wie möglich wiederherzustellen. Wir werden Updates bereitstellen, wenn wir mehr erfahren.

2. 16. Juli 2026 um 09:05 UTCidentified

   Wir haben das Problem als Störung unseres Authentifizierungsanbieters identifiziert, die durch einen laufenden AWS CloudFront-Vorfall verursacht wurde. Die Website bleibt möglicherweise zugänglich, aber einige Benutzer können sich möglicherweise nicht anmelden oder bestimmte Plattformfunktionen verwenden. Unser Anbieter implementiert aktiv Maßnahmen, um den betroffenen CloudFront-Service zu umgehen, und wir beobachten ihren Fortschritt genau. Wir werden ein weiteres Update bereitstellen, sobald weitere Informationen verfügbar sind.

3. 16. Juli 2026 um 11:26 UTCmonitoring

   Die Dienste funktionieren normal. Wir überwachen die Plattform weiterhin, um sicherzustellen, dass alles stabil bleibt.

4. 16. Juli 2026 um 12:09 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. März 2026 um 16:28 UTCinvestigating

   We're investigating a system-wide performance degradation impacting many users.

2. 23. März 2026 um 23:34 UTCmonitoring

   Service is returning to normal. We are continuing to monitor the situation.

3. 24. März 2026 um 09:32 UTCresolved

   The issue has been resolved. The doxy.me system is functioning as normal. Once our investigation is complete, a full report will be provided.

4. 27. März 2026 um 20:33 UTCpostmortem

   **Summary of event:** On March 23, doxy.me experienced intermittent service disruptions during a planned system upgrade. A combination of internal issues and a third-party service issue led to degraded performance throughout the day. **Incident Classification:** Service disruption caused by a combination of internal system changes and a third-party service issue. This was not a security breach. **Business impacts:** Some users experienced dropped calls, difficulty accessing History and Analytics, and issues with Custom Waiting Rooms. **Data Impact:** No evidence of unauthorized access, disclosure, or loss of customer data or PHI. Some data was temporarily unavailable during the incident but has been fully restored. **Root cause:** The disruption was caused by overlapping issues, including a third-party service not updating correctly, delays in loading History, and a migration issue affecting some settings. **How the issue was resolved:** Our team deployed fixes throughout the day and paused the upgrade to prevent further impact. Service returned to normal after all issues, including the third-party issue, were resolved. **Preventative next steps:** We are improving our system upgrade process, strengthening safeguards around third-party services, and enhancing monitoring to respond more quickly in the future.

1. 6. Januar 2026 um 18:21 UTCinvestigating

   We are currently investigating a reported system outage that's impacting provider log in.

2. 6. Januar 2026 um 19:00 UTCmonitoring

   Provider login is returning back to normal. We are continuing to monitor the situation.

3. 6. Januar 2026 um 20:00 UTCresolved

   The issue impacting provider login has been resolved. The doxy.me system is functioning as normal. Once our investigation is complete, a post-mortem will be provided.

1. 2. Januar 2026 um 15:36 UTCinvestigating

   We are currently investigating a reported system outage that's impacting provider log in.

2. 2. Januar 2026 um 16:29 UTCmonitoring

   The ability to login is returning back to normal. We are continuing to monitor the situation.

3. 2. Januar 2026 um 19:30 UTCresolved

   The issue preventing provider login has been resolved. The doxy.me system is functioning as normal. Once our investigation is complete, a post-mortem will be provided.

1. 29. Oktober 2025 um 16:22 UTCinvestigating

   We are currently investigating an issue affecting some provider logins on doxy.me. Users may experience a blank or unresponsive login page. Initial investigation indicates that the issue originates from our authentication system, which is currently experiencing a global outage related to CDN configuration. We’re actively monitoring the situation and working to ensure service stability. Components Affected: • Provider Sign-In • Authentication Service

2. 29. Oktober 2025 um 16:46 UTCmonitoring

   Fix for the issue with auth CDN provider is applied, and login services on doxy.me are now recovering. We are continuing to monitor performance and accessibility across all regions to ensure full stability. Components Affected: • Provider Sign-In • Authentication Service

3. 29. Oktober 2025 um 18:22 UTCresolved

   This incident has been resolved. All login and authentication services are now operating normally.

1. 20. Oktober 2025 um 09:56 UTCinvestigating

   We’re investigating an issue causing file uploads (like check-in photos) to fail and preventing some new sessions from starting. Ongoing calls are working normally. The issue appears related to an AWS outage and we’re monitoring their progress.

2. 20. Oktober 2025 um 10:20 UTCmonitoring

   A fix has been implemented by our AWS partner, and affected doxy.me services are recovering. File uploads and new session starts are operating normally, but we’re continuing to monitor to ensure full stability.

3. 20. Oktober 2025 um 14:49 UTCinvestigating

   A doxy.me partner, AWS, is experiencing an issue that is now impacting some provider sign-ins, site functionality, and file uploads. We’re monitoring AWS and will share updates as they become available.

4. 20. Oktober 2025 um 20:04 UTCinvestigating

   The ongoing AWS issue continues to affect some doxy.me services. We’re closely monitoring the situation and will share updates as they are available.

5. 21. Oktober 2025 um 09:38 UTCresolved

   The AWS issue has been resolved and all doxy.me services are now functioning normally.

1. 8. September 2025 um 11:36 UTCinvestigating

   We are investigating an issue with our SMS partner affecting custom SMS delivery. Default SMS continues to work as expected.

2. 8. September 2025 um 14:51 UTCidentified

   The issue has been identified with our SMS provider and work is underway on a long-term solution. Custom SMS appointment invites are currently sending, but there may still be disruptions.

3. 9. September 2025 um 16:49 UTCmonitoring

   Custom SMS appointment invites are sending reliably and we’re continuing to monitor.

4. 11. September 2025 um 15:54 UTCresolved

   After a period of monitoring, we have confirmed SMS appointment invites are sending normally and the issue is resolved.

1. 14. August 2025 um 18:22 UTCinvestigating

   We are currently investigating a reported system outage that's impacting provider log in.

2. 14. August 2025 um 18:47 UTCmonitoring

   The ability to login is returning back to normal. We are continuing to monitor the situation.

3. 14. August 2025 um 19:42 UTCresolved

   The issue preventing provider login has been resolved. The doxy.me system is functioning as normal. Once our investigation is complete, a post-mortem will be provided.

1. 28. April 2025 um 12:29 UTCinvestigating

   We're currently investigating a reported system outage that's impacting patient check-in and provider account access.

2. 28. April 2025 um 12:51 UTCmonitoring

   The system is returning to normal. We are continuing to monitor the situation.

3. 28. April 2025 um 16:00 UTCresolved

   The system issue preventing patient check-in and provider account access has been resolved. The doxy.me system is functioning as normal. Once our investigation is complete, a post-mortem will be provided.

4. 29. April 2025 um 11:43 UTCpostmortem

   **Summary of event** On April 28, our monitoring system detected a sharp slowdown in platform performance, preventing some users from accessing doxy.me. This disruption lasted for approximately 35 minutes before service was restored by increasing system capacity. **Business impacts** During the incident, users were unable to access doxy.me for telehealth sessions, leading to delayed or missed appointments and interruptions in patient care. **Root cause** A recent system update unintentionally lowered the number of active servers. Because this deployment occurred after our daily resource allocations, the platform did not have sufficient capacity to handle the level of traffic, resulting in degraded performance. **How the issue was resolved** Once the root cause was identified, our engineering team increased the number of active servers. This promptly reduced system load and restored access for users. **Preventative next steps** * Update deployment procedures to appropriately size server capacity at the time updates are launched * Improve intra-day automated resource allocations and real-time monitoring

1. 13. März 2025 um 21:08 UTCinvestigating

   We're actively investigating an outage affecting Apps, such as File Transfer and Whiteboard.

2. 13. März 2025 um 21:53 UTCidentified

   We've identified the cause of the outage. Our team is working on a fix, and we’ll share updates as we make progress.

3. 13. März 2025 um 21:55 UTCmonitoring

   Monitoring - App functionality has been restored. We’ll continue to monitor the situation.

4. 13. März 2025 um 22:07 UTCresolved

   The issue causing the app outage has been fixed and the system is now fully operational. All apps are functioning normally. A post-mortem report will be provided in the coming days.

1. 5. März 2025 um 18:42 UTCinvestigating

   We're currently investigating a reported system outage that's impacting patient check-in and provider account access.

2. 5. März 2025 um 18:57 UTCinvestigating

   System is returning back to normal. We are continuing to monitor the situation.

3. 5. März 2025 um 18:57 UTCmonitoring

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

4. 5. März 2025 um 19:30 UTCresolved

   We recently encountered an issue that prevented patients from appearing in their provider's waiting room queue. This issue has now been resolved, and patient check-in is functioning as expected. A post-mortem report will be provided in the coming days.

1. 19. Dezember 2024 um 17:06 UTCinvestigating

   We are currently investigating this issue.

2. 19. Dezember 2024 um 22:19 UTCmonitoring

   The system is returning to normal. We are continuing to monitor the situation.

3. 20. Dezember 2024 um 01:43 UTCresolved

   The system issue preventing patient check-in and provider account access has been resolved. The doxy.me system is functioning as normal. Once our investigation is complete, a post-mortem will be provided.

1. 25. Oktober 2024 um 00:36 UTCinvestigating

   We’re aware that patients are not appearing in their provider’s waiting room queue, and we are actively investigating the issue. We will provide updates as soon as we have more information. Thank you for your patience.

2. 25. Oktober 2024 um 10:02 UTCmonitoring

   System is returning back to normal. We are continuing to monitor the situation.

3. 25. Oktober 2024 um 11:28 UTCresolved

   We recently encountered an issue that prevented patients from appearing in their provider’s waiting room queue. This issue has now been resolved, and patient check-in is functioning as expected. We will provide a post-mortem report in the coming days.

4. 4. November 2024 um 14:08 UTCpostmortem

   **Summary of event**: On October 24, patients who successfully checked in did not appear in the Waiting Room queue due to an incident from our real-time partner, PubNub. PubNub provides the technology that enables instant updates to [doxy.me](http://doxy.me) when a patient has joined a provider's Waiting Room and allows us to start a video call. This led to an outage on [doxy.me](http://doxy.me) approximately between October 24, 7:15 AM ET - 10:00 AM ET and October 24, 8:15 PM ET - October 25, 6:00 AM ET. **Business impacts:** Although providers were able to log in, their Waiting Room queue remained empty, preventing a session from starting between the patient and provider. **Root cause:** Our real-time partner, PubNub, encountered an unusual surge in traffic from sources other than [doxy.me](http://doxy.me), that temporarily overwhelmed their system, preventing it from responding quickly enough. As a result, PubNub’s communications to [doxy.me](http://doxy.me) were interrupted, causing patients to not appear in the Waiting Room queue.  **How was the issue resolved:** PubNub blocked the source of surging traffic and made changes to handle the increased demand. Once PubNub made this update, [doxy.me](http://doxy.me) was fully operational again. [Doxy.me](http://Doxy.me) did not make any changes.  **Preventative next steps:** [Doxy.me](http://Doxy.me) will collaborate with PubNub to ensure PubNub can manage traffic surges from its other customers and maintain scalable infrastructure, minimizing any potential impact on [doxy.me](http://doxy.me) services and customers.

1. 24. Oktober 2024 um 11:32 UTCinvestigating

   We are currently investigating this issue of patients not being able to check in and start call. We will update this status as soon as we have more information

2. 24. Oktober 2024 um 13:06 UTCidentified

   Our real-time service provider has identified the issue and is working on a fix. We will continue to monitor and work towards restoring our services.

3. 24. Oktober 2024 um 14:09 UTCmonitoring

   Our real-time service provider is seeing improvements with the patient check-in and appointment start issues, and we will continue to closely monitor the recovery process

4. 24. Oktober 2024 um 16:00 UTCresolved

   Resolved - The issue affecting patient check-ins and starting doxy.me appointments has been resolved and will continue to be monitored to ensure stable performance

1. 19. Oktober 2024 um 20:18 UTCresolved

   We recently encountered an issue that prevented patients from checking in on doxy.me 2.0. This issue has now been resolved, and patient check-in is functioning as expected. We will provide a post-mortem report in the coming days.

2. 28. Oktober 2024 um 21:32 UTCpostmortem

   **Summary of event**: On October 19, [doxy.me](http://doxy.me) encountered an issue that prevented patients from checking in on [doxy.me](http://doxy.me) 2.0. This outage resulted in 8 hours and 28 minutes of unplanned downtime between 8:01 AM ET and 4:30 PM ET. **Business impacts:** Patients were unable to complete the check-in process. After entering their name and clicking the Check-In button, they remained stuck on the check-in screen instead of joining their provider’s waiting room. While providers were able to log in during this incident and receive patient check-in notifications, patients didn’t appear in their waiting room queue. This prevented a provider from starting a video call with the patient. **Root cause:** Security improvements implemented in our real-time messaging system and [doxy.me](http://doxy.me) 2.0 platform led to an issue that arose approximately 48 hours after the release. The continuous release cycle of [doxy.me](http://doxy.me) prevented the issue from appearing in our non-production environments used for pre-release testing. **How was the issue resolved:** Engineering identified real-time messaging as the root cause of the outage and updated accordingly while maintaining the security enhancements implemented.   **Preventative next steps:** We’re enhancing our testing framework to include additional scenarios that will help identify unexpected real-time issues.

1. 21. November 2023 um 15:24 UTCinvestigating

   We are aware of an outage currently affecting doxy.me. Our team is currently investigating at this time. We will post an update as we know more.

2. 21. November 2023 um 16:17 UTCinvestigating

   We are continuing to investigate this issue.

3. 21. November 2023 um 19:25 UTCidentified

   The issue has been identified and a fix is being created. We are continuing to monitor the situation and have seen normal site functionality return.

4. 22. November 2023 um 12:52 UTCresolved

   This incident has been resolved.

1. 18. Juli 2023 um 17:07 UTCinvestigating

   We are currently investigating this issue.

2. 18. Juli 2023 um 17:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 18. Juli 2023 um 17:35 UTCresolved

   Between 12:37 PM and 1:13 AM EST, our partner AWS experienced elevated error rates for request serviced by the CloudFront Origin Shield and Regional Edge Cache in the US-EAST-1 region. The issue has been resolved and service is operating normally.

1. 25. Mai 2023 um 18:29 UTCinvestigating

   We are aware of an outage currently affecting doxy.me. This appears to affect sign-in, call connecting, and various other system services. Our team is currently investigating at this time. We will post an update as we know more.

2. 25. Mai 2023 um 19:06 UTCmonitoring

   We are seeing our system stabilizing. We are continuing to look into the incident and are going to continue to monitor the situation.

3. 26. Mai 2023 um 13:00 UTCmonitoring

   System levels have remained stable overnight. We are continuing to monitor the system performance and will provide another update by 12pm ET.

4. 26. Mai 2023 um 16:01 UTCresolved

   Doxy.me services continue to be stable. We are considering this incident resolved and will provide a post mortem within the few business days.

5. 2. Juni 2023 um 17:35 UTCpostmortem

   **Summary of event:** On May 25th, [Doxy.me](http://doxy.me/) experienced a database issue that resulted in 27 minutes of unplanned downtime from 2:03pm to 2:30pm ET. **Business Impacts:** Sessions in progress were not impacted. The incident resulted in providers being unable to log in for their sessions. In addition, patients who were not already in the queue were unable to check in to their providers waiting room. **Root cause:** A data import file was processed internally. While it was being processed, a series of long-running secondary server processes were triggered. Unfortunately, these processes built up in number, consuming additional server resources until the servers were backed up. **How was the issue resolved:** The file was able to finish processing and the system self recovered. **Preventative next steps:** We are optimizing the the long-running processes which will help prevent this scenario from happening again. In the short term, we are no longer running large data imports during peak business hours.

1. 10. Januar 2023 um 15:21 UTCinvestigating

   We are currently investigating an issue where older versions of web browsers (Safari, Chrome, Firefox, Edge) are not allowing doxy.me to load. Updating your browser to the latest version will allow doxy.me to load. Browsers able to load doxy.me: Safari 15.4 and newer Chrome 93 and newer Firefox 92 and newer Edge 93 and newer If you or your client is impacted at this time, our help article will help guide you to update.

2. 10. Januar 2023 um 17:39 UTCidentified

   We have determined the root cause for this incident and are currently testing a fix. At this time, we expect the fix to be deployed early tomorrow, between 3:00am and 7:00am EST (between 08:00 and 12:00 UTC).

3. 11. Januar 2023 um 12:59 UTCresolved

   We have deployed a fix restoring functionality to the out of date browsers. We recommend keeping your devices and browsers up to date in general, but do apologize for any disruption this incident may have caused. We will share the post mortem within the next few business days.

4. 13. Januar 2023 um 18:40 UTCpostmortem

   **Summary of event:** On January 10th, an update caused out-of-date browsers to not load [doxy.me](http://doxy.me/). **Business Impacts:** Patients or providers using the impacted browsers were unable to access [doxy.me](http://doxy.me/). **Root cause:** One of the software packages used in our code was updated on January 10th, 2023 at 08:20 AM UTC. The updated version was incompatible with and no longer supported older browser versions, including any versions older than the following: * Chrome: 93 \(released August 31st, 2021\) * Firefox: 92 \(released September 7th, 2021\) * Safari: 15.4 \(released March 15th, 2022\) * Edge:  93 \(released August 3rd, 2021\) **How was the issue resolved:** [Doxy.me](http://doxy.me/) released a fix that reverted the update to the software packages on January 11th, at 8:03 AM UTC. **Preventative next steps:** We will be updating our internal system requirements and our supported browser policies. Once approved, we will increase our communication efforts with our customers to make it easier for them to recognize when they are using an out-of-date browser and how to update it. We will also shore up our testing coverage to better detect these problems in advance. Thank you for your patience.