Viedoc Outage History

Started Sep 08, 2026, 02:07 PM UTC· resolved Sep 11, 2026, 08:25 AM UTC

1. investigating Sep 08, 2026, 02:07 PM UTC

   Email alerts triggered by EDC actions in Viedoc have been failing intermittently on the EU production instance during the following time windows: Monday, August 31, 11:02–17:25 CEST Thursday, September 3, 13:31 CEST – Friday, September 4, 22:07 CEST Most emails are being sent as expected, but a subset are delayed or, in some cases, not delivered at all. No other instances are affected. We are actively investigating and will post updates as more information becomes available.

2. monitoring Sep 10, 2026, 01:51 PM UTC

   We have not observed any new email failures since our previous report. We are now monitoring the situation and will post a further update once we can confirm the issue is fully resolved.

3. resolved Sep 11, 2026, 08:25 AM UTC

   This incident has been resolved.

4. postmortem Sep 17, 2026, 08:12 AM UTC

   **Sporadic Email Failures on EU Production Instance** ‌ **Description**‌ During the two windows below, email alerts triggered by actions in Viedoc were sent intermittently. Most were delivered as expected. A subset were delayed, and some were not delivered at all. * Monday, August 31, 11:02–17:25 CEST * Thursday, September 3, 13:31 CEST – Friday, September 4, 22:07 CEST Email alerts in Viedoc are not sent by the application at the moment a user saves data. They are produced by background processing that runs immediately afterwards and decides, based on your study's configuration, which alerts need to be sent. During these two windows that background processing did not always complete, so the alerts it would have produced were delayed or never generated. ‌ Data entered and saved by users during these periods was stored as expected. The interruption affected work handled by particular processing servers rather than the platform as a whole, which is why alerts were intermittent rather than stopping entirely. ‌ **Cause** Viedoc's background processing runs across several servers working in parallel. Each server needs a working connection to a shared internal service that Viedoc uses to coordinate this work safely - for example, to ensure two servers never process the same subject at the same moment.‌ During these windows, individual servers lost that connection and did not re-establish it. An affected server continued to accept work but could not complete it. Other servers running at the same time were unaffected, which is why the impact was intermittent and why the platform continued to appear healthy overall. ‌ **Corrective action** * The affected servers were identified and replaced. Normal processing, including alert generation, resumed immediately afterwards. * We confirmed that subsequent processing completed correctly, and that no further email failures occurred. ‌ **Preventative action** Increased monitoring We have increased the monitoring and added alerting that detects this specific failure on \*\*any individual server\*\* much faster, preventing this to fail silently. ‌ Underlying cause - ongoing investigation ‌The investigation into why these connections failed remains open, and we are treating it as separate from the mitigations above.

Read the full incident report →

Started Sep 04, 2026, 03:00 PM UTC· resolved Sep 04, 2026, 03:00 PM UTC

1. resolved Sep 04, 2026, 04:15 PM UTC

   We had a temporary disturbance which led to customers not being able to reach out .cn portals between about 23:00 and 00:00. The problem was in our infrastructure and we apologize for the inconvencience. Systems are back to normal and there are no issues with confidentiality or integrity. This problem only affected access to our systems.

Read the full incident report →

Started Aug 17, 2026, 09:54 AM UTC· resolved Aug 17, 2026, 11:20 AM UTC

1. monitoring Aug 17, 2026, 09:54 AM UTC

   We are experiencing inssues in an underlying platform component from Azure in the France Central region, this is creating some loss of traffic which you can experience as the service not being available for short periods of time. We are investigating and will keep you posted here.

2. monitoring Aug 17, 2026, 10:09 AM UTC

   We are continuing to monitor for any further issues.

3. resolved Aug 17, 2026, 11:25 AM UTC

   Incident has now been resolved by Microsoft and we can confirm that Viedoc suite is fully operational again. We apologize for the inconvenience.

4. postmortem Aug 17, 2026, 12:27 PM UTC

   ## Summary We have experienced issues in an underlying platform component from Azure \(Azure App services\) in the France Central region, which created some loss of traffic which customers experienced as the service not being available. Our system monitoring caught the issues immediately and alerted our platform team which responded within 1 minute. We could confirm within 15 minutes that the problem was with the Platform provider. ## Instances affected All products in Europe instance ## Duration 2026-08-17 09:32 UTC to 2026-08-17 11:20 UTC. ## Root Cause An infrastructure component in Microsoft Azure Cloud responsible for processing incoming requests within the Azure App Service platform in the France Central region exceeded operational thresholds, reducing the availability of service resources supporting customer work-loads. As a result, Viedoc experienced intermittent availability issues and failed requests. ## Impact This affected Viedoc availability without affecting data confidentality, integrity or privacy. ## Actions Followup with platform provider about capacity.

Read the full incident report →

Started Jul 29, 2026, 12:07 PM UTC· resolved Jul 29, 2026, 05:06 PM UTC

1. investigating Jul 29, 2026, 01:35 PM UTC

   We are currently investigating this issue, update coming soon.

2. investigating Jul 29, 2026, 02:11 PM UTC

   The issue correlates with a data center decommissioning in China and we are continuing to investigate.

3. resolved Jul 29, 2026, 05:06 PM UTC

   The incident was identified as a problem within Azure Cloud China and we have confirmation now that the problem has been mitigated. Once we have a root-cause analysis we will update with an incident report. We apologize for any inconvenience.

4. postmortem Jul 31, 2026, 01:23 PM UTC

   ## Summary Our China region suffered an outage due to a configuration fault in our platform provider related to internal messaging between our system components, effectively rendering our product suite unusable for a period of 4 hours and 40 minutes. Customer impact is expected to be low due to this being nighttime in China with normally very low traffic volume. Our system monitoring caught the issues immediately and alerted our platform team which responded within 1 minute and we could confirm within 1 hour that the problem was with the Platform provider. A type A support ticket was logged with our platform provider who could confirm that they indeed had an issue 2 hours and 32 minutes later, and it was resolved 38 minutes after that. ## Instances affected All products in China instance ## Duration 2026-07-29 12:07 UTC to 2026-07-29 16:47 UTC. ## Root Cause A configuration error by our platform provider in China, 21ViaNet/Microsoft Azure Cloud China. ## Impact Availability only. Data integrity and data confidentiality unaffected. ## Actions Followup with platform provider about improving their operating procedures, monitoring and incident response.

Read the full incident report →

Started Jul 09, 2026, 09:40 PM UTC· resolved Jul 16, 2026, 09:42 AM UTC

1. identified Jul 09, 2026, 09:40 PM UTC

   Since the 4.95 release, Viedoc Me submissions have been recorded in the database using UTC time rather than the site's local time zone. If the UTC date and the site's local date differ at the time of submission, the Event date in Viedoc Clinic will incorrectly reflect the UTC date instead of the local date. Depending on the data entry windows defined in the study design, this may also result in out-of-window queries. The audit trail in the Viedoc Clinic UI, accessed via "Show History," displays the correct date and time stamp according to the local time zone. This issue affects both the current and legacy versions of the Viedoc Me application. The issue has been identified, and a fix is currently being prepared. The fix will ensure new submissions are stored using the site's local time zone, but it will not correct timestamps or out-of-window queries that have already occurred. These will be addressed in a future update.

2. identified Jul 14, 2026, 02:57 PM UTC

   We are actively working to resolve this issue as quickly as possible. A hotfix is currently being finalized and tested, and we estimate it will be released to production in the first half of next week.

3. identified Jul 16, 2026, 06:53 AM UTC

   We will begin releasing the hotfix to production environments during the day today. An update will be posted once the release is complete on all instances.

4. resolved Jul 16, 2026, 09:42 AM UTC

   The incident has been resolved with the release of hotfix 4.95.2 to all training and production instances. This release prevents the issue from recurring going forward. However, Event dates already recorded in UTC will remain unchanged for now, and any out-of-window queries already triggered by this issue will also remain until corrected. Submissions currently stored in UTC will be corrected at a later date. The timing for this correction has not yet been confirmed.

Read the full incident report →

Started Jun 10, 2026, 06:32 PM UTC· resolved Jun 17, 2026, 10:40 AM UTC

1. investigating Jun 10, 2026, 06:32 PM UTC

   After the Viedoc 4.95 release, when a revision is applied to a form containing a repeating item group, and a user upgrades the form from the landing page, data previously entered in the repeating item group is cleared. The issue is occurring on the EU and US training and production instances. Investigation is ongoing. Until further information is known, we advise all customers to refrain from applying revisions requiring form upgrades on forms containing repeating item groups.

2. identified Jun 10, 2026, 11:31 PM UTC

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

3. identified Jun 16, 2026, 02:45 PM UTC

   Hotfix 4.95.1 has been released on the US training and production instances. The incident is resolved on those instances. The hotfix will be deployed to EU training and production instances tomorrow.

4. resolved Jun 17, 2026, 10:40 AM UTC

   Hotfix 4.95.1 has been released on the EU training and production instances. The incident is now resolved on all instances.

Read the full incident report →

Started Jun 03, 2026, 12:12 PM UTC· resolved Jun 03, 2026, 01:23 PM UTC

1. monitoring Jun 03, 2026, 12:12 PM UTC

   Temporary operational disturbance observed in the Viedoc suite on the Chinese instance (clinic.viedoc.cn).

2. resolved Jun 03, 2026, 01:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 28, 2026, 05:30 AM UTC· resolved May 28, 2026, 06:40 AM UTC

1. investigating May 28, 2026, 07:35 AM UTC

   Operational disturbance observed in Viedoc suite on the Chinese instance (clinic.viedoc.cn). Investigations are ongoing since 07:20 GMT+2

2. resolved May 28, 2026, 07:38 AM UTC

   The incident has been resolved since 08:40 GMT+2

Read the full incident report →

Started May 06, 2026, 09:48 AM UTC· resolved May 11, 2026, 09:54 AM UTC

1. identified May 06, 2026, 09:48 AM UTC

   After the Viedoc 4.94 release, the following issues affect the EU and US training and production instances: - Users cannot approve randomization configurations in Viedoc Admin when kit allocation is not used. Randomization and kit allocation in Viedoc Clinic are not affected. - WHO Drug dictionary terms are not loading as expected in the legacy medical coding tool. The new medical coding tool is not affected. We are working on a fix for these issues.

2. identified May 07, 2026, 06:34 AM UTC

   After the Viedoc 4.94 release, the following issues affect the EU and US training and production instances: - Users cannot approve randomization configurations in Viedoc Admin when kit allocation is not used. Randomization and kit allocation in Viedoc Clinic are not affected. - WHO Drug dictionary terms are not loading as expected in the legacy medical coding tool. The new medical coding tool is not affected. - Intermittent failures in Designer, where users are unexpectedly logged out, are affecting certain users. We are working on a fix for these issues, and the Designer issue is currently under investigation.

3. identified May 08, 2026, 08:22 AM UTC

   A hotfix is currently being prepared and will be deployed to both our EU and US instances. Based on preliminary timelines, we expect this release to go out on Monday, May 11.

4. resolved May 11, 2026, 09:54 AM UTC

   This incident was resolved this morning with the release of hotfix version 4.94.1 on both the EU and US instances.

Read the full incident report →

Started Apr 27, 2026, 11:00 AM UTC· resolved Apr 27, 2026, 07:00 PM UTC

1. investigating Apr 27, 2026, 01:04 PM UTC

   Operational disturbance observed in Viedoc 4 on the European instance (v4.viedoc.net). Investigations are ongoing.

2. investigating Apr 27, 2026, 05:40 PM UTC

   Microsoft Azure experienced a power event at their France Central datacenter, caused by a loss of utility power from an external provider. Power has since been restored via backup generators and recovery is underway. As of now, there are no active disruptions to Viedoc services, and we continue to monitor the situation closely.

3. monitoring Apr 27, 2026, 05:42 PM UTC

   Microsoft Azure experienced a power event at their France Central datacenter, caused by a loss of utility power from an external provider. Power has since been restored via backup generators and recovery is underway. As of now, there are no active disruptions to Viedoc services, and we continue to monitor the situation closely.

4. resolved Apr 27, 2026, 07:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 09, 2025, 09:37 AM UTC· resolved Dec 09, 2025, 12:20 PM UTC

1. investigating Dec 09, 2025, 09:37 AM UTC

   We have received reports of intermittent delivery failures affecting text messages sent to numbers with country codes +31 (Netherlands), +32 (Belgium), +33 (France), and +44 (United Kingdom). An investigation is currently underway together with the subproccessor. The default SMS sender is changed from a phone number to "Viedoc" to reduce the risk of texts being treated as spam.

2. resolved Dec 09, 2025, 12:20 PM UTC

   Since 10.30 CET today text messages are delivered as expected to numbers with country codes previously listed.

Read the full incident report →

Started Dec 05, 2025, 12:25 PM UTC· resolved Dec 16, 2025, 03:18 PM UTC

1. identified Dec 05, 2025, 12:25 PM UTC

   The User Administration Log (Excel) and Log of Users and Roles (PDF) cannot currently be generated for studies containing more than 100 users. This issue was introduced in the 4.90 release and affects all instances where version 4.90 has been deployed. The root cause has been identified, and a corrective fix is currently in preparation.

2. identified Dec 09, 2025, 08:30 AM UTC

   A fix has been developed and is currently undergoing testing. The fix is planned to be deployed as a hotfix.

3. resolved Dec 16, 2025, 03:18 PM UTC

   This issue has been resolved with the release of Viedoc 4.90.1, which was deployed to all production instances on 2025-12-16. The User Administration Log (Excel) and Log of Users and Roles (PDF) can now be generated as expected, including for studies containing more than 100 users.

Read the full incident report →

Started Dec 01, 2025, 01:10 PM UTC· resolved Dec 02, 2025, 08:21 AM UTC

1. identified Dec 01, 2025, 01:10 PM UTC

   Since around 12.30 CET, 1st of December, Viedoc is not sending any emails from the EU and US training and production instances due to a service disruption. The issue has been identified and we are working with our subprocessor to resolve the issue. All emails triggered during the affected period have been queued and will be delivered. The incident is caused by a malfunction at one of our subprocessors.

2. monitoring Dec 01, 2025, 01:46 PM UTC

   The email queue is currently being processed, and messages are being delivered, although with a temporary delay.

3. resolved Dec 02, 2025, 08:21 AM UTC

   The queue had been fully processed at around 9.20 PM CET on 2025-12-01. Since that time emails have been delivered without delay.

Read the full incident report →

Started Nov 25, 2025, 01:31 PM UTC· resolved Nov 26, 2025, 09:08 AM UTC

1. monitoring Nov 25, 2025, 01:31 PM UTC

   Between 13:22 CET and 14:12 CET on 25 November 2025, Viedoc did not send any emails from the EU training and production instance due to a service disruption. The issue was identified and fully resolved at 14:12 CET, after which email processing resumed as normal. All emails triggered during the affected period have been queued and will be delivered. The incident was caused by a malfunction at one of our subprocessors.

2. monitoring Nov 25, 2025, 02:16 PM UTC

   The email queue is currently being processed, and messages are being delivered, although with a temporary delay.

3. resolved Nov 26, 2025, 09:08 AM UTC

   The queue had been fully processed at around 5.30 PM CET on 2025-11-25.

Read the full incident report →

Started Nov 11, 2025, 11:55 AM UTC· resolved Nov 11, 2025, 11:55 AM UTC

1. resolved Nov 11, 2025, 11:55 AM UTC

   The planned release of version 4.89 to the CN training and production instances has been cancelled due to unforeseen technical issues specific to the Chinese server environment. As the 4.90 release is already scheduled for December, we will proceed directly from version 4.88 to 4.90 for the CN training and production instances. The impact to end users is minimal, as version 4.89 contains only non-critical bug fixes. No other instances or regions are affected by this change. We appreciate your understanding and apologize for any inconvenience this may cause.

Read the full incident report →

Started Nov 02, 2025, 10:30 PM UTC· resolved Nov 02, 2025, 11:54 PM UTC

1. resolved Nov 03, 2025, 01:27 PM UTC

   From approximately 23.44 UTC to 23.54 UTC, users faced issues logging in to the European production instance. Investigations to find the root cause are ongoing. No other instances were affected.

2. postmortem Nov 10, 2025, 10:45 AM UTC

   Description From approximately 23.44 UTC to 23.54 UTC on 2025-11-02, users were unable to log in to the European production instance. It is possible that users faced sporadic issues logging in also between approximately 23.00 UTC and 23.44 UTC. No other instances were affected. ‌ Cause The cause of the issue was an unexpected error in the identity provider \(idp\), leading to an accumulating memory consumption during the evening \(UTC\) of 2025-11-02. From approximately 23.00 UTC users would face sporadic failures when trying to log in. From approximately 23.44 UTC users could not log in. At 23.54 UTC on 2025-11-02 the idp was restarted, and users could log in as expected again. ‌ Corrective Action Alerts were triggered when the idp did not respond and the idp was restarted again at 2354 UTC on 2025-11-02. After the restart users could log in as expected again. ‌ Preventive Action Preliminary investigation identified a few improvements that could be made to make the idp more resilient. Implementation of these improvements have been initiated while the investigation of the issue continues.

Read the full incident report →

Started Sep 02, 2025, 01:56 PM UTC· resolved Sep 03, 2025, 02:27 PM UTC

1. investigating Sep 02, 2025, 01:56 PM UTC

   Emails triggered from EDC actions in Viedoc has been failing sporadically on the EU production instance since approximately 9AM CEST 2025-09-02. No other instances are affected. Investigations are ongoing.

2. identified Sep 03, 2025, 08:49 AM UTC

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

3. monitoring Sep 03, 2025, 11:25 AM UTC

   A fix has been implemented and emails are now being sent as expected. We will continue to monitor the situation.

4. resolved Sep 03, 2025, 02:27 PM UTC

   Since approximately noon CEST, emails triggered from the EDC has been delivered as expected.

5. postmortem Sep 09, 2025, 08:22 PM UTC

   **Description** Between 9AM CEST on 2025-09-02 and noon CEST 2025-09-03 there were sporadic failures in email alerts expected to be triggered from Viedoc on the EU production instance. No other instances were affected. Customers were initially informed through the status page at 15.56 CEST on 2025-09-03. ‌ **Cause** On Tuesday at 9AM CEST on 2025-09-02, there was a very high load on the system. The high load on the system caused worker function apps, used to handle various processes in the EDC, to scale out to the maximum use of 20 instances in parallel. This caused failures, and in combination with in-built retry policy of failing actions, there was an overload on the system. While form save and form view continued to work as expected throughout the duration of the issue, there were sporadic errors in specific system actions in the post-processing step. * EDC email alerts, configured in the CRF design, were sporadically not sent during this time window. It did not affect all emails. * Terms defined to be coded in the medical coding tool sporadically failed to sync to Viedoc Coder. It did not affect all terms. ‌ **Corrective action** Once the root cause of the exceptions was identified, the worker function app was gradually scaled down to run on 4 instances to avoid having too many actions ongoing at the same time. This work begun around 11AM CET on 2025-09-03 and an immediate improvement could be seen. Around noon 2025-09-03 the situation was completely resolved, and all emails could be sent as expected again. ‌ Email alerts not sent during this issue could not be re-sent and will also not show up in the communication log. ‌ All terms that had not synced properly with Viedoc Coder during the issue, were synced with Viedoc Coder on the afternoon of 2025-09-03 and 2025-09-04. ‌ **Preventive action** Scaling down the worker function app to run on 4 instances is not considered to bring any noticeable impact on performance, but will ensure the same overload issue will not occur again. An evaluation will be performed if it is necessary to scale up the worker function app again and if so, how this could be done without causing any similar issues.

Read the full incident report →

Started Aug 25, 2025, 11:29 AM UTC· resolved Aug 28, 2025, 01:11 PM UTC

1. investigating Aug 25, 2025, 11:29 AM UTC

   When exporting custom reports in xptv8 format through Viedoc Reports, and using an %xpt2loc macro to import the data to SAS, the macro can fail when using long labels for columns. Investigation is ongoing.

2. resolved Aug 28, 2025, 01:11 PM UTC

   The issue has been resolved with a hotfix on Viedoc Reports. When exporting custom reports in xptv8 format from Viedoc Reports, using an %xpt2loc macro to import the data to SAS will now work as expected also when using long labels for columns.

Read the full incident report →

Started Aug 19, 2025, 05:38 PM UTC· resolved Aug 19, 2025, 06:32 PM UTC

1. investigating Aug 19, 2025, 05:38 PM UTC

   Intermittent network disturbance observed on the Chinese instance (clinic.viedoc.cn). There are problems to reach the instance from time to time. Investigations are ongoing.

2. monitoring Aug 19, 2025, 06:07 PM UTC

   Access to Chinese instance is stable again. Continue monitoring status.

3. resolved Aug 19, 2025, 06:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2025, 03:17 PM UTC· resolved Jul 25, 2025, 01:32 PM UTC

1. investigating Jul 23, 2025, 03:17 PM UTC

   There have been reports of degraded eTMF performance (slow load times) on the Europe server. The root cause is currently under investigation.

2. resolved Jul 25, 2025, 01:32 PM UTC

   After 24 hours of monitoring, this issue has been resolved after completion of maintenance aimed at correcting networking issues. Proactive monitoring will continue. Thank you for your patience in this matter.

Read the full incident report →

Started Jul 14, 2025, 01:50 AM UTC· resolved Jul 14, 2025, 02:47 PM UTC

1. resolved Jul 14, 2025, 02:29 PM UTC

   The US production experienced some operational disturbance and was inaccessible for all users between 1:50AM UTC and 06:29AM UTC on 2025-07-14. Intermittent issues with accessing Viedoc Me on the US production instance between 10:44PM UTC (2025-07-13) - 2:47PM UTC (2025-07-14) Investigation on how to prevent these issues from happening again is ongoing. No other instance was affected.

Read the full incident report →

Started Mar 26, 2025, 09:12 PM UTC· resolved Mar 26, 2025, 10:59 PM UTC

1. investigating Mar 26, 2025, 09:12 PM UTC

   There are currently issues accessing the TMF on the US training (clinictraining.us.viedoc.com) and US production instance (clinic.us.viedoc.com). No other instances are affected. Investigations are ongoing.

2. resolved Mar 26, 2025, 10:59 PM UTC

   This incident has been resolved and users on the US training and production instance can now launch the TMF as expected again.

Read the full incident report →

Started Jan 24, 2025, 08:20 PM UTC· resolved Jan 26, 2025, 08:47 PM UTC

1. investigating Jan 24, 2025, 08:20 PM UTC

   There are currently issues with generating pdf documents (blank CRFs, annotated CRFs and study workflow) in Viedoc Designer on the European training and production server. This is currently being investigated. No other regions are affected by the issue.

2. resolved Jan 26, 2025, 08:47 PM UTC

   Pdf documents (blank CRFs, annotated CRFs and study workflow) can now be generated as expected in Viedoc Designer on the European training and production server.

3. postmortem Feb 02, 2025, 07:31 PM UTC

   **Description** Reports on failed pdf generation in Viedoc Designer on the EU Production and Training instance. **Instances affected** Viedoc 4 Production and Training Instance, Europe. **Duration** 2025-01-24 17:34 UTC to 2025-01-25 **Cause** 2025-01-24 17:34 UTC – Pdf documents \(blank CRF, annotated CRF and study workflow\) could not be printed in Viedoc Designer on the EU Training and Production instance. Documents were stuck in 0% progress without further feedback to the user. Analysis showed that documents were processed, although a high peak of print jobs resulted in a queue. During the night between 2025-01-24 and 2025-01-25 the queue had been processed and documents were again printed as expected **Impact** Documents were printed from Viedoc Designer on the EU Production and Training server with a delay during this time period. All print jobs started were completed. **Corrective action** None **Preventive action** TBD

Read the full incident report →

Started Jan 16, 2025, 11:52 AM UTC· resolved Jan 16, 2025, 11:59 AM UTC

1. investigating Jan 16, 2025, 11:52 AM UTC

   Operational disturbance observed in the Viedoc application on the European instance (v4.viedoc.net). Users are currently unable to access the login page and a "runtime error" is displayed to the user. Investigations are ongoing.

2. investigating Jan 16, 2025, 11:56 AM UTC

   We are continuing to investigate this issue.

3. resolved Jan 16, 2025, 11:59 AM UTC

   The incident has been resolved since 11.57 UTC. Users can since then launch Viedoc as expected again.

4. postmortem Jan 23, 2025, 11:42 AM UTC

   **Description** STS failure, impacting user login services. **Instances affected** Viedoc 4 Production Instance, Europe. **Duration** 2025-01-16 11:46 UTC to 2025-01-16 11:57 UTC. **Cause** 2025-01-16 11.46 UTC – Alerts were received from the automated platform monitoring, saying that the STS \(security token service\), managing authentication of users, unexpectedly stopped due to exceeding its operating capacity. **Impact** The issue led to Viedoc users on the European production instance being unable to access the login page and login to the system. There was no impact to other instances. **Corrective action** The STS was restarted and at 2025-01-16 11.57 UTC the users could access the European production instance as expected again. **Preventive action** Investigation is ongoing to determine the cause of the exception and how to prevent this from happening in the future.

Read the full incident report →