Historial de interrupciones de Nuance

1. August 28, 2026 at 6:58 AM UTCidentified

   Microsoft ha identificado y es activamente problemático solucionar un problema que afecta a los productos Dax/Dragon Copilot dentro de nuestro centro de datos de los Estados Unidos. Se proporcionarán más detalles cuando se disponga de información.

2. August 28, 2026 at 7:01 AM UTCidentified

   Microsoft está investigando una interrupción del servicio en nuestro Centro de Datos de EE.UU. que afecta a los productos DAX/Dragon Copilot para médicos y enfermeras. Los síntomas pueden incluir • Dragon/DAX Copilot Standalone o Los Usuarios podrían seguir dictando y creando grabaciones. o Los Usuarios no podían acceder a resúmenes generados a través de la UI. o Se espera que la grabación/dictación y las subidas continúen, y los resúmenes estarán disponibles una vez que el servicio se recupere. • Clientes integrados (Epic/EHR integrados): o Se continuó la entrega resumida. o La experiencia Sidecar/UI no estaba disponible. o Se esperaba que se entregaran resúmenes generados. Nuestros equipos de ingeniería están trabajando activamente para mitigar el impacto. Proporcionaremos actualizaciones adicionales cuando estén disponibles. Nos disculpamos por cualquier inconveniente y apreciamos su asociación continua mientras trabajamos para volver a los niveles normales de servicio lo más rápido posible.

3. August 28, 2026 at 7:46 AM UTCidentified

   Seguimos trabajando para solucionar este problema.

4. August 28, 2026 at 8:38 AM UTCidentified

   Microsoft continúa investigando el problema impactando un servicio de backend en nuestro Centro de Datos de EE.UU. que afecta a DAX/Dragon Copilot para Médicos y Enfermeras . Los síntomas pueden incluir • Dragon/DAX Copilot Standalone o Los Usuarios podrían seguir dictando y creando grabaciones. o Los Usuarios no podían acceder a resúmenes generados a través de la UI. o Se espera que la grabación/dictación y las subidas continúen, y los resúmenes estarán disponibles una vez que el servicio se recupere. • Clientes integrados (Epic/EHR integrados): o Se continuó la entrega resumida. o La experiencia Sidecar/UI no estaba disponible. o Se esperaba que se entregaran resúmenes generados. Situación actual Nuestros equipos de ingeniería están trabajando activamente para mitigar el impacto después del problema identificado que un centro de datos que apoya la funcionalidad Dragon y DAX Copilot ha experimentado un evento de energía. Estamos trabajando para llevar a cabo operaciones de recuperación para restaurar los recursos informáticos afectados mientras que en paralelo realizamos una falla en la infraestructura sana para restaurar el servicio más rápidamente. Seguiremos vigilando la situación y proporcionaremos actualizaciones adicionales a medida que estén disponibles. Nos disculpamos por cualquier inconveniente y apreciamos su asociación y paciencia continuas mientras trabajamos para volver a los niveles normales de servicio lo más rápido posible.

5. August 28, 2026 at 10:41 AM UTCmonitoring

   Microsoft sigue abordando activamente el problema que afecta a DAX/Dragon Copilot para Médicos y Enfermeros relacionados con una dependencia de servicio de backend en nuestro entorno de centro de datos de EE.UU.. Situación actual Hemos completado la falta de infraestructura de servicio redundante, sin embargo nuestra vigilancia determinó que el impacto continuó. Junto a esto confirmamos que el evento de potencia que impacta a un centro de datos que apoya la funcionalidad Dragon/DAX Copilot se ha recuperado y los recursos impactados han sido restaurados. Como tal, estamos revertiendo el fracaso de nuevo a la configuración conocida anterior Los síntomas pueden incluir • Dragon/DAX Copilot Standalone o Los Usuarios podrían seguir dictando y creando grabaciones. o Los Usuarios no podían acceder a resúmenes generados a través de la UI. o Se espera que la grabación/dictación y las subidas continúen, y los resúmenes estarán disponibles una vez que el servicio se recupere. • Clientes integrados (Epic/EHR integrados): o Se continuó la entrega resumida. o La experiencia Sidecar/UI puede haber sido indisponible o intermitentemente impactada. o Se esperaba que se entregaran resúmenes generados. Acciones en curso Microsoft continúa monitoreando de cerca la salud de los servicios al completar las actividades de recuperación y validación. Seguimos enfocados en restaurar toda la funcionalidad y garantizar una experiencia de cliente estable. Proporcionaremos actualizaciones adicionales a medida que se disponga de más información. Nos disculpamos por cualquier inconveniente que este problema pueda haber causado y apreciar su paciencia y asociación continuas mientras trabajamos para restaurar plenamente los niveles de servicio normales.

6. August 28, 2026 at 12:38 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

7. August 28, 2026 at 2:37 PM UTCresolved

   Microsoft ha remediado el problema que estaba afectando a DAX/Dragon Copilot para Médicos y Enfermeros relacionados con una dependencia de servicio de backend en nuestro entorno de centro de datos de Estados Unidos. Estado final: Antes de completar la reversión de la falla, confirmamos que las acciones de mitigación anteriores habían restaurado la capacidad de los usuarios para cargar y acceder a los resúmenes generados a través de la interfaz de usuario. Esta es la actualización final del incidente. Preliminary Root Cause: Un centro de datos que apoya la funcionalidad Dragon y DAX Copilot experimentaron un evento de energía, lo que llevó a impacto.

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

1. August 28, 2026 at 6:46 AM UTCinvestigating

   Microsoft ha identificado y es activamente problemático solucionar un problema que afecta a los productos Dax/Dragon Copilot dentro de nuestro centro de datos de los Estados Unidos. Se proporcionarán más detalles cuando se disponga de información.

2. August 28, 2026 at 6:49 AM UTCidentified

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

3. August 28, 2026 at 6:49 AM UTCidentified

   Seguimos trabajando para solucionar este problema.

4. August 28, 2026 at 6:50 AM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

5. August 28, 2026 at 6:51 AM UTCinvestigating

   Seguimos investigando esta cuestión.

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

1. August 13, 2026 at 2:00 PM UTCinvestigating

   We are currently investigating this issue.

2. August 13, 2026 at 2:21 PM UTCinvestigating

   Microsoft is investigating an issue affecting DAX Copilot for DMO customers. The symptoms include: - Summary unavailable - summaries stay in "writing" status, or disappear after uploading the recording - Delayed summary delivery Clinicians are able to successfully record encounters, but the completed summary is not available or delayed after upload. There is no known data loss and impacted encounters will be successfully processed once this issue is mitigated. Thank you for your patience and continued partnership.

3. August 13, 2026 at 2:49 PM UTCidentified

   Microsoft has mitigated the root cause of the recent issue affecting DAX copilot for DMO customers. The symptoms included: - Summary unavailable - summaries stay in "writing" status, or disappear after uploading the recording - Delayed summary delivery At this time, clinicians are able to successfully receive summaries after initiating new recordings using DAX Copilot for DMO. We are actively working to reprocess any encounters that were impacted by this incident to make the summaries available. There is no known data loss and impacted encounters will be successfully processed. We will provide additional communication to update the status of the recovery efforts. Thank you for your patience and continued partnership.

4. August 13, 2026 at 4:59 PM UTCresolved

   Microsoft has mitigated the root cause of the recent issue affecting DAX copilot for DMO customers and successfully reprocessed all impacted encounters. The symptoms included: - Summary unavailable - summaries stay in "writing" status, or disappear after uploading the recording - Delayed summary delivery All encounters impacted by this incident have been recovered. At this time, summaries are available for any encounters impacted during this incident, and clinicians are able to successfully receive summaries after initiating new recordings using DAX Copilot for DMO. Thank you for your patience and continued partnership.

1. August 12, 2026 at 6:32 PM UTCinvestigating

   Microsoft has been made aware of an issue that is impacting customer being able to call and contact support. This is being investigated. At this time please continue to use the other avenues for support access to include the Community Portal and Chat where available.

2. August 13, 2026 at 1:32 AM UTCidentified

   Microsoft has identified the issue preventing calls from being received by the support team and continues to work on remediation. At this time, it is encouraged that other methods of contacting support be utilzied such as the Nuance Community Portal.

3. August 13, 2026 at 5:37 PM UTCresolved

   Microsoft has mitigated the issue preventing calls from being received by the support team. The technical support line is functioning as expected. Thank you for your patience and continued partnership.

1. August 4, 2026 at 2:10 PM UTCinvestigating

   We are curretly investigating reports of issues launching Dragon Copilot/DAX Copilot application. More details will be provided shortly

2. August 4, 2026 at 2:45 PM UTCidentified

   Microsoft has identified an issue affecting Dragon Copilot Desktop and DAX Copilot for Epic ambient users.  Dragon Copilot Desktop and DAX Copilot in Epic launch fails with one of the following messages: Ambient recorder failed to load Visit recording could not be started Unable to Launch Dax Copilot  Engineers are currently engaged and working toward remediation. Thank you for your patience and continued partnership.

3. August 4, 2026 at 4:02 PM UTCmonitoring

   Microsoft has resolved an intermittent issue that affected some Dragon Copilot Desktop and DAX Copilot for Epic ambient users. While the issue is no longer impacting users, we continue to monitor the environment and investigate the underlying root cause. Impacted users may have experienced one of the following messages: Ambient recorder failed to load Visit recording could not be started Unable to Launch DAX Copilot Thank you for your patience and continued partnership.

4. August 12, 2026 at 6:30 PM UTCresolved

   This incident has been resolved.

1. August 1, 2026 at 10:59 PM UTCinvestigating

   Actualmente estamos investigando un problema donde los administradores pueden no ser capaces de agregar nuevos usuarios a NMC. Vamos a proporcionar una actualización en breve

2. August 1, 2026 at 11:50 PM UTCresolved

   Tras la investigación se identificó una cuestión regional y se ha remediado inmediatamente.

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

1. July 15, 2026 at 12:57 PM UTCinvestigating

   Microsoft está investigando el error reportado anteriormente.

2. July 15, 2026 at 1:18 PM UTCidentified

   Microsoft ha identificado el error reportado anteriormente y trabajando en la remediación.

3. July 15, 2026 at 1:39 PM UTCidentified

   Microsoft está investigando un problema que afecta a Dragon y DAX Copilot para usuarios ambientales EPIC en Epic Nebula. El lanzamiento de DAX/Dragon Copilot en Epic Haiku estaba fallando con el siguiente mensaje: Se encontró un error al comunicarse con el servidor. Busque asistencia de un administrador si el problema persiste. Código: SerializaciónFailure Details: Token inesperada. El impacto se atribuye específicamente a: Los usuarios de Ambient en Epic Nebula. Se han adoptado medidas de rehabilitación y se ha observado un mejor desempeño. Microsoft está monitoreando estrechamente y actualizará el estado en consecuencia. Gracias por su paciencia y colaboración continua.

4. July 15, 2026 at 2:26 PM UTCmonitoring

   Microsoft ha remediado un problema que afecta a Dragon y DAX Copilot para usuarios ambientales EPIC en Epic Nebula. El lanzamiento de DAX/Dragon Copilot en Epic Haiku estaba fallando con el siguiente mensaje: Se encontró un error al comunicarse con el servidor. Busque asistencia de un administrador si el problema persiste. Código: SerializaciónFailure Details: Token inesperada. El impacto se atribuye específicamente a: Los usuarios de Ambient en Epic Nebula. Gracias por su paciencia y colaboración continua.

5. July 15, 2026 at 3:27 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 14, 2026 at 3:50 PM UTCinvestigating

   Microsoft está investigando los informes de este error.

2. July 14, 2026 at 4:57 PM UTCmonitoring

   Se resuelve un problema que afecta a Dragon y DAX Copilot para usuarios ambientales EPIC en Epic Nebula. El lanzamiento de DAX/Dragon Copilot en Epic Haiku estaba fallando con el siguiente mensaje: Se encontró un error al comunicarse con el servidor. Busque asistencia de un administrador si el problema persiste. Código: SerializaciónFailure Details: Token inesperada. El impacto se atribuye específicamente a: Usuarios ambientes en Nebulas épicas. Epic ha identificado y remediado la cuestión a finales de 11:36am ET y están monitoreando activamente. Gracias por su paciencia y colaboración continua.

3. July 14, 2026 at 5:25 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 2, 2026 at 4:18 AM UTCidentified

   Microsoft ha identificado y es activamente problemático solucionar un problema que afecta a los productos Dax/Dragon Copilot dentro de nuestro centro de datos de los Estados Unidos. Se proporcionarán más detalles cuando se disponga de información.

2. July 2, 2026 at 5:15 AM UTCmonitoring

   Microsoft ha identificado y mitigado una interrupción del servicio en nuestro Centro de Datos de EE.UU. que afecta a los clientes de Dragon y DAX Copilot. Los síntomas pueden haber incluido Incapaz de iniciar sesión en DAX Copilot Mensaje de error que indica "Unable to launch DAX Copilot" Mensaje de error que indica "Dragon Copilot no está disponible actualmente" Nuestros equipos de ingeniería continuarán monitoreando estrechamente el servicio para garantizar la estabilidad. Nos disculpamos por cualquier inconveniente y apreciamos su asociación continua

3. July 2, 2026 at 5:52 AM UTCmonitoring

   Microsoft ha identificado y mitigado una interrupción del servicio en nuestro Centro de Datos de EE.UU. que afecta a los clientes de Dragon y DAX Copilot. Los síntomas pueden haber incluido Incapaz de iniciar sesión en DAX Copilot Mensaje de error que indica "Unable to launch DAX Copilot" Mensaje de error que indica "Dragon Copilot no está disponible actualmente" Nuestros equipos de ingeniería siguen vigilando de cerca el servicio para garantizar la estabilidad y que todo el audio impactado se reprocese con éxito. En este momento todos los servicios son devueltos a la normalidad. Nota: Los usuarios que ya estaban conectados, recomendamos iniciar sesión y volver a entrar para garantizar un rendimiento óptimo de la aplicación Nos disculpamos por cualquier inconveniente y apreciamos su asociación continua

4. July 2, 2026 at 5:22 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 1, 2026 at 5:22 PM UTCmonitoring

   Microsoft está investigando una interrupción del servicio en nuestros centros de datos estadounidenses que afectan la capacidad de utilizar Dragon Medical One (DMO) con Chrome o extensión Edge para un pequeño subconjunto de usuarios.

2. July 1, 2026 at 6:59 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 2, 2026 at 5:48 PM UTCinvestigating

   Microsoft is investigating a service disruption in our US Data Center affecting a subset of DAX Copilot and Dragon Copilot customers. Symptoms may include: -Delay in summary delivery on some encounters. (If you are uncertain about impact and want to assess impact to your specific organization your Customer Service Manager (CSM) can assist). Our engineering teams are actively working to identify the root cause and mitigate impact. We will provide additional updates as they become available. We apologize for any inconvenience and appreciate your continued partnership while we work to return to normal service levels as quickly as possible.

2. June 2, 2026 at 5:55 PM UTCidentified

   Microsoft is investigating an issue affecting some Dragon Copilot and DAX Copilot users within your US datacenter region. Symptoms may include: Delay in summary delivery on some encounters. If you are uncertain about impact and want to assess impact to your specific organization your Customer Service Manager (CSM) can assist. Our engineering teams are actively working to identify the root cause and mitigate impact. We will provide additional updates as they become available. We apologize for any inconvenience and appreciate your continued partnership while we work to return to normal service levels as quickly as possible.

3. June 2, 2026 at 6:27 PM UTCmonitoring

   Microsoft has remediated an issue affecting some Dragon Copilot and DAX Copilot users within your US datacenter region. Symptoms may have included: Delay in summary delivery on some encounters. If you are uncertain about impact and want to assess impact to your specific organization your Customer Service Manager (CSM) can assist. All impacted notes have now been delivered. Note: There are potential delays with orders and backlog is being processed. We apologize for any inconvenience and appreciate your continued partnership.

4. June 2, 2026 at 7:41 PM UTCresolved

   Microsoft has remediated an issue affecting some Dragon Copilot and DAX Copilot users within your US datacenter region. Symptoms may have included: Delay in summary delivery on some encounters. If you are uncertain about impact and want to assess impact to your specific organization your Customer Service Manager (CSM) can assist. All impacted notes have now been delivered. The Orders backlog has been processed. We apologize for any inconvenience and appreciate your continued partnership

1. May 27, 2026 at 5:40 PM UTCidentified

   Microsoft is investigating an issue affecting DAX Copilot for EPIC users within our US datacenters. Symptom: Subsequent recordings are failing to generate new drafts. Microsoft is actively working on remediation and will provide more information as soon as it is available. Thank you for your patience and continued partnership.

2. May 27, 2026 at 5:59 PM UTCresolved

   Microsoft has resolved an issue affecting Dax/Dragon Copilot products within our US datacenter. A detailed analysis for the impact will be available within the next 10 days.

1. May 18, 2026 at 6:09 PM UTCidentified

   Microsoft is currently aware of an intermittent analytics-related impact stemming from a Microsoft Fabric / Power BI issue. Our engineering teams are actively investigating. Current symptoms include: -Service Unavailable errors -Delays when loading analytics At this time, there is no confirmed workaround. However, some users have reported intermittent success by restarting the application and retrying the operation. We will continue to provide updates as more information becomes available. Thank you for your patience while we work to resolve this issue. Azure Status Link: https://azure.status.microsoft/en-us/status

2. May 19, 2026 at 1:01 PM UTCresolved

   This incident has been resolved.

1. April 28, 2026 at 5:28 PM UTCidentified

   Microsoft is actively investigating an intermittent issue impacting Epic Nebula customers using DAX and Dragon Copilot. We are working jointly with Epic to identify the root cause. We expect to provide an update shortly regarding the scope of impact and recommended next steps. Known intermittent symptoms include: - Summaries being delayed We will share additional updates as soon as more information is confirmed. We apologize for the disruption and appreciate your continued partnership while we work to resolve this issue.

2. April 28, 2026 at 8:58 PM UTCmonitoring

   Microsoft has mitigated the issue impacting Epic Nebula customers using DAX and Dragon Copilot. Summaries are now being successfully delivered to Epic. We apologize for the disruption and appreciate your continued partnership while we worked to resolve this issue.

3. May 4, 2026 at 2:51 PM UTCresolved

   This incident has been resolved.

1. April 28, 2026 at 2:25 PM UTCidentified

   Microsoft has identified and is actively troubleshooting a recurrence of an issue affecting Dax/Dragon Copilot products. Symptoms may include: -- delayed summaries -- auto styling failures More details will be provided when information is available. We apologize for any inconvenience and appreciate your continued partnership as we work to resolve this issue.

2. April 28, 2026 at 3:39 PM UTCidentified

   There was a brief issue yesterday impacting auto styling for a small subset of DAX and Dragon Copilot customers. There was a brief reoccurrence of that same issue today, which has been quickly remediated. Some end users may have experienced delay summaries as a related impact. We are seeing improvements in system stability, and we will continue to closely monitor to confirm improved behavior. We apologize for any inconvenience and appreciate your continued partnership while we worked to resolve this issue.

3. April 28, 2026 at 3:41 PM UTCmonitoring

   There was a brief issue yesterday impacting auto styling for a small subset of DAX and Dragon Copilot customers. There was a brief reoccurrence of that same issue today, which has been quickly remediated. Some end users may have experienced delay summaries as a related impact. We are seeing improvements in system stability, and we will continue to closely monitor to confirm improved behavior. We apologize for any inconvenience and appreciate your continued partnership while we worked to resolve this issue.

4. May 4, 2026 at 2:51 PM UTCresolved

   This incident has been resolved.

1. April 16, 2026 at 1:18 PM UTCidentified

   Microsoft has identified and is investigating an intermittent service disruption in our US Data Center affecting a subset of DAX Copilot for DMO customers. Symptoms may include: Error messages indicating a problem in displaying summaries. More details will be provided when information is available.

2. April 16, 2026 at 1:42 PM UTCidentified

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

3. April 16, 2026 at 3:07 PM UTCmonitoring

   Microsoft has identified the root cause of the reported issue related to summary errors affecting a subset of DAX Copilot for DMO customers. Mitigation steps are currently underway, and encounters recorded during the impacted timeframe are expected to recover automatically. Note: There will be no data loss for impacted encounters. At this time, we recommend continuing to use the application as this issue appears to be intermittent. We apologize for any inconvenience and appreciate your continued partnership.

4. April 16, 2026 at 8:33 PM UTCmonitoring

   A fix will be deployed overnight (with no expected downtime)

5. April 16, 2026 at 8:33 PM UTCmonitoring

   We are continuing to monitor for any further issues.

6. April 17, 2026 at 12:49 PM UTCresolved

   This incident has been resolved.

1. April 14, 2026 at 2:18 PM UTCidentified

   Microsoft has identified and is actively troubleshooting an issue affecting Nuance Management Console within our US datacenter following the latest Edge browser update. More details will be provided when information is available.

2. April 14, 2026 at 2:56 PM UTCidentified

   Microsoft has identified and is working on remediation on the current NMC issue. Impact is that some admins working with the most recent Edge/Chrome browser updates, that also manage multiple organizations may be experiencing an issue with Orgnaization dropdown/selector.

3. April 14, 2026 at 8:02 PM UTCresolved

   This incident has been resolved.

1. April 10, 2026 at 6:40 PM UTCinvestigating

   We currently identified and investigating issue related to DAX Copilot for EPIC users getting an error message in Haiku stating, "Visit recording failed to load. A TLS error caused the secure connection to fail."

2. April 10, 2026 at 6:44 PM UTCinvestigating

   We are continuing to investigate this issue.

3. April 10, 2026 at 7:23 PM UTCidentified

   Microsoft is investigating an issue affecting DAX Copilot for EPIC users within our US datacenters. Symptom: Error message when attempting to initiate a session in Haiku, "Visit recording failed to load. A TLS error caused the secure connection to fail." Impact is specifically attributed to: Epic Hyperspace Embedded Launch Haiku Android Haiku iOS Enhanced View Haiku iOS Simple view (only if the client has any Android users as well) Note: Simple WebView users will not experience the issue. Microsoft is actively working on remediation and will provide more information as soon as it is available. Thank you for your patience and continued partnership.

4. April 10, 2026 at 7:42 PM UTCmonitoring

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

5. April 10, 2026 at 8:05 PM UTCresolved

   This incident has been resolved.

1. April 10, 2026 at 6:40 PM UTCidentified

   Microsoft has identified and is actively troubleshooting an issue affecting Dax/Dragon Copilot products within our US datacenter. More details will be provided when information is available.

2. April 10, 2026 at 6:41 PM UTCresolved

   This incident has been resolved.

1. April 1, 2026 at 5:04 PM UTCidentified

   Microsoft has identified and is actively troubleshooting an issue affecting Dax/Dragon Copilot products within our US datacenter. More details will be provided when information is available.

2. April 1, 2026 at 5:44 PM UTCinvestigating

   Microsoft is investigating a service disruption in our US Data Center affecting a subset of DAX Copilot customers. Symptoms may include: - Delays in encounter uploads. - Delayed availability of summaries. - Error messages indicating that a visit recording could not be started. Our engineering teams are actively working to identify the root cause and mitigate impact. We will provide additional updates as they become available. We apologize for any inconvenience and appreciate your continued partnership while we work to return to normal service levels as quickly as possible.

3. April 1, 2026 at 6:29 PM UTCinvestigating

   Microsoft has stabilized service performance for Dragon/DAX Copilot in our US Data Center. Microsoft will continue to investigate root cause and monitor the environment closely. Encounters recorded during the impacted timeframe are expected to recover automatically.

4. April 1, 2026 at 7:25 PM UTCmonitoring

   Microsoft has stabilized service performance for Dragon/DAX Copilot in our US Data Center and the environment is operating normally. We will continue to closely monitor the service while completing our root cause investigation to ensure continued stability. Encounters recorded during the impacted timeframe are expected to recover automatically. We apologize for any inconvenience and appreciate your continued partnership.

5. April 2, 2026 at 5:26 PM UTCresolved

   This incident has been resolved.