Is Viedoc down?
Last checked 8m agoNo incidents right now.
Viedoc is operational right now. Last checked 8m ago; the most recent incident resolved 3d ago.
Real-time Viedoc status, recent outages, and incident history — pulled directly from Viedoc's official status page at https://status.viedoc.com every 5 minutes. Pingoru tracks 25 Viedoc services and has captured 8 incidents in the last 90 days (98.57% uptime). Get email, Slack, Discord, or webhook alerts the moment Viedoc reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- 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 · Jul 29, 2026, 01:35 PM UTC
We are currently investigating this issue, update coming soon.
- investigating · Jul 29, 2026, 02:11 PM UTC
The issue correlates with a data center decommissioning in China and we are continuing to investigate.
- 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.
- 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.
Latest: ## 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 render…
-
- Subject portal (ViedocMe)Subject portal (ViedocMe)Subject portal (ViedocMe)Subject portal (ViedocMe)
Timeline · 4 updates
- 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.
- 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.
- 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.
- 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.
Latest: 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, Ev…
-
- Main portal (clinic/admin/designer)Main portal (clinic/admin/designer)
Timeline · 4 updates
- 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.
- identified · Jun 10, 2026, 11:31 PM UTC
The issue has been identified and a fix is being implemented.
- 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.
- 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.
Latest: Hotfix 4.95.1 has been released on the EU training and production instances. The incident is now resolved on all instances.
-
- 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 · 2 updates
- monitoring · Jun 03, 2026, 12:12 PM UTC
Temporary operational disturbance observed in the Viedoc suite on the Chinese instance (clinic.viedoc.cn).
- resolved · Jun 03, 2026, 01:23 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- 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 · 2 updates
- 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
- resolved · May 28, 2026, 07:38 AM UTC
The incident has been resolved since 08:40 GMT+2
Latest: The incident has been resolved since 08:40 GMT+2
-
See the full Viedoc outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Viedoc outage history →Or sign up free to get alerts when Viedoc breaks · 10 free monitors · No credit card
- Issues in China region ResolvedStarted Jul 29, 2026, 12:07 PM UTC · Resolved Jul 29, 2026, 05:06 PM UTC · 4h 59m
- Started Jul 09, 2026, 09:40 PM UTC · Resolved Jul 16, 2026, 09:42 AM UTC · 6d 12h
- Batch upgrade after form revision clears data in repeating item groups on EU and US instances ResolvedStarted Jun 10, 2026, 06:32 PM UTC · Resolved Jun 17, 2026, 10:40 AM UTC · 6d 16h
- Started Jun 03, 2026, 12:12 PM UTC · Resolved Jun 03, 2026, 01:23 PM UTC · 1h 11m
- Started May 28, 2026, 05:30 AM UTC · Resolved May 28, 2026, 06:40 AM UTC · 1h 9m
- Started May 18, 2026, 09:55 AM UTC · Resolved May 18, 2026, 10:32 AM UTC · 36m
- Started May 06, 2026, 09:48 AM UTC · Resolved May 11, 2026, 09:54 AM UTC · 5d