Arista CloudVision Outage History

Started Oct 12, 2025, 11:05 AM UTC· resolved Oct 12, 2025, 02:15 PM UTC

1. investigating Oct 12, 2025, 11:05 AM UTC

   We are currently investing an issue affecting the platform.

2. identified Oct 12, 2025, 11:21 AM UTC

   The issue has been identified and a fix is being implemented.

3. identified Oct 12, 2025, 12:11 PM UTC

   We are continuing to work on a fix for the issue.

4. identified Oct 12, 2025, 12:45 PM UTC

   We have recovered the service and our system is currently processing the last 2 hours of telemetry data. The service is currently experiencing degraded performance.

5. monitoring Oct 12, 2025, 01:14 PM UTC

   The processing of the telemetry data backlog is progressing well. We estimate that the system will have full catch up in about 1h.

6. resolved Oct 12, 2025, 02:15 PM UTC

   The data processing pipeline has fully recovered, and the service is now operating in a healthy state. The ingestion of device telemetry data was not impacted during the incident. There was no data loss. Postmortem for this incident is still pending. Our team is currently actively working on reviewing this incident, and postmortem update.

Read the full incident report →

Started Sep 08, 2025, 12:56 PM UTC· resolved Sep 08, 2025, 03:35 PM UTC

1. investigating Sep 08, 2025, 12:56 PM UTC

   We are currently investing alerts about connection failure affecting all service regions.

2. identified Sep 08, 2025, 01:18 PM UTC

   We have identified the root cause of the issue. The team is working on a fix.

3. identified Sep 08, 2025, 02:01 PM UTC

   A fix is rolling out on all service regions.

4. monitoring Sep 08, 2025, 02:15 PM UTC

   Services is coming back up, but with degraded performance. We are monitoring the situation.

5. monitoring Sep 08, 2025, 02:22 PM UTC

   uk-1, india-1 and na-northeast1-b regions are fully operational.

6. monitoring Sep 08, 2025, 02:26 PM UTC

   euwest-2 region is fully operational.

7. monitoring Sep 08, 2025, 02:42 PM UTC

   ausoutheast-1 and apnortheast-1 regions are fully operational.

8. monitoring Sep 08, 2025, 02:56 PM UTC

   us-central1-b region is fully operational.

9. monitoring Sep 08, 2025, 03:07 PM UTC

   us-central1-a region is fully operational.

10. monitoring Sep 08, 2025, 03:31 PM UTC

    us-central1-c region is fully operational.

11. resolved Sep 08, 2025, 03:35 PM UTC

    This incident is now fully resolved. Postmortem for this incident is still pending. Our team is currently actively working on reviewing this incident, and postmortem update.

12. postmortem Sep 16, 2025, 05:54 PM UTC

    **Incident Report: CVaaS Service Disruption - September 8, 2025** On September 8, 2025, CloudVision as-a-Service experienced a service disruption, lasting from 8 minutes in our UK region \(cv-prod-uk-1\) to 25 minutes in a US region \(us-central1-a\). During this time, users were unable to establish new connections, and transient connection errors occurred for those with existing connections. We do not expect any data loss, as device state streaming was coalesced and resumed after the disruption. This incident was not caused by a security breach, intrusion, or other malicious activity. ‌ **Root Cause** An internal certificate expired within our trust chain, causing a disruption. The certificate was not properly monitored in our system, which notifies and automatically renews certificates, leading to its expiration. ‌ **Our Response** Our team was alerted to similar service disruptions across various global regions, and a status page incident was posted because the issue was not transient and was unrelated to our service provider. The disruption was triaged, the root cause identified, and mitigations implemented within 20 minutes. Corrective actions were taken simultaneously over the next approximately 35 minutes. The incident was closed after an assessment of all regions was completed, and services were restored. We understand that an outage of this nature is unacceptable and apologize to all affected CloudVision as-a-Service users impacted by this incident. We are committed to implementing changes identified during our internal investigation to prevent this type of failure from happening again. Thank you for using CloudVision as-a-Service.

Read the full incident report →

Started Sep 02, 2025, 03:38 AM UTC· resolved Sep 02, 2025, 05:38 AM UTC

1. identified Sep 02, 2025, 03:38 AM UTC

   We've identified issue that is affecting devices streaming state and updates from being properly updated. We are working on resolving this issue. There is currently no ETA.

2. identified Sep 02, 2025, 04:33 AM UTC

   We are continuing to work on resolving this issue.

3. monitoring Sep 02, 2025, 05:07 AM UTC

   We have identified, recovered from the main issue and now monitoring.

4. monitoring Sep 02, 2025, 05:37 AM UTC

   During the one-hour impact window, addition of new devices and modifications to the existing device inventory were both delayed. Postmortem for this incident is still pending. Our team is currently actively working on reviewing this incident, and postmortem update.

5. resolved Sep 02, 2025, 05:38 AM UTC

   This incident has been resolved.

6. postmortem Sep 09, 2025, 12:40 AM UTC

   ## **Incident Report: CVaaS Service Disruption - September 1, 2025** On September 1, 2025, CloudVision as-a-Service region cv-prod-euwest-2 experienced a disruption that lasted 2h. During this time some devices may have experienced state update becoming visible to be delayed up to those 2h. There was no data loss of device state. This incident was not due to a security breach, intrusion, or otherwise malicious activity.‌ **Root Cause** The root cause of this incident was caused by residual impact that was as described [in this incident](https://status.arista.io/incidents/7bcj2khfpqcy). Please find further details of root cause, and our response as described in this linked post. Thank you for using CloudVision as-a-Service.

Read the full incident report →

Started Sep 01, 2025, 05:39 PM UTC· resolved Sep 02, 2025, 05:27 AM UTC

1. investigating Sep 01, 2025, 05:39 PM UTC

   Flow data processing is currently delayed due to an issue with our ingest service. We are actively investigating the issue.

2. identified Sep 01, 2025, 10:22 PM UTC

   We have identified the core issue affecting ingest of flow updates. Unfortunately at this time we have a significant delay in accepting flow updates.

3. identified Sep 01, 2025, 10:57 PM UTC

   We are continuing to resolve this issue.

4. identified Sep 02, 2025, 12:03 AM UTC

   We are continuing to work on resolving this issue.

5. identified Sep 02, 2025, 01:09 AM UTC

   We are continuing to work on resolving this issue.

6. identified Sep 02, 2025, 02:05 AM UTC

   We are continuing to work on resolving this issue.

7. identified Sep 02, 2025, 03:28 AM UTC

   We are continuing to work on resolving this issue.

8. identified Sep 02, 2025, 04:33 AM UTC

   We are continuing to work on resolving this issue.

9. identified Sep 02, 2025, 04:33 AM UTC

   We are continuing to work on a fix for this issue.

10. monitoring Sep 02, 2025, 05:06 AM UTC

    We have identified, recovered from the main issue and now monitoring. All flow ingest should resume processing again.

11. resolved Sep 02, 2025, 05:27 AM UTC

    Ingestion of flow data into cv-prod-euwest-2 was unavailable for approximately 12 hours. Consequently, no flow data was ingested or is currently visible for your devices during this period. Postmortem for this incident is still pending. Our team is currently actively working on reviewing this incident, and postmortem update.

12. postmortem Sep 02, 2025, 06:27 PM UTC

    ## **Incident Report: CVaaS Service Disruption - September 1, 2025** On September 1, 2025, CloudVision as-a-Service region cv-prod-euwest-2 experienced a disruption that lasted 11 hours and 48 minutes. During this time, the service was unable to ingest flow data successfully. As a result, a gap in data might be seen when viewing traffic flow dashboards, flows in Topology views, event-specific details related to traffic flows, or UNO-related product reporting during this period. This incident was not due to a security breach, intrusion, or otherwise malicious activity. **Root cause** This outage was caused by a subset of our data becoming unreadable. The particular corner case was a result of a race condition found in a specific part of the system that controls data lifecycle and enforces access control through checking permissions. Successful authz is required for any CRUD operations on any part of our data to be successful. When we reach an inconsistent state as such, our system’s default behavior is to fail close. This design, while protective, led to this incident where we could not successfully ingest and write flow data, and the system remained secure by design. **Our Response** Our team worked non-stop to resolve the issue. The extended duration of the outage was due to an initial misdiagnosis of the root cause. Once the correct cause was identified, our team was able to resolve the issue and restore full functionality within approximately 30 minutes. We understand this broad outage and the impact on your experience is unacceptable. We sincerely apologize to all affected CloudVision as-a-Service users in the affected region. We are committed to implementing changes identified during our internal investigation to prevent this type of failure from happening again. Thank you for using CloudVision as-a-Service.

Read the full incident report →

Started Sep 01, 2025, 02:09 PM UTC· resolved Sep 01, 2025, 02:26 PM UTC

1. identified Sep 01, 2025, 02:09 PM UTC

   We are aware of an issue with applying image bundles via the "Image Repository" page. We have identified the cause, and are applying a mitigation. There may be a short period of disruption for any provisioning related activities during this time.

2. resolved Sep 01, 2025, 02:26 PM UTC

   The fix has been deployed and this incident has been resolved.

Read the full incident report →

Started Aug 26, 2025, 08:59 PM UTC· resolved Aug 26, 2025, 11:14 PM UTC

1. investigating Aug 26, 2025, 08:59 PM UTC

   We are investigating issues around building workspaces that are affecting some customers. We are working on a mitigation.

2. monitoring Aug 26, 2025, 10:12 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 26, 2025, 11:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 13, 2025, 03:27 PM UTC· resolved Aug 13, 2025, 03:37 PM UTC

1. resolved Aug 13, 2025, 03:27 PM UTC

   This is a retroactive post for the event that occurred earlier today on us1b on August 13th, 8:30 UTC that lasted about 10 minutes. Some impact may have been user visible, such as: - Some events, such as "Device stopped streaming" or "Streaming Latency Breached Threshold" may have fired incorrectly during this period. - There may have been sporadic timeouts when viewing parts of the UI. - There may have been general slowdown of provisioning activities, potentially resulting in timeouts or errors.

Read the full incident report →

Started Jun 16, 2025, 04:59 PM UTC· resolved Jun 16, 2025, 04:59 PM UTC

1. resolved Jun 16, 2025, 05:03 PM UTC

   CloudVision as-a-Service will no longer officially support devices running EOS 4.23, 4.24, or 4.25 trains starting January 1st, 2026. This is in line with our CloudVision Lifecycle Policy (https://www.arista.com/en/support/product-documentation/cloudvision-life-cycle-policy). We won't remove existing support, but new CloudVision releases won't be tested with these older EOS trains. While most CloudVision features will likely continue to function, any support for these older trains will be on a best-effort basis. We strongly recommend upgrading your EOS devices via CloudVision to a supported release.

Read the full incident report →