All Systems Operational
Viedoc 4 - Japan Operational
90 days ago
100.0 % uptime
Today
Main portal (clinic/admin/designer) Operational
90 days ago
100.0 % uptime
Today
Subject portal (ViedocMe) Operational
90 days ago
100.0 % uptime
Today
Application programming interface (API) Operational
90 days ago
100.0 % uptime
Today
Background processes (import/export/revisions/alerts/archive/disposal) Operational
90 days ago
100.0 % uptime
Today
Viedoc 4 - Europe Operational
90 days ago
99.88 % uptime
Today
Main portal (clinic/admin/designer) Operational
90 days ago
100.0 % uptime
Today
Subject portal (ViedocMe) Operational
90 days ago
100.0 % uptime
Today
Application programming interface (API) Operational
90 days ago
100.0 % uptime
Today
Background processes (import/export/revisions/alerts/archive/disposal) Operational
90 days ago
99.52 % uptime
Today
Viedoc 4 - China Operational
90 days ago
100.0 % uptime
Today
Main portal (clinic/admin/designer) Operational
90 days ago
100.0 % uptime
Today
Subject portal (ViedocMe) Operational
90 days ago
100.0 % uptime
Today
Application programming interface (API) Operational
90 days ago
100.0 % uptime
Today
Background processes (import/export/revisions/alerts/archive/disposal) Operational
90 days ago
100.0 % uptime
Today
Viedoc 3 - Japan Operational
90 days ago
99.94 % uptime
Today
Viedoc 3 - Europe Operational
90 days ago
99.94 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Feb 26, 2021
Resolved - Incident resolved.

Microsoft: "Preliminary Root Cause: During the window of impact, an increase in utilisation was observed and this combined with the sudden loss of backend instance meant an operational threshold was reached. This in turn caused failures for customers and Azure services attempting to utilise Storage resources."

Microsoft Tracking ID: PLWV-BT0
Feb 26, 10:23 UTC
Update - Microsoft has identified the underlying cause and are actively pursuing multiple mitigation workstreams and recovery is currently in progress.

We continue to monitor the Viedoc services, which are all as of now Operational.
Feb 26, 07:28 UTC
Monitoring - The issue has been resolved, monitoring and waiting on confirmation from Microsoft.
Feb 26, 07:06 UTC
Identified - An issue with Azure storage accessibility in Japan East has been identified at our service provider, Microsoft Azure. Microsoft is currently investigating the issue. https://status.azure.com/en-us/status

The issue impact Viedoc functionality such as export, file upload and PDF generation.

Updated 05:57 UTC

Microsoft has identified a possible root cause and are actively determining mitigation steps.

Updated 06:19 UTC
Feb 26, 05:25 UTC
Investigating - We are currently investigating this issue.
Feb 26, 04:01 UTC
Feb 25, 2021

No incidents reported.

Feb 24, 2021

No incidents reported.

Feb 23, 2021

No incidents reported.

Feb 22, 2021

No incidents reported.

Feb 21, 2021

No incidents reported.

Feb 20, 2021

No incidents reported.

Feb 19, 2021
Postmortem - Read details
Feb 22, 07:57 UTC
Resolved - This incident has been resolved.
Feb 19, 08:28 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 19, 08:14 UTC
Update - We are continuing to investigate this issue.
Feb 19, 06:44 UTC
Investigating - We are currently investigating this issue.
Feb 19, 06:25 UTC
Feb 18, 2021

No incidents reported.

Feb 17, 2021

No incidents reported.

Feb 16, 2021

No incidents reported.

Feb 15, 2021

No incidents reported.

Feb 14, 2021

No incidents reported.

Feb 13, 2021

No incidents reported.

Feb 12, 2021

No incidents reported.