Arista CloudVision Outage History

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

This incident has been resolved.

This incident has been resolved. We will follow up with a postmortem.

We experienced high device streaming latency on this affected cluster. Some impact may be user visible, such as: - A delay in processing streamed device data. Some events such as "Device stopped streaming" or "Streaming Latency Breached Threshold" may fire as a result of this. In this case, the device updates are behind schedule and will be processed with some delay during the impact window. - There may be some stale data, or sporadic timeouts viewing parts of the UI. - Some provisioning features may be delayed or timeout due to the high latency. This was due to an internal component upgrade in our cloud environment; we continue to work on decreasing the impact of this upgrade process. Thank you for your patience.

This incident has been resolved.

The fix has been successfully deployed to all regions. Customers will have to reload the UI for the changes to take effect.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

Telemetry was delayed for up to 30 minutes due to an disruptive infrastructure reconfiguration. The incident has now been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

Closing this courtesy notice.

Hello CloudVision as a Service customers, We have identified an issue impacting a small subset of customers where all EOS devices in a tenant were incorrectly marked as inactive. Importantly, the devices were actively streaming and all data and telemetry were generated and stored correctly. Impacted customers may have observed this incorrect streaming status displayed for several consecutive hours or days since November 25th, 2025. We have identified the root cause and deployed an immediate fix. There is no action required from you as the customer. This is a courtesy notice only. If you have any questions about this issue or if your tenant was affected, please reach out to [email protected]. Thank you for being a valued CloudVision as a Service customer.

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.

This incident has been resolved.

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

This incident has been resolved.

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.