Update - We have narrowed the scope of this issue. Impact is limited to customers with the "Studios - Partial Configuration Management (Beta)" feature enabled. Our team is currently determining the next steps for a fix.
Feb 13, 2026 - 02:42 UTC
Identified - We have identified the cause of the loading issues on the Change Control page and are currently evaluating the full extent of the impact.
Feb 13, 2026 - 01:47 UTC
Investigating - We are investigating an issue with the Change Control page where configuration diffs are failing to load. We are working to identify the root cause.
Feb 13, 2026 - 01:30 UTC
We have not removed 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. Posted on
Jan 08, 2026 - 01:03 UTC
CloudVision as-a-Service will no longer officially support devices running EOS 4.26 or 4.27 trains starting April 20th, 2026. This is in line with our CloudVision Lifecycle Policy (https://www.arista.com/en/support/product-documentation/cloudvision-life-cycle-policy/eos-support). 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. Posted on
Jan 14, 2026 - 02:13 UTC
Past Incidents
Feb 13, 2026
Unresolved incident: Device configuration diff is not loading on Change Control page.
Resolved -
This incident has been resolved.
Jan 31, 01:42 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jan 31, 01:33 UTC
Update -
Data ingestion into the platform remains uninterrupted, but UI interactions and usage are currently being disrupted.
Jan 31, 01:04 UTC
Update -
The disruption is continuing. This is due to disruptions with our underlying provider, and we are working on restoring the service ASAP. Thank you for your patience.
Jan 31, 01:01 UTC
Identified -
We are investigating a platform degradation in the US region.
Jan 31, 00:16 UTC