Historial de interrupciones de Doxyme

1. September 1, 2026 at 2:28 PM UTCinvestigating

   Estamos investigando un problema que afecta a las invitaciones de correo electrónico enviadas a través de doxy.me mediante Invita Via. Algunas invitaciones pueden retrasarse o no ser entregadas. Este es un problema conocido relacionado con una interrupción con Mandrill, nuestro proveedor de correo electrónico de terceros. Tanto nuestro equipo como el equipo de Mandrill están trabajando activamente para resolverlo. Doxy.me sigue disponible, y puedes seguir compartiendo tu enlace de habitación de otras maneras. Proporcionaremos actualizaciones a medida que aprendamos más.

2. September 1, 2026 at 3:34 PM UTCidentified

   Hemos confirmado que el problema que afecta a las invitaciones de correo electrónico enviadas usando Invita Via está relacionado con una perturbación con Mandrill. Ambos equipos están trabajando activamente para restaurar la entrega de correo electrónico.

3. September 1, 2026 at 6:46 PM UTCmonitoring

   Mandrill ha implementado una solución. Estamos monitoreando las invitaciones de correo electrónico enviadas usando Invita Via para confirmar que se están entregando como se espera.

4. September 1, 2026 at 6:48 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

5. September 1, 2026 at 7:12 PM UTCresolved

   Se ha resuelto la perturbación con Mandrill. Las invitaciones de correo electrónico enviadas mediante Invita Via están siendo entregadas como se espera.

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

1. July 16, 2026 at 8:10 AM UTCinvestigating

   Actualmente estamos investigando un problema que causa una interrupción parcial del servicio. Si bien el sitio web sigue siendo accesible, algunas funcionalidades no funcionan como se espera, incluyendo la autenticación y el login. Nuestro equipo está trabajando activamente con nuestro proveedor para identificar la causa raíz y restaurar la funcionalidad lo más rápido posible. Proporcionaremos actualizaciones a medida que aprendamos más.

2. July 16, 2026 at 9:05 AM UTCidentified

   Hemos identificado el problema como una perturbación que afecta a nuestro proveedor de autenticación, causada por un incidente en curso de AWS CloudFront. El sitio web puede permanecer accesible, pero algunos usuarios pueden ser incapaces de iniciar sesión o utilizar ciertas funciones de plataforma. Nuestro proveedor está implementando activamente mitigacións para evitar el servicio CloudFront afectado, y estamos monitoreando de cerca su progreso. Proporcionaremos otra actualización tan pronto como se disponga de más información.

3. July 16, 2026 at 11:26 AM UTCmonitoring

   Los servicios funcionan normalmente. Continuamos monitoreando la plataforma para asegurar que todo permanezca estable.

4. July 16, 2026 at 12:09 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. March 23, 2026 at 4:28 PM UTCinvestigating

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

2. March 23, 2026 at 11:34 PM UTCmonitoring

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

3. March 24, 2026 at 9:32 AM 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. March 27, 2026 at 8:33 PM 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. January 6, 2026 at 6:21 PM UTCinvestigating

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

2. January 6, 2026 at 7:00 PM UTCmonitoring

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

3. January 6, 2026 at 8:00 PM 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. January 2, 2026 at 3:36 PM UTCinvestigating

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

2. January 2, 2026 at 4:29 PM UTCmonitoring

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

3. January 2, 2026 at 7:30 PM 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. October 29, 2025 at 4:22 PM 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. October 29, 2025 at 4:46 PM 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. October 29, 2025 at 6:22 PM UTCresolved

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

1. October 20, 2025 at 9:56 AM 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. October 20, 2025 at 10:20 AM 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. October 20, 2025 at 2:49 PM 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. October 20, 2025 at 8:04 PM 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. October 21, 2025 at 9:38 AM UTCresolved

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

1. September 8, 2025 at 11:36 AM UTCinvestigating

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

2. September 8, 2025 at 2:51 PM 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. September 9, 2025 at 4:49 PM UTCmonitoring

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

4. September 11, 2025 at 3:54 PM UTCresolved

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

1. August 14, 2025 at 6:22 PM UTCinvestigating

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

2. August 14, 2025 at 6:47 PM UTCmonitoring

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

3. August 14, 2025 at 7:42 PM 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. April 28, 2025 at 12:29 PM UTCinvestigating

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

2. April 28, 2025 at 12:51 PM UTCmonitoring

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

3. April 28, 2025 at 4:00 PM 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. April 29, 2025 at 11:43 AM 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. March 13, 2025 at 9:08 PM UTCinvestigating

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

2. March 13, 2025 at 9:53 PM 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. March 13, 2025 at 9:55 PM UTCmonitoring

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

4. March 13, 2025 at 10:07 PM 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. March 5, 2025 at 6:42 PM UTCinvestigating

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

2. March 5, 2025 at 6:57 PM UTCinvestigating

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

3. March 5, 2025 at 6:57 PM UTCmonitoring

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

4. March 5, 2025 at 7:30 PM 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. December 19, 2024 at 5:06 PM UTCinvestigating

   We are currently investigating this issue.

2. December 19, 2024 at 10:19 PM UTCmonitoring

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

3. December 20, 2024 at 1:43 AM 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. October 25, 2024 at 12:36 AM 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. October 25, 2024 at 10:02 AM UTCmonitoring

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

3. October 25, 2024 at 11:28 AM 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. November 4, 2024 at 2:08 PM 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. October 24, 2024 at 11:32 AM 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. October 24, 2024 at 1:06 PM 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. October 24, 2024 at 2:09 PM 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. October 24, 2024 at 4:00 PM 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. October 19, 2024 at 8:18 PM 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. October 28, 2024 at 9:32 PM 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. November 21, 2023 at 3:24 PM 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. November 21, 2023 at 4:17 PM UTCinvestigating

   We are continuing to investigate this issue.

3. November 21, 2023 at 7:25 PM 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. November 22, 2023 at 12:52 PM UTCresolved

   This incident has been resolved.

1. July 18, 2023 at 5:07 PM UTCinvestigating

   We are currently investigating this issue.

2. July 18, 2023 at 5:34 PM UTCinvestigating

   We are continuing to investigate this issue.

3. July 18, 2023 at 5:35 PM 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. May 25, 2023 at 6:29 PM 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. May 25, 2023 at 7:06 PM 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. May 26, 2023 at 1:00 PM UTCmonitoring

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

4. May 26, 2023 at 4:01 PM 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. June 2, 2023 at 5:35 PM 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. January 10, 2023 at 3:21 PM 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. January 10, 2023 at 5:39 PM 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. January 11, 2023 at 12:59 PM 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. January 13, 2023 at 6:40 PM 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.