- Detected by Pingoru
- May 18, 2026, 09:55 AM UTC
- Resolved
- May 18, 2026, 10:32 AM UTC
- Duration
- 36m
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)Application programming interface (API)Background processes (import/export/revisions/alerts/archive/disposal)Reporting tool (ViedocReports)Document management (ViedocTMF)
Timeline · 3 updates
-
investigating May 18, 2026, 10:24 AM UTC
Operational disturbance observed in Training on the Chinese instance (clinic.viedoc.cn). Investigations are ongoing.
-
investigating May 18, 2026, 10:26 AM UTC
We are continuing to investigate this issue.
-
resolved May 18, 2026, 10:32 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 09:48 AM UTC
- Resolved
- May 11, 2026, 09:54 AM UTC
- Duration
- 5d
Affected: Main portal (clinic/admin/designer)Main portal (clinic/admin/designer)
Timeline · 4 updates
-
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.
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Apr 27, 2026, 11:00 AM UTC
- Resolved
- Apr 27, 2026, 07:00 PM UTC
- Duration
- 7h 59m
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)Application programming interface (API)Background processes (import/export/revisions/alerts/archive/disposal)Reporting tool (ViedocReports)Document management (ViedocTMF)
Timeline · 4 updates
-
investigating Apr 27, 2026, 01:04 PM UTC
Operational disturbance observed in Viedoc 4 on the European instance (v4.viedoc.net). Investigations are ongoing.
-
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.
-
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.
-
resolved Apr 27, 2026, 07:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 09, 2025, 09:37 AM UTC
- Resolved
- Dec 09, 2025, 12:20 PM UTC
- Duration
- 2h 43m
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Dec 05, 2025, 12:25 PM UTC
- Resolved
- Dec 16, 2025, 03:18 PM UTC
- Duration
- 11d 2h
Affected: Main portal (clinic/admin/designer)Main portal (clinic/admin/designer)Main portal (clinic/admin/designer)Main portal (clinic/admin/designer)
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Dec 01, 2025, 01:10 PM UTC
- Resolved
- Dec 02, 2025, 08:21 AM UTC
- Duration
- 19h 10m
Affected: Background processes (import/export/revisions/alerts/archive/disposal)Background processes (import/export/revisions/alerts/archive/disposal)
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Nov 25, 2025, 01:31 PM UTC
- Resolved
- Nov 26, 2025, 09:08 AM UTC
- Duration
- 19h 36m
Affected: Background processes (import/export/revisions/alerts/archive/disposal)
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Nov 11, 2025, 11:55 AM UTC
- Resolved
- Nov 11, 2025, 11:55 AM UTC
- Duration
- —
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)Application programming interface (API)Background processes (import/export/revisions/alerts/archive/disposal)Reporting tool (ViedocReports)Document management (ViedocTMF)
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Nov 03, 2025, 01:27 PM UTC
- Resolved
- Nov 02, 2025, 10:30 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2025, 01:56 PM UTC
- Resolved
- Sep 03, 2025, 02:27 PM UTC
- Duration
- 1d
Affected: Main portal (clinic/admin/designer)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2025, 11:29 AM UTC
- Resolved
- Aug 28, 2025, 01:11 PM UTC
- Duration
- 3d 1h
Affected: Reporting tool (ViedocReports)Reporting tool (ViedocReports)Reporting tool (ViedocReports)Reporting tool (ViedocReports)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Aug 19, 2025, 05:38 PM UTC
- Resolved
- Aug 19, 2025, 06:32 PM UTC
- Duration
- 54m
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)Application programming interface (API)Background processes (import/export/revisions/alerts/archive/disposal)Reporting tool (ViedocReports)Document management (ViedocTMF)
Timeline · 3 updates
-
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.
-
monitoring Aug 19, 2025, 06:07 PM UTC
Access to Chinese instance is stable again. Continue monitoring status.
-
resolved Aug 19, 2025, 06:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2025, 03:17 PM UTC
- Resolved
- Jul 25, 2025, 01:32 PM UTC
- Duration
- 1d 22h
Affected: Document management (ViedocTMF)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jul 14, 2025, 02:00 AM UTC
- Resolved
- Jul 14, 2025, 02:00 AM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Mar 26, 2025, 09:12 PM UTC
- Resolved
- Mar 26, 2025, 10:59 PM UTC
- Duration
- 1h 46m
Affected: Document management (ViedocTMF)
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jan 24, 2025, 08:20 PM UTC
- Resolved
- Jan 26, 2025, 08:47 PM UTC
- Duration
- 2d
Affected: Background processes (import/export/revisions/alerts/archive/disposal)
Timeline · 3 updates
-
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.
-
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.
-
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 →
Critical January 16, 2025 - Detected by Pingoru
- Jan 16, 2025, 11:52 AM UTC
- Resolved
- Jan 16, 2025, 11:59 AM UTC
- Duration
- 6m
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)Application programming interface (API)Background processes (import/export/revisions/alerts/archive/disposal)Reporting tool (ViedocReports)Document management (ViedocTMF)
Timeline · 4 updates
-
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.
-
investigating Jan 16, 2025, 11:56 AM UTC
We are continuing to investigate this issue.
-
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.
-
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 →
- Detected by Pingoru
- Oct 22, 2024, 08:21 PM UTC
- Resolved
- Oct 22, 2024, 04:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 22, 2024, 08:21 PM UTC
Intermittent issues with logging in to the US production and US training instance between 6:29 - 7:07PM CET on 2024-10-22. The incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 10, 2024, 06:15 PM UTC
- Resolved
- Oct 17, 2024, 01:40 PM UTC
- Duration
- 6d 19h
Affected: Background processes (import/export/revisions/alerts/archive/disposal)Background processes (import/export/revisions/alerts/archive/disposal)
Timeline · 3 updates
-
investigating Oct 10, 2024, 06:15 PM UTC
Imports of large data files submitted through the WCF API on the EU and US instance are currently failing. Investigation is ongoing and status updates will be provided here. For urgent imports, please contact the support or your product specialist for advice.
-
resolved Oct 17, 2024, 01:40 PM UTC
The issue has now been resolved. Imports of large data files submitted through the WCF API on the EU and US instances are now working as expected again. This issue was resolved on the EU instance on 2024-10-16 and on the US instance on 2024-10-17.
-
postmortem Oct 23, 2024, 06:41 AM UTC
**Description** After release of Viedoc 4.80, the WCF API did not accept requests with a large amount of data. This was for example causing the import of clinical data through the WCF API to fail. **Cause** When migrating the WCF service to dot NET core, the maximum size of message accepted was set to default \(65535 bytes\) in the framework. **Corrective action** Updated the code to change the message size to a configurable value. And changed the configurable value to accommodate large messages. **Preventive action** The message size is set to max value that can be handled by system.
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2024, 10:04 AM UTC
- Resolved
- Aug 21, 2024, 12:05 PM UTC
- Duration
- 2h
Affected: Background processes (import/export/revisions/alerts/archive/disposal)
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2024, 09:26 PM UTC
- Resolved
- Aug 18, 2024, 09:26 PM UTC
- Duration
- —
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)Application programming interface (API)Background processes (import/export/revisions/alerts/archive/disposal)Reporting tool (ViedocReports)Document management (ViedocTMF)
Timeline · 1 update
-
resolved Aug 18, 2024, 09:26 PM UTC
Updated release schedule for Viedoc 4.79. The release is planned for the following dates on the CN instance: 2024-09-03 (all applications except Viedoc TMF) 2024-09-04 (Viedoc TMF)
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2024, 09:23 PM UTC
- Resolved
- Aug 18, 2024, 09:23 PM UTC
- Duration
- —
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)Application programming interface (API)Background processes (import/export/revisions/alerts/archive/disposal)Reporting tool (ViedocReports)Document management (ViedocTMF)
Timeline · 1 update
-
resolved Aug 18, 2024, 09:23 PM UTC
Updated release schedule for Viedoc 4.79. The release is planned for the following dates on the JP instance: 2024-08-27 (all applications except Viedoc TMF) 2024-08-28 (Viedoc TMF)
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2024, 02:18 PM UTC
- Resolved
- Jul 31, 2024, 07:43 AM UTC
- Duration
- 17h 25m
Timeline · 3 updates
-
monitoring Jul 30, 2024, 02:18 PM UTC
The incident was resolved by infrastructure provider Microsoft Azure.
-
resolved Jul 31, 2024, 07:43 AM UTC
This incident has been resolved.
-
postmortem Aug 08, 2024, 07:38 AM UTC
# Viedoc service issue report **Report author** Ted Lähteenmäki, Manager IT Operations Viedoc Technologies AB Email: [[email protected]](mailto:[email protected]) **Report issued** 2024-07-30 **Description**` ` Disturbance in IdP impacting user login services. **Instances affected** Viedoc 4 – Europe. **Duration** 2024-07-30 13:30 UTC to 2024-07-30 13:35 UTC. **Cause** The infrastructure provider \(Microsoft Azure\) experienced a service issue which impacted our IdP login services. **Impact** Upon attempting to log in to Viedoc, a “Maintenance mode” message appeared during the times specified above. Data integrity and confidentiality were not affected. **Corrective action** This issue was resolved automatically as when the infrastructure provider services were restored. **Preventive action** Pending the Root Cause Analysis report from the infrastructure provider.
Read the full incident report →
- Detected by Pingoru
- Jul 18, 2024, 11:09 PM UTC
- Resolved
- Jul 19, 2024, 06:17 AM UTC
- Duration
- 7h 7m
Timeline · 3 updates
-
investigating Jul 18, 2024, 11:09 PM UTC
We are currently investigating an operational disturbance.
-
identified Jul 19, 2024, 01:44 AM UTC
We have identified that our provider Microsoft Azure is experiencing a disturbance with their service.
-
resolved Jul 19, 2024, 06:17 AM UTC
Incident have been resolved by infrastructure provider Microsoft Azure, meaning that the US instance of Viedoc is now operating as expected again.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2024, 08:04 PM UTC
- Resolved
- Jul 15, 2024, 09:26 PM UTC
- Duration
- 1h 22m
Affected: Main portal (clinic/admin/designer)Subject portal (ViedocMe)
Timeline · 2 updates
-
investigating Jul 15, 2024, 08:04 PM UTC
There are currently disturbances with text messages sent to US phone numbers from the Viedoc EU instance. This is affecting 2FA text messages and Viedoc Me reminders sent via SMS. Numbers from other regions are not affected.
-
resolved Jul 15, 2024, 09:26 PM UTC
This incident has been resolved.
Read the full incident report →
