Is there an Virtuoso outage?
Virtuoso status: Systems Active
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for Virtuoso and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for Virtuoso and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Virtuoso.
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 NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Application & API | Active |
| Bridge | Active |
| Cross browser and real device testing | Active |
| Integrations | Active |
| Jobs and bot cluster | Active |
View the latest incidents for Virtuoso and check for official updates:
Description: At around 16:41PM we started receiving error alerts indicating that screenshots and other captured data \(downloaded files, network logs\) could not be saved to our object storage backend. At around 17:11 we identified the cause and rolled out a fix by 17:18. While screenshots were not stored for some steps for jobs running within this period, other execution results were still collected, and executions continued uninterrupted. We recently changed the authentication mechanism that our execution backend uses to upload screenshots and other information during execution. The team released the latest platform to production today which included this change. However, our release automation did not make the necessary infrastructure changes at the same time which led to the failed authentication events.
Status: Postmortem
Impact: Minor | Started At: Feb. 6, 2023, 4:41 p.m.
Description: Our team was alerted to the unavailability of the bridge service for a large number of our customers. Upon this discovery, our team immediately started investigating the problem and identified the problem to be due to the discovery of some of our bridge services. Prior to this, our team had made a number of improvements and refactoring that involved changing part of the discovery logic, which inadvertently caused a number of older bridge servers not to be discovered by our bot, and as a result, led to execution failures. Although we do have extensive tests for both our bridge service and the discovery logic \(e.g., including even full end-to-end validation of creating and using a bridge\), this issue escaped our testing as it impacted only a subset of the services to be discovered. As part of this, upon discovery of the root cause, we immediately shipped a fix to the logic that resolves this discovery. We would like to apologize for any trouble this caused for the subset of customers using our bridge service, and we are putting mitigations in place to ensure this issue would not occur again.
Status: Postmortem
Impact: Critical | Started At: Jan. 24, 2023, 3 p.m.
Description: Our team was alerted to the unavailability of the bridge service for a large number of our customers. Upon this discovery, our team immediately started investigating the problem and identified the problem to be due to the discovery of some of our bridge services. Prior to this, our team had made a number of improvements and refactoring that involved changing part of the discovery logic, which inadvertently caused a number of older bridge servers not to be discovered by our bot, and as a result, led to execution failures. Although we do have extensive tests for both our bridge service and the discovery logic \(e.g., including even full end-to-end validation of creating and using a bridge\), this issue escaped our testing as it impacted only a subset of the services to be discovered. As part of this, upon discovery of the root cause, we immediately shipped a fix to the logic that resolves this discovery. We would like to apologize for any trouble this caused for the subset of customers using our bridge service, and we are putting mitigations in place to ensure this issue would not occur again.
Status: Postmortem
Impact: Critical | Started At: Jan. 24, 2023, 3 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Oct. 20, 2022, 12:15 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Oct. 20, 2022, 12:15 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
