Arista Cloudvision status history
Current state: operational — “All Systems Operational” per https://status.arista.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Arista Cloudvision incidents last?
From 44 incidents with a vendor-posted start and resolve time. Longest on record: High Device Streaming Latency experienced on the Platform — 11.2 days (2026-06-26 17:27 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (44)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-09 20:02 UTC | Platform wide Disruption | resolved | major | 8 h 00 min |
| 2026-09-01 03:22 UTC | High Device Streaming Latency experienced on the Platform | resolved | minor | 1 h 25 min |
| 2026-08-28 17:39 UTC | Platform Disruption | resolved | minor | 3 h 00 min |
| 2026-08-20 02:54 UTC | High Device Streaming Latency experienced on the Platform | resolved | minor | 2 h 15 min |
| 2026-08-12 18:51 UTC | Core platfrorm | resolved | minor | 12 min |
| 2026-08-12 16:19 UTC | Device Experiencing Streaming Issues | resolved | minor | 13 h 05 min |
| 2026-08-06 10:45 UTC | High Streaming Latency | resolved | minor | 1 h 02 min |
| 2026-07-15 21:45 UTC | Change Control disruption | resolved | minor | 0 min |
| 2026-07-15 01:09 UTC | Change Control disruption | resolved | major | 2 h 18 min |
| 2026-07-10 18:25 UTC | Temporary Ingestion Lag | resolved | minor | 21 min |
| 2026-07-07 22:58 UTC | [Informational Only] CloudVision may report brief elevated Streaming Latencies for devices for service region cv-prod-us-central1-b | resolved | none | 6 d 0 h |
| 2026-06-26 17:27 UTC | High Device Streaming Latency experienced on the Platform | postmortem | minor | 11 d 5 h |
| 2026-06-10 11:48 UTC | High Streaming Latency | resolved | minor | 4 h 15 min |
| 2026-05-29 20:24 UTC | Network Provisioning - Device is present in an unexpected container | postmortem | major | 5 d 4 h |
| 2026-05-29 17:45 UTC | Network Provisioning/Studios - Incorrect End Configurations Generated | resolved | major | 3 h 16 min |
| 2026-05-26 15:38 UTC | Issues logging into the platform | resolved | major | 9 h 24 min |
| 2026-05-18 13:35 UTC | High Device Streaming Latency experienced on the Platform | resolved | none | 0 min |
| 2026-05-15 17:24 UTC | Partial outage in network provisioning | resolved | major | 5 min |
| 2026-04-15 12:04 UTC | High Device Streaming Latency experienced on the Platform | resolved | minor | 29 min |
| 2026-03-19 00:38 UTC | High Device Streaming Latency experienced on the Platform | resolved | minor | 18 min |
| 2026-03-12 15:33 UTC | Performance Degradation in Provisioning Tasks Window | resolved | minor | 6 h 24 min |
| 2026-03-04 05:23 UTC | Partial Outage of Secured ZTP (sztp) / License management functionality | resolved | minor | 1 h 19 min |
| 2026-03-03 04:15 UTC | Elevated request errors | resolved | minor | 15 min |
| 2026-02-13 01:30 UTC | Device configuration diff is not loading on Change Control page | resolved | none | 4 d 15 h |
| 2026-01-31 00:16 UTC | Platform Disruption | postmortem | major | 1 h 26 min |
| 2026-01-30 14:36 UTC | Outage affecting 'Log in with Email' | postmortem | major | 1 h 28 min |
| 2026-01-23 09:28 UTC | Platform disruption | resolved | minor | 2 h 45 min |
| 2026-01-15 20:53 UTC | Temporary service disruption | resolved | none | 2 h 55 min |
| 2026-01-12 21:48 UTC | Temporary Surge of "Device Stopped Streaming" Events | resolved | none | 2 h 22 min |
| 2025-12-19 17:22 UTC | Intermittent network issues possible in several regions. | resolved | none | 4 h 54 min |
| 2025-12-09 17:42 UTC | Delayed ingesting device streaming state | resolved | none | 6 h 17 min |
| 2025-12-08 23:57 UTC | Incorrect Device Streaming State affecting some Customers | resolved | none | 0 min |
| 2025-10-12 11:05 UTC | Platform outage | resolved | major | 3 h 09 min |
| 2025-09-16 18:38 UTC | High Device Streaming Latency experienced on the Platform | resolved | none | 23 min |
| 2025-09-11 18:00 UTC | High Device Streaming Latency experienced on the Platform | resolved | none | 5 h 17 min |
| 2025-09-10 23:18 UTC | High Device Streaming Latency experienced on the Platform | resolved | none | 1 h 13 min |
| 2025-09-08 12:56 UTC | Elevated connections and requests failure | postmortem | critical | 2 h 38 min |
| 2025-09-02 03:38 UTC | Device state and updates may be delayed | postmortem | none | 1 h 59 min |
| 2025-09-01 17:39 UTC | Flow data processing outage | postmortem | none | 11 h 47 min |
| 2025-09-01 14:09 UTC | Issue with Image Repository | resolved | none | 17 min |
| 2025-08-26 20:59 UTC | Issues building workspaces | resolved | none | 2 h 15 min |
| 2025-08-21 17:41 UTC | Issues building workspaces | resolved | none | 55 min |
| 2025-08-13 15:27 UTC | High Processing Latency | resolved | none | 0 min |
| 2025-08-13 13:04 UTC | High Device Streaming Latency experienced on the Platform | resolved | none | 18 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Arista Cloudvision with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"arista-cloudvision"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}