Arista CloudVision Outage History

Arista CloudVision is up right now

Arista CloudVision had 39 outages in the last 2 years totaling 28h 38m of downtime — averaging 1.6 incidents per month.

There were 39 Arista CloudVision outages since December 2, 2024 totaling 28h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.arista.io

Notice June 16, 2025

[Informational] CloudVision as-a-Service will no longer officially support devices running EOS 4.23, 4.24, or 4.25 trains starting January 1st, 2026

Detected by Pingoru
Jun 16, 2025, 05:03 PM UTC
Resolved
Jun 16, 2025, 04:59 PM UTC
Duration
—
Timeline · 1 update
  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 →

Notice June 12, 2025

Service disruption on all CVaaS regions

Detected by Pingoru
Jun 12, 2025, 06:46 PM UTC
Resolved
Jun 13, 2025, 02:11 AM UTC
Duration
7h 24m
Affected: Core PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosEventsEventsEventsEventsEventsEventsEventsEventsEventsLoginLoginLoginLoginLoginLoginLoginLoginLogin
Timeline · 6 updates

Read the full incident report →

Notice June 12, 2025

Platform Slowness

Detected by Pingoru
Jun 12, 2025, 12:22 PM UTC
Resolved
Jun 12, 2025, 12:45 PM UTC
Duration
22m
Affected: Core Platform
Timeline · 2 updates
  1. investigating Jun 12, 2025, 12:22 PM UTC

    Hello CVaaS Users, We are experiencing a temporary platform slowness from 2025-06-12 12:15 UTC. During this time there may be "Devices Stopped Streaming" events firing.

  2. resolved Jun 12, 2025, 12:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 13, 2025

Known Impact on CVaaS

Detected by Pingoru
Mar 13, 2025, 10:29 PM UTC
Resolved
Mar 13, 2025, 11:21 PM UTC
Duration
51m
Affected: Core PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore Platform
Timeline · 2 updates
  1. identified Mar 13, 2025, 10:29 PM UTC

    We have discovered an issue that may impact a subset of users on CVaaS. We have identified the issue and working on mitigation. We're focusing on mitigation and will provide RCA as soon as possible. Thank you for your patience.

  2. resolved Mar 13, 2025, 11:21 PM UTC

    We have resolved the known issue and are reaching out to impacted customers directly. If you do not hear from us in the next hour you are not impacted by this incident. We are prioritizing working with impacted customers first, and will circle back for RCA update.

Read the full incident report →

Notice February 27, 2025

Performance degradation

Detected by Pingoru
Feb 27, 2025, 03:35 PM UTC
Resolved
Feb 27, 2025, 05:17 PM UTC
Duration
1h 41m
Affected: Core PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformCore PlatformNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosEventsEventsEventsEventsEventsEventsEventsEventsLoginLoginLoginLoginLoginLoginLoginLogin
Timeline · 2 updates
  1. identified Feb 27, 2025, 03:35 PM UTC

    We're aware of transient spikes in processing latency affecting all regions following an upgrade. We have identified the root cause and are working on mitigation. Thank you for your patience.

  2. resolved Feb 27, 2025, 05:17 PM UTC

    This fix has been rolled out and this incident has been resolved.

Read the full incident report →

Major February 21, 2025

Temporary "DeadlineExceeded" Errors seen on various APIs

Detected by Pingoru
Feb 21, 2025, 06:40 PM UTC
Resolved
Feb 21, 2025, 06:40 PM UTC
Duration
—
Affected: Network Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosNetwork Provisioning - StudiosEventsEventsEventsEventsEventsEventsEventsEventsLoginLoginLoginLoginLoginLoginLoginLogin
Timeline · 1 update
  1. resolved Feb 21, 2025, 06:40 PM UTC

    Hello CVaaS users, You may have experienced various red toast errors with message such as "DeadlineExceeded.." when viewing, interacting, or using various UI or APIs. We sincerely apologize for this issue. The offending change has been identified, rolledback, and should no longer be present. If you are still experiencing these red toast errors, please reach out to [email protected]. Thank you.

Read the full incident report →

Major February 20, 2025

Elevated error rate

Detected by Pingoru
Feb 20, 2025, 10:52 AM UTC
Resolved
Feb 20, 2025, 11:24 AM UTC
Duration
32m
Affected: Core Platform
Timeline · 3 updates
  1. investigating Feb 20, 2025, 10:52 AM UTC

    We are currently observing an elevated error rate on this cluster.

  2. monitoring Feb 20, 2025, 10:59 AM UTC

    Our reverse proxy was throwing errors, we've mitigated the issue and are investigating the root cause.

  3. resolved Feb 20, 2025, 11:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 24, 2025

ChangeControls failing to execute

Detected by Pingoru
Jan 24, 2025, 06:16 PM UTC
Resolved
Jan 24, 2025, 07:13 PM UTC
Duration
57m
Affected: Network Provisioning - Studios
Timeline · 3 updates
  1. investigating Jan 24, 2025, 06:16 PM UTC

    We are aware that changecontrols are failing to execute. We are currently investigating the cause of this issue and working on resolution. Thank you for your patience.

  2. monitoring Jan 24, 2025, 06:56 PM UTC

    We've applied a rollback that was causing this issue. We'll continue to monitor change control usage and update.

  3. resolved Jan 24, 2025, 07:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 21, 2025

New events not processing

Detected by Pingoru
Jan 21, 2025, 07:20 PM UTC
Resolved
Jan 22, 2025, 01:23 AM UTC
Duration
6h 3m
Affected: Events
Timeline · 4 updates
  1. investigating Jan 21, 2025, 07:20 PM UTC

    We are currently experiencing issues with events processing. There are no new events generated. We will update as soon as we have more information.

  2. monitoring Jan 21, 2025, 10:22 PM UTC

    The issue has been identified and a mitigation has been implemented. We're monitoring the incident to ensure the issue is fully resolved.

  3. monitoring Jan 21, 2025, 11:01 PM UTC

    All expected event generation should be functional. We're continuing to monitor the incident.

  4. resolved Jan 22, 2025, 01:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 14, 2025

Platform slowness

Detected by Pingoru
Jan 14, 2025, 05:19 PM UTC
Resolved
Jan 14, 2025, 11:29 PM UTC
Duration
6h 10m
Affected: Core PlatformCore Platform
Timeline · 6 updates
  1. monitoring Jan 14, 2025, 05:19 PM UTC

    Some dashboards can be slow. We expect that it will improve in 30 min.

  2. monitoring Jan 14, 2025, 06:19 PM UTC

    Some services still may be slow. We expect improvement in the next hour.

  3. monitoring Jan 14, 2025, 07:04 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jan 14, 2025, 10:00 PM UTC

    us-central1-c region has recovered. We are still mitigating the platform slowness on us-central1-a.

  5. monitoring Jan 14, 2025, 10:34 PM UTC

    Both us-central1-a and us-central1-c regions have recovered. We are continuing to monitor.

  6. resolved Jan 14, 2025, 11:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 13, 2025

Data ingestion is blocked

Detected by Pingoru
Jan 13, 2025, 06:18 AM UTC
Resolved
Jan 13, 2025, 10:23 AM UTC
Duration
4h 5m
Affected: Core PlatformNetwork Provisioning - StudiosEventsLogin
Timeline · 5 updates
  1. investigating Jan 13, 2025, 06:18 AM UTC

    One of our databases is in read only mode. We are investigating the issue.

  2. identified Jan 13, 2025, 08:24 AM UTC

    The system is catching up now, ETA to catch up is approximately 1hr.

  3. identified Jan 13, 2025, 09:04 AM UTC

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

  4. monitoring Jan 13, 2025, 09:37 AM UTC

    Everything is back to normal, data backlogged has been ingested, we're continuing to monitor the situation and will then proceed with our postmortem analysis.

  5. resolved Jan 13, 2025, 10:23 AM UTC

    The incident has been resolved, we're still working on our postmortem analysis and will follow up with a detailed RCA soon.

Read the full incident report →

Major December 2, 2024

Ingest processing delay

Detected by Pingoru
Dec 02, 2024, 08:51 PM UTC
Resolved
Dec 02, 2024, 09:20 PM UTC
Duration
29m
Affected: Core Platform
Timeline · 3 updates
  1. investigating Dec 02, 2024, 08:51 PM UTC

    Telemetry and application data currently being published to the platform is currently being processed slowly, we're investigating.

  2. monitoring Dec 02, 2024, 09:04 PM UTC

    Process lag has been caught up. We've identified the root cause to a disruptive configuration change. We're monitoring the situation and following up on the root cause and possible next steps to prevent this from reoccurring.

  3. resolved Dec 02, 2024, 09:20 PM UTC

    This incident has been resolved.

Read the full incident report →