Histórico de interrupções do Samanage

1. 31 Eost 2026 da 15:15 UTCidentified

   Atualmente, estamos passando por atrasos em informações atualizadas mostrando na plataforma. tickets novos e atualizados, comentários, alterações de incidentes e atualizações de campo, como estado e título, e outras funções, são às vezes lentos para atualizar e ou mostrar informações desatualizadas. Também estamos vendo os tempos de carga da página sendo impactados. A equipe identificou a questão e está trabalhando em uma resolução. Você pode experimentar alguns atrasos à medida que lançamos a correção através da plataforma.

2. 31 Eost 2026 da 15:58 UTCmonitoring

   A correção foi implantada, e estamos processando ativamente o atraso restante das atualizações do ticket. Enquanto o processamento está em andamento, algumas atualizações de ticket podem continuar a sofrer atrasos. Esperamos que estes atrasos se resolvam à medida que o atraso for ultrapassado. Continuaremos a monitorar o sistema e fornecer atualizações adicionais à medida que o processamento progride.

3. 31 Eost 2026 da 16:50 UTCmonitoring

   Estamos vendo melhorias após a implantação da correção; estamos monitorando ativamente o sistema para garantir que o desempenho permanece estável e que todas as atualizações atrasadas são totalmente processadas.

4. 31 Eost 2026 da 17:42 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gouere 2026 da 14:30 UTCinvestigating

   Atualmente estamos investigando um problema que afeta SolarWinds Service Desk. Alguns usuários podem não ser capazes de acessar o aplicativo neste momento. Nossa equipe está trabalhando ativamente para identificar a causa e restaurar o serviço o mais rápido possível. Vamos compartilhar outra atualização assim que mais informações estiverem disponíveis.

2. 14 Gouere 2026 da 14:44 UTCinvestigating

   Continuamos a investigar esta questão.

3. 14 Gouere 2026 da 14:57 UTCinvestigating

   A aplicação é acessível novamente, e o serviço foi restaurado. Nossa equipe continua monitorando o aplicativo de perto para garantir a estabilidade. Forneceremos outra atualização se forem identificados outros problemas.

4. 14 Gouere 2026 da 15:05 UTCmonitoring

   Nossa equipe continua monitorando o aplicativo de perto para garantir a estabilidade. Outras atualizações serão compartilhadas assim que estiverem disponíveis.

5. 14 Gouere 2026 da 16:01 UTCresolved

   Após um longo período de monitoramento, o SolarWinds Service Desk está operando normalmente. Neste momento, consideramos o incidente resolvido. A análise da causa raiz (RCA) será compartilhada nos próximos dias assim que a investigação estiver concluída. Se você precisar de qualquer assistência adicional ou experimentar quaisquer outros problemas, entre em contato conosco em [email protected].

Traduzido automaticamente da atualização oficial do incidente.

1. 7 Gouere 2026 da 15:59 UTCidentified

   Estamos atualmente investigando um problema que afeta SolarWinds Service Desk, onde incidentes criados por e-mail estão sendo enviados com sucesso, e mensagens de confirmação estão sendo enviadas, mas os incidentes recém-criados podem não aparecer na página Incident Index. Nossa equipe está trabalhando ativamente para identificar a causa raiz e restaurar a visibilidade normal o mais rápido possível. Forneceremos outra atualização assim que mais informações estiverem disponíveis.

2. 7 Gouere 2026 da 16:23 UTCinvestigating

   Continuamos a investigar um problema no SolarWinds Service Desk onde novos incidentes podem não aparecer na página Incident Index, apesar de terem sido enviados com sucesso e gerarem mensagens de confirmação. A nossa equipa está a trabalhar para identificar a causa e restaurar a visibilidade normal. Vamos compartilhar outra atualização assim que mais informações estiverem disponíveis.

3. 7 Gouere 2026 da 16:57 UTCidentified

   Identificamos a causa básica do problema que afeta o SolarWinds Service Desk, onde novos incidentes podem não aparecer na página Incident Index, apesar de terem sido submetidos com sucesso. Vamos compartilhar outra atualização assim que mais informações estiverem disponíveis.

4. 7 Gouere 2026 da 18:00 UTCmonitoring

   Uma correção foi implementada para corrigir o problema que afeta SolarWinds Service Desk, onde novos incidentes podem não aparecer na página Incident Index, apesar de terem sido criados com sucesso. Continuamos a monitorar o serviço de perto para garantir que a visibilidade normal seja totalmente restaurada.

5. 7 Gouere 2026 da 19:00 UTCresolved

   Após um longo período de monitoramento, o SolarWinds Service Desk está operando normalmente. Neste momento, consideramos o incidente resolvido. Se você precisar de qualquer assistência adicional ou experimentar quaisquer outros problemas, entre em contato conosco em [email protected].

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Mezheven 2026 da 17:22 UTCinvestigating

   Estamos atualmente investigando um problema que afeta SolarWinds Service Desk, onde incidentes criados por e-mail são enviados com sucesso e mensagens de confirmação são enviadas, mas os incidentes recém-criados podem não aparecer na página Incident Index. Nossa equipe está trabalhando ativamente para identificar a causa e restaurar a visibilidade normal o mais rápido possível. Vamos compartilhar outra atualização assim que mais informações estiverem disponíveis.

2. 30 Mezheven 2026 da 17:58 UTCidentified

   Identificamos a causa do problema relatado e estamos a trabalhar numa solução o mais rápido possível. Obrigado pela vossa paciência.

3. 30 Mezheven 2026 da 18:09 UTCmonitoring

   Completamos a correção para este problema e os serviços estão voltando ao normal. Incidentes enviados por e-mail devem agora aparecer corretamente na página Incident Index, como esperado. A nossa equipa continuará a acompanhar de perto o ambiente para garantir a estabilidade e confirmar que a questão foi totalmente resolvida. Agradecemos a sua paciência enquanto trabalhávamos para resolver este problema.

4. 30 Mezheven 2026 da 19:47 UTCmonitoring

   Continuamos a monitorar de perto o comportamento enquanto nossa equipe trabalha para confirmar visibilidade consistente na lista de incidentes. Vamos compartilhar outra atualização assim que mais informações estiverem disponíveis.

5. 30 Mezheven 2026 da 21:04 UTCmonitoring

   Estamos vendo melhorias no desempenho global da aplicação. Nossa equipe continua a monitorar de perto o ambiente para garantir a estabilidade e confirmar que não há mais questões. Iremos compartilhar atualizações adicionais conforme necessário.

6. 30 Mezheven 2026 da 22:02 UTCresolved

   Após um período prolongado de monitorização, a questão não reapareceu e não recebemos quaisquer relatórios adicionais de impacto. O serviço funciona normalmente, e estamos a considerar este incidente resolvido. Se você continuar a experimentar quaisquer problemas ou precisar de mais assistência, entre em contato conosco por e-mail em [email protected], e nossa equipe ficará feliz em ajudar.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Mezheven 2026 da 16:14 UTCinvestigating

   Atualmente estamos investigando um problema em que incidentes criados por e-mail podem não aparecer imediatamente na lista de incidentes no SolarWinds Service Desk UI. Durante nossa revisão, confirmamos que as notificações de criação de incidentes estão sendo enviadas com sucesso, e os incidentes afetados podem ser acessados através de seus links diretos. Contudo, pode haver um atraso antes de esses incidentes se tornarem visíveis na lista de incidentes dentro da IU. Nossa equipe está ativamente investigando esse comportamento e trabalhando para determinar a causa. Vamos compartilhar outra atualização assim que mais informações estiverem disponíveis.

2. 23 Mezheven 2026 da 16:37 UTCmonitoring

   Estamos actualmente a acompanhar esta questão. Nossa investigação confirmou que a criação de incidentes está ocorrendo com sucesso e os e-mails de notificação estão sendo enviados como esperado. No entanto, alguns incidentes criados por e-mail podem não aparecer imediatamente na lista de incidentes dentro da UI, embora permaneçam acessíveis através do link direto incluído no e-mail de notificação. Continuamos a monitorar de perto o comportamento enquanto nossa equipe trabalha para confirmar visibilidade consistente na lista de incidentes. Vamos compartilhar outra atualização assim que mais informações estiverem disponíveis.

3. 23 Mezheven 2026 da 18:31 UTCresolved

   Nosso monitoramento indica que o problema impactando a visibilidade do incidente foi resolvido. Continuamos a acompanhar de perto o serviço e não observamos mais ocorrências do problema. Neste momento, consideramos o incidente resolvido. Se você precisar de qualquer assistência adicional ou experimentar quaisquer outros problemas, entre em contato conosco em [email protected].

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Mezheven 2026 da 12:18 UTCinvestigating

   We are currently investigating reports of slow performance issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.

2. 3 Mezheven 2026 da 13:03 UTCidentified

   We have identified the cause of the reported issue and are actively working to implement a fix as quickly as possible. Thank you for your patience and understanding while we work toward a resolution.

3. 3 Mezheven 2026 da 13:32 UTCmonitoring

   We are seeing improved performance on our end and are continuing to monitor the situation closely. We are also working to confirm whether customers are experiencing similar improvements as we continue our efforts to ensure full service stability. We appreciate your patience and understanding during this time. We will provide another update as soon as additional information becomes available.

4. 3 Mezheven 2026 da 14:26 UTCresolved

   We have continued to monitor the service and have not observed any further issues. In addition, we have not received any new reports of slow performance. Based on our monitoring and the current system status, this incident is considered resolved. Should you require any further assistance or experience any additional issues, please do not hesitate to contact us at [email protected]. Thank you for your patience and cooperation throughout this process.

1. 6 Mae 2026 da 13:23 UTCinvestigating

   We are aware of an issue that caused the application to be unavailable for a few minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.

2. 6 Mae 2026 da 13:53 UTCmonitoring

   The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.

3. 6 Mae 2026 da 15:25 UTCresolved

   Following an extended monitoring period, the issue has not reappeared, and no further impact has been reported. Services are operating normally, and we consider this incident resolved. If you experience any additional issues or need assistance, please contact us at [email protected], and our team will be glad to help.

1. 29 Ebrel 2026 da 19:01 UTCinvestigating

   We are aware of an issue that caused the application to be unavailable for approximately two minutes. Our team is currently investigating the cause and monitoring the service to ensure it remains stable. Further updates will be posted here as more information becomes available.

2. 29 Ebrel 2026 da 19:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 Ebrel 2026 da 19:56 UTCmonitoring

   The services are currently operating normally, and our engineering team is closely monitoring system performance to ensure continued stability. We will provide additional updates here if we observe any further impact or if additional action is required.

4. 29 Ebrel 2026 da 23:28 UTCresolved

   After an extended period of monitoring, the issue has not resurfaced and we have not received any additional reports of impact. Service is operating normally and we are considering this incident resolved. If you continue to experience any issues or need further assistance, please contact us via email at [email protected], and our team will be happy to help.

1. 3 Ebrel 2026 da 12:33 UTCinvestigating

   We are currently investigating reports of slow performance and intermittent Error 500 issues in SolarWinds Service Desk. Our team is working to resolve this as quickly as possible.

2. 3 Ebrel 2026 da 13:00 UTCidentified

   We've identified the cause of the reported issue and are working on a fix as quickly as possible. Thank you for your patience.

3. 3 Ebrel 2026 da 13:42 UTCmonitoring

   We have completed the fix for this issue and will continue to monitor the situation to ensure stability.

4. 3 Ebrel 2026 da 15:08 UTCinvestigating

   We have observed unexpected behavior following the recent fix and are currently reviewing the issue. Our team is continuing to investigate while working to ensure full stability. We appreciate your patience and will provide further updates as soon as more information becomes available.

5. 3 Ebrel 2026 da 16:29 UTCinvestigating

   We are actively investigating continued unexpected behavior following a recent fix. Our team is working to ensure full stability. We appreciate your patience and will share another update as soon as more information is available.

6. 3 Ebrel 2026 da 17:56 UTCmonitoring

   We are seeing improved results on our end and are continuing to monitor performance closely. We are also working to confirm whether customers are seeing similar improvement while we continue to ensure full stability. We appreciate your patience and will provide another update as soon as more information becomes available.

7. 3 Ebrel 2026 da 21:57 UTCresolved

   We have continued to monitor the service and have not observed any further issues. Additionally, we have not received any new reports of slow performance or Error 500 errors. At this time, the incident is considered resolved. If further assistance is needed, please contact [email protected]. Thank you for your patience throughout this process.

1. 18 Meurzh 2026 da 09:14 UTCinvestigating

   We have received reports of overlapping text fields in Incident/Service Request tickets and are currently investigating the issue.

2. 18 Meurzh 2026 da 09:46 UTCidentified

   We have identified the cause of the overlapping text fields and are currently working on a fix. We will provide updates as soon as progress is made. Thank you for your patience and understanding.

3. 18 Meurzh 2026 da 11:52 UTCidentified

   We are still working on fixing the issue. We will continue to monitor the situation and provide updates as they become available.

4. 18 Meurzh 2026 da 11:57 UTCidentified

   We will deploy a fix shortly. We will provide an update once it has been deployed.

5. 18 Meurzh 2026 da 12:26 UTCidentified

   We are in the process of deploying the fix. We will keep you updated as progress continues.

6. 18 Meurzh 2026 da 12:47 UTCmonitoring

   We have completed the deployment of the fix for this issue and will continue to monitor the situation to ensure stability.

7. 18 Meurzh 2026 da 13:30 UTCresolved

   This issue has been resolved.

1. 2 Cʼhwevrer 2026 da 15:49 UTCinvestigating

   We are currently experiencing performance issues in the Service Desk Application, and our team is investigating. This impacts actions such as navigating through the Incidents page and other areas of the app.

2. 2 Cʼhwevrer 2026 da 16:21 UTCinvestigating

   We have identified elevated load on the database layer in our US Service Desk environment. This is leading to slow page loads, delayed data population, and intermittent 504 Gateway Timeout errors for some customers. Our team is actively working on remediation to reduce database load and restore normal performance. During this time, the application may run more slowly than normal. We will provide the next update within 30 minutes or sooner as we make progress.

3. 2 Cʼhwevrer 2026 da 16:50 UTCidentified

   We are still actively working on reducing the elevated database load in our US Service Desk environment. The underlying issue has been identified, and our team is continuing remediation efforts to stabilize performance.

4. 2 Cʼhwevrer 2026 da 17:26 UTCidentified

   We are continuing to work on a fix for this issue and further reducing the elevated database load in our US Service Desk environment. Some users may still experience intermittent slowness or timeouts while we complete these changes. We will provide another update within 30 minutes or as soon as we have more information.

5. 2 Cʼhwevrer 2026 da 18:19 UTCmonitoring

   We have implemented a fix for the database load issue affecting our US Service Desk environment; we are restarting a set of frontend services to complete remediation. Users should now begin to see improved performance and fewer timeouts as these changes take effect. Our team will continue to closely monitor the environment and will provide another update once performance is fully stabilized.

6. 2 Cʼhwevrer 2026 da 18:55 UTCresolved

   We have resolved the database load issue affecting our US Service Desk environment and restarted the impacted frontend services. Since then, performance has remained stable under monitoring, and we are no longer observing elevated errors or timeouts. This incident is now closed. If you continue to experience slowness or errors, please contact SolarWinds Support or open a ticket so we can investigate further.

1. 28 Genver 2026 da 19:54 UTCinvestigating

   We are investigating an issue where some users are unable to fully load service (catalog) requests. Affected pages may briefly appear and then show blank or incomplete content. Our engineering team is actively investigating the cause and working to restore full functionality. We will provide updates on this page as more information becomes available. If you are impacted and need assistance, please contact SolarWinds Support through your usual channels.

2. 28 Genver 2026 da 20:08 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 Genver 2026 da 20:43 UTCinvestigating

   Our investigation has determined that this issue is limited to a subset of Service Desk service requests and service catalog items and does not affect all users or all catalogs. We are continuing to investigate the underlying cause and will provide additional updates on this page as our work progresses.

4. 28 Genver 2026 da 21:29 UTCidentified

   We have identified the root cause of the issue. It occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account within the affected Service Desk instance. Our engineering team is actively working on a fix. Additional updates will be provided on this page as progress continues.

5. 28 Genver 2026 da 23:17 UTCidentified

   We are actively working on a fix for this issue. As a reminder, the cause occurs when a process workflow includes a Send Notification action that sends an email to a user or email address that does not have a valid user account in the affected Service Desk instance. As a temporary workaround, service desk administrators can update the affected workflows so that Send Notification actions are configured to send emails to a named user with a valid Service Desk account instead of an email address that is not associated with a user. We will provide further updates on this page as our work progresses.

6. 29 Genver 2026 da 01:41 UTCidentified

   Our engineering team has prepared a fix for this issue, and the deployment process has started. During the deployment window, some users may experience brief slowdowns or intermittent delays; we expect any impact to be minimal and temporary. We will provide a further update on this page once the deployment has finished.

7. 29 Genver 2026 da 03:30 UTCmonitoring

   Our Engineering team has successfully applied a fix and is applying it retroactively to resolve the issue for all affected users. Any interruptions during this process should be minimal. We will provide another update in the next hour.

8. 29 Genver 2026 da 05:38 UTCmonitoring

   Our Engineering team is continuously working on applying a fix to the data for all affected users. Further updates will be provided in the next hour.

9. 29 Genver 2026 da 08:19 UTCmonitoring

   Our Engineering team is actively deploying a remediation to address issues resulting in page load failures, blank pages, or incomplete content. Further updates will be provided as progress continues.

10. 29 Genver 2026 da 11:05 UTCmonitoring

    Our team is in the final stages of deploying the fix. We expect completion shortly and will share an update immediately.

11. 29 Genver 2026 da 11:28 UTCmonitoring

    The fix deployment is now complete, and our team is closely monitoring the results to ensure stability.

12. 29 Genver 2026 da 14:12 UTCresolved

    We are marking this issue as resolved, as we have confirmed that all new service requests work correctly and previously submitted requests work as intended. If the issue resurfaces or if you require any further assistance, please don’t hesitate to contact us at [email protected].

1. 27 Genver 2026 da 18:51 UTCinvestigating

   We are currently investigating an issue affecting Service Requests for customers in the US and AU regions. Initial findings indicate that when the approval process is configured to use the Incident Assignee as the approver, the workflow may terminate unexpectedly with the following error: “The task [Task Name] has been automatically declined per predefined approval conditions because the approval step contains unknown approvers.” Our engineering teams are actively working to identify the root cause and determine a resolution. If you have questions, are experiencing related issues, or would like to provide additional details, please contact us via chat or email at [email protected]. We will continue to provide updates as more information becomes available.

2. 27 Genver 2026 da 19:48 UTCinvestigating

   Our team is actively investigating the issue, which may be related to a recent deployment. We are working to identify the root cause and resolve it, and we will provide updates as more information becomes available. Thank you for your patience.

3. 27 Genver 2026 da 21:49 UTCinvestigating

   Our team is continuing to investigate the issue and is focused on identifying the root cause and resolving it as quickly as possible. We will provide updates as new details become available. Thank you for your patience.

4. 27 Genver 2026 da 23:13 UTCidentified

   We have identified the root cause of the issue affecting Service Request approval workflows for customers in the US and AU regions. We are currently testing a fix. Once testing is complete, we will proceed with deployment and share further updates.

5. 28 Genver 2026 da 03:44 UTCidentified

   The fix we had in place did not resolve the issue as expected. Our Engineering team has identified and is currently working on a resolution. Our team is preparing for the deployment, which is expected to be completed within the next hour. If this changes, we will provide an update immediately.

6. 28 Genver 2026 da 04:49 UTCresolved

   This issue has been resolved.

1. 27 Genver 2026 da 00:03 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in the AU Data Center, where newly created objects, such as tickets and assets, are not appearing in the user interface as expected. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 27 Genver 2026 da 01:23 UTCmonitoring

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

3. 27 Genver 2026 da 02:09 UTCresolved

   This incident has been resolved.

1. 12 Genver 2026 da 19:49 UTCinvestigating

   We are currently seeing performance slowness within the Service Desk Application, and our team is investigating this matter. This impacts actions such as navigating through the Incidents page and other areas of the app.

2. 12 Genver 2026 da 22:55 UTCinvestigating

   The platform performance has greatly improved, and while that is the case, we are still seeing delays, at times, when navigating between pages. The engineering team found a high load on the database, which has been cleared for a couple of hours, and are now focusing efforts on the remaining delay issues. You can expect the next update in one hour.

3. 13 Genver 2026 da 02:23 UTCresolved

   This issue has been resolved.

1. 12 Genver 2026 da 07:43 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in the AU Data Center. New tickets are not appearing in the UI. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 12 Genver 2026 da 12:28 UTCresolved

   This issue has been resolved.

1. 9 Genver 2026 da 09:27 UTCinvestigating

   We are aware of an issue affecting a scheduled Service Desk service catalog item in our EU data center. Our team is actively working to identify the root cause and restore normal functionality. Additional updates will be shared as they become available.

2. 9 Genver 2026 da 09:36 UTCidentified

   Additional resources have been allocated to help manage the queue. As a result, the backlog is now being processed efficiently, and pending items are getting cleared. Additional updates will be shared as they become available.

3. 9 Genver 2026 da 10:09 UTCmonitoring

   Scheduled service catalog item are now being processed. We are monitoring the situation closely to ensure continued stability.

4. 9 Genver 2026 da 11:00 UTCresolved

   This incident has been resolved.

1. 6 Genver 2026 da 10:47 UTCinvestigating

   We are currently investigating an issue affecting Service Desk in EU Data Center. Round-robin assignment and Automation Rules process are delayed, this affects automation assigning and or updating incidents. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 6 Genver 2026 da 11:14 UTCinvestigating

   We have identified performance degradation in the Service Desk application within EUDC. This issue is impacting multiple functionalities of the application. Our team is actively investigating the issue and working to identify the root cause. Further updates will be shared as more information becomes available.

3. 6 Genver 2026 da 14:32 UTCmonitoring

   Service Desk EU data-center degradation issue affecting the application has now been restored. System performance is now normal and the application is operating as expected. We continue to monitor performance closely to ensure ongoing stability and reliability.

4. 6 Genver 2026 da 17:59 UTCresolved

   This incident has been resolved.

1. 5 Genver 2026 da 13:35 UTCinvestigating

   We are currently investigating an issue affecting the Service Desk in our EU Data Center. The round-robin automatic assignment is not working as expected, and newly created tickets are not being assigned to a user or group automatically. Our team is actively working to identify the root cause and will provide updates as soon as more information becomes available. We appreciate your patience and understanding.

2. 5 Genver 2026 da 16:13 UTCmonitoring

   A fix has been implemented. We will continue to monitor until we can confirm that no additional impact is expected.

3. 5 Genver 2026 da 19:13 UTCresolved

   This incident has been resolved.

1. 18 Du 2025 da 13:32 UTCmonitoring

   We're currently experiencing an upstream vendor outage. This is affecting services, and you may see failures in items such as VA (Virtual Agent) functionality and custom domain routing. Our teams are monitoring the situation closely for updates.

2. 18 Du 2025 da 14:16 UTCmonitoring

   Our upstream vendor are continue working on restoring service for application services.

3. 18 Du 2025 da 15:33 UTCmonitoring

   Based on the recent update from our upstream vendor they have implemented a fix to resolve the issue. Our team is continuously monitoring for updates.

4. 18 Du 2025 da 19:23 UTCmonitoring

   Our upstream vendor’s issue has been resolved, and we are no longer seeing any impact on our platform. We will continue to closely monitor the fix.

5. 18 Du 2025 da 23:17 UTCresolved

   This issue has been resolved. Please contact us at [email protected] if you need further assistance.