Company Logo

Is there an Virtuoso outage?

Virtuoso status: Systems Active

Last checked: 2 minutes ago

Get notified about any outages, downtime or incidents for Virtuoso and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Virtuoso outages and incidents

Outage and incident data over the last 30 days for Virtuoso.

There have been 1 outages or incidents for Virtuoso in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Virtuoso

Outlogger tracks the status of these components for Xero:

Application & API Active
Bridge Active
Cross browser and real device testing Active
Integrations Active
Jobs and bot cluster Active
Component Status
Application & API Active
Bridge Active
Cross browser and real device testing Active
Integrations Active
Jobs and bot cluster Active

Latest Virtuoso outages and incidents.

View the latest incidents for Virtuoso and check for official updates:

Updates:

  • Time: July 17, 2024, 9:41 a.m.
    Status: Postmortem
    Update: On Tuesday 16 July around 06:40 UTC, during a regular update of the platform on all environments we had a severe service degradation on the EU production environment. Usually this would trigger an automatic rollback of the update, but in this specific circumstance only a few of the services were able to return to the previous version, requiring manual intervention to restore full service availability. Alarms in place immediately warned the team that something unexpected occurred and some services were not being able to initialize the new versions. After analyzing the data available and impact of potential decisions, at 07:20 UTC the team triggered a manual downgrade of the service back to the previously known working version, restoring full availability at 08:10 UTC. We are sorry for the inconvenience caused to our customers affected by this outage. This falls below the standard of operational excellence that we wish to provide to our users. We have implemented and released a product change that hardened the automated capabilities of the platform to recover in the scenario described.
  • Time: July 16, 2024, 9:05 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: July 16, 2024, 7:51 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: July 16, 2024, 7:42 a.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: July 16, 2024, 7:01 a.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: May 24, 2024, 12:49 p.m.
    Status: Postmortem
    Update: On Wednesday 15 May at 14:31 in the production environment the Flow integration was deleted in error by an internal team member with elevated privileges. This caused the integration to be removed from all instances, meaning users could not see Flows and jobs did not trigger. At 16:31 the integration was made available again, but this new instance did not contain existing Flows. The team then worked to restore the configurations from a backup. At 19:10 this was completed and configurations were restored for most affected users. Further to this, a small number of customers had some configurations that were later restored following further review on Friday 24 May at 13:45. We are sorry for the inconvenience caused to our customers affected by this outage. This falls below the standard of operational excellence that we wish to provide to our users. We have implemented and released a product change that removes the ability to completely delete integrations when they are installed in organizations.
  • Time: May 16, 2024, 2:05 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: May 16, 2024, 2:04 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: May 15, 2024, 6:07 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: May 15, 2024, 3:31 p.m.
    Status: Identified
    Update: Flow is now available again in production, however we are working to restore existing configurations. We will continue to provide updates as this process progresses.
  • Time: May 15, 2024, 1:54 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: May 24, 2024, 12:49 p.m.
    Status: Postmortem
    Update: On Wednesday 15 May at 14:31 in the production environment the Flow integration was deleted in error by an internal team member with elevated privileges. This caused the integration to be removed from all instances, meaning users could not see Flows and jobs did not trigger. At 16:31 the integration was made available again, but this new instance did not contain existing Flows. The team then worked to restore the configurations from a backup. At 19:10 this was completed and configurations were restored for most affected users. Further to this, a small number of customers had some configurations that were later restored following further review on Friday 24 May at 13:45. We are sorry for the inconvenience caused to our customers affected by this outage. This falls below the standard of operational excellence that we wish to provide to our users. We have implemented and released a product change that removes the ability to completely delete integrations when they are installed in organizations.
  • Time: May 16, 2024, 2:05 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: May 16, 2024, 2:04 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: May 15, 2024, 6:07 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: May 15, 2024, 3:31 p.m.
    Status: Identified
    Update: Flow is now available again in production, however we are working to restore existing configurations. We will continue to provide updates as this process progresses.
  • Time: May 15, 2024, 1:54 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: March 4, 2024, 7:05 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 4, 2024, 7:05 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 4, 2024, 7:02 p.m.
    Status: Monitoring
    Update: A fix has been deployed and results are being computed for jobs run during the period of degraded performance. The delay will persist until the cluster has cleared the backlog of results to post-process.
  • Time: March 4, 2024, 7:02 p.m.
    Status: Monitoring
    Update: A fix has been deployed and results are being computed for jobs run during the period of degraded performance. The delay will persist until the cluster has cleared the backlog of results to post-process.
  • Time: March 4, 2024, 6:58 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: March 4, 2024, 6:58 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: March 4, 2024, 5:36 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.
  • Time: March 4, 2024, 5:36 p.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: Dec. 15, 2023, 2:37 p.m.
    Status: Resolved
    Update: Executions are now continuing as normal.
  • Time: Dec. 15, 2023, 2:33 p.m.
    Status: Monitoring
    Update: The fix has reached our production environments and we are continuing to monitor the situation. Executions are now starting to run.
  • Time: Dec. 15, 2023, 2:12 p.m.
    Status: Identified
    Update: We have identified the root cause of the issue and are working to implement a fix.
  • Time: Dec. 15, 2023, 2:03 p.m.
    Status: Investigating
    Update: We are observing a reduced launch rate for jobs on the Virtuoso cluster. We are investigating the issue and will provide an update when we have identified the cause.

Check the status of similar companies and alternatives to Virtuoso

Avalara
Avalara

Systems Active

Crisis Text Line
Crisis Text Line

Systems Active

Jamf
Jamf

Systems Active

Mulesoft
Mulesoft

Systems Active

Meltwater
Meltwater

Systems Active

HashiCorp
HashiCorp

Systems Active

Datto
Datto

Issues Detected

Vox Media
Vox Media

Systems Active

Cradlepoint
Cradlepoint

Systems Active

Liferay
Liferay

Systems Active

Zapier
Zapier

Systems Active

Workato US
Workato US

Systems Active

Frequently Asked Questions - Virtuoso

Is there a Virtuoso outage?
The current status of Virtuoso is: Systems Active
Where can I find the official status page of Virtuoso?
The official status page for Virtuoso is here
How can I get notified if Virtuoso is down or experiencing an outage?
To get notified of any status changes to Virtuoso, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Virtuoso every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Virtuoso do?
Virtuoso is a QA automation testing tool that combines Natural Language Programming and Robotic Process Automation for faster deployment and self-healing capabilities.