CVaaS Status Page

Jul 10, 2026 · resolved Jul 10

This incident has been resolved.

Jul 7, 2026

Hello CVaaS Users, This is a courtesy notice to keep our users on service region cv-prod-us-central1-b informed. Our team continues to monitor as follow up to mitigations for the incident on June 26th (https://status.arista.io/incidents/5vx7cvb07k7d). At present, cv-prod-us-central1-b service region is fully operational. We expect users to be able to continue using Provisioning and Telemetry features as normal. No other service regions are impacted by this incident. Thank you for using CVaaS.

Jun 26, 2026 · resolved Jul 7

Hello CVaaS Users, This incident is closed as the original high impact on June 26th, 2026 where cv-prod-us-central1-b service region experienced a period of high ingestion latency that may have caused devices incorrectly being marked as Inactive on CloudVision, or experiencing sustained periods of elevated streaming latency also as reported by CloudVision. This original high impact has been effectively mitigated by June 27th, 2026. Since then our team has been working on fixing brief, intermittent streaming latencies (under 1 minute) that affect a small number of devices. At present, cv-prod-us-central1-b service region is fully operational. We expect users to be able to continue using Provisioning and Telemetry features as normal. No other service regions are impacted by this incident. We will follow up with a postmortem of this incident, especially regarding the impact on June 26th, 2026.

Jun 10, 2026 · resolved Jun 10

We identified the source of the problem and the data ingestion latency has been resolved.

May 29, 2026 · resolved Jun 4

**Incident Report: CVaaS Service Disruption - May 29, 2026** On May 29th, 2026, CloudVision as-a-Service delivered a software change for a set of services that provide the Network Provisioning workflows in the product. All services regions were impacted by this Network Provisioning feature update.  This update introduced a critical bug across all service regions. As a result, customers utilizing the Network Provisioning workflows \(see [https://www.arista.io/help/articles/provisioning-network-provisioning#network-provisioning](https://www.arista.io/help/articles/provisioning-network-provisioning#network-provisioning)\) may have experienced instances where devices were mapped to the incorrect containers in the network provisioning hierarchy, creating a risk that unintended configuration states could be applied if customers then attempted to roll out additional changes to devices. The Network Provisioning workflows were disabled while we recovered from the issue, meaning that customers could not make any changes to their network configuration during this time. Customers only defining their network configuration using Studios workflows \(see [https://www.arista.io/help/articles/provisioning-studios](https://www.arista.io/help/articles/provisioning-studios)\) were not impacted. The software change that caused this issue was rolled back on May 29th, 2026. The delay in mitigation was due to gaps in our automated monitoring systems. FAQ: * _Did this bug cause a network outage for customers?_ No. * _Was there any data loss?_ No. * Was overall CloudVision service availability impacted?No. * _Are there any additional steps to recovery?_ No; the vast majority of impacted customers were recovered without requiring customer intervention. At this moment if you have not been directly contacted by us, no further action is required from you. ‌ **Root Cause** The bug was due to logic applied to an incorrect data state within the Network Provisioning feature. This caused an incorrect device container mapping during the device state reconciliation phase. This was not caught during testing or during the post deployment evaluation phase in various environments prior to being released to production. Additionally, the rollout strategy used in the continuous delivery applicable for this particular set of services allowed the bug to propagate quickly across all CloudVision as-a-Service regions. ‌ **Our Response** Once the bug was identified on May 29th, 2026, our team rolled back the update responsible within approximately a five hour period on all production regions. In addition, API usage restrictions were established as a protective measure against customers that may inadvertently execute a configuration change on their network without knowledge of this bug and device state change. Between May 29th and June 1st, 2026, our team engaged in continuous efforts to restore services for all affected customers and devices. The majority of these recovery operations were successfully concluded by May 30th, 2026. Throughout this period, we maintained regular updates on Statuspage to keep our customers informed regarding our progress. We understand a disruption of this nature is unacceptable for our customers. We are conducting a full review of design, testing, validation, delivery, monitoring, and incident response as part of the postmortem review, and we are committed to ensuring we do not run into incidents of this nature in the future.  Thank you for using CloudVision as-a-Service.

Is CVaaS down right now?

No — CVaaS is up. All systems operational as of Jul 13, 11:44 PM UTC.

What is CVaaS's current status?

CVaaS: All Systems Operational. Alert24 checks CVaaS's status page continuously and can notify you the moment it changes.

How do I get alerted when CVaaS goes down?

Alert24 monitors CVaaS and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.