{
"vendor": "Arista Cloudvision",
"slug": "arista-cloudvision",
"platform": "statuspage",
"status_url": "https://status.arista.io",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-10T12:15:40Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-10T04:03:26.382Z",
"resolved_inferred": false,
"started_at": "2026-09-09T20:02:43.890Z",
"state": "resolved",
"title": "Platform wide Disruption",
"updated_at": "2026-09-10T04:03:26.399Z",
"url": "https://stspg.io/rbjq8l3hyxkp"
},
{
"body": "A mitigation was put in place and the performance is now stabilized. We will continue to monitor the situation. Thank you",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-01T04:47:56.942Z",
"resolved_inferred": false,
"started_at": "2026-09-01T03:22:34.450Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2026-09-01T04:47:56.963Z",
"url": "https://stspg.io/wv4mf6255y6t"
},
{
"body": "This incident arose from unexpected localized network partitioning due to underlying conditions. Our systems automatically detected the event in <5m of the start of the impact, and began recovery, with minimal manual intervention involved. We are analyzing further hardening against the underlying conditions of this nature.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-28T20:40:36.781Z",
"resolved_inferred": false,
"started_at": "2026-08-28T17:39:57.230Z",
"state": "resolved",
"title": "Platform Disruption",
"updated_at": "2026-08-28T20:40:36.799Z",
"url": "https://stspg.io/zy2qz6k6qt3j"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-20T05:09:23.081Z",
"resolved_inferred": false,
"started_at": "2026-08-20T02:54:03.744Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2026-08-20T05:09:23.101Z",
"url": "https://stspg.io/3dtb1f876h1m"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-12T19:03:50.725Z",
"resolved_inferred": false,
"started_at": "2026-08-12T18:51:17.000Z",
"state": "resolved",
"title": "Core platfrorm",
"updated_at": "2026-08-12T19:03:50.738Z",
"url": "https://stspg.io/wpgnhbpcsvnc"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-13T05:25:27.232Z",
"resolved_inferred": false,
"started_at": "2026-08-12T16:19:38.427Z",
"state": "resolved",
"title": "Device Experiencing Streaming Issues",
"updated_at": "2026-08-13T05:25:27.265Z",
"url": "https://stspg.io/nw96jnqcf24p"
},
{
"body": "The issue has been identified and a mitigation has been put in place. Streaming latencies have returned to their expected level.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-06T11:47:35.502Z",
"resolved_inferred": false,
"started_at": "2026-08-06T10:45:23.704Z",
"state": "resolved",
"title": "High Streaming Latency",
"updated_at": "2026-08-06T11:47:35.523Z",
"url": "https://stspg.io/c8bfthpv2t8x"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-15T21:45:15.101Z",
"resolved_inferred": false,
"started_at": "2026-07-15T21:45:01.991Z",
"state": "resolved",
"title": "Change Control disruption",
"updated_at": "2026-07-15T21:45:15.118Z",
"url": "https://stspg.io/97wbxkzj3tqv"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-15T03:27:33.953Z",
"resolved_inferred": false,
"started_at": "2026-07-15T01:09:33.713Z",
"state": "resolved",
"title": "Change Control disruption",
"updated_at": "2026-07-15T03:27:33.969Z",
"url": "https://stspg.io/wrh95xj8tqqx"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-10T18:46:39.905Z",
"resolved_inferred": false,
"started_at": "2026-07-10T18:25:05.679Z",
"state": "resolved",
"title": "Temporary Ingestion Lag",
"updated_at": "2026-07-10T18:46:39.920Z",
"url": "https://stspg.io/0ngytwwvwwm4"
},
{
"body": "This issue is resolved. Please follow https://status.arista.io/incidents/5vx7cvb07k7d for postmortem update when it becomes available.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-13T23:54:59.538Z",
"resolved_inferred": false,
"started_at": "2026-07-07T22:58:26.134Z",
"state": "resolved",
"title": "[Informational Only] CloudVision may report brief elevated Streaming Latencies for devices for service region cv-prod-us-central1-b",
"updated_at": "2026-07-13T23:54:59.556Z",
"url": "https://stspg.io/19bvg200ncwk"
},
{
"body": "**Incident Report: CVaaS Service Disruption - June 26th, 2026**\n\nOn June 26th, 2026 10:00AM PDT - 12:30PM PDT CVaaS service region cv-prod-us-central1-b experienced significant ingestion delay into NetDL that caused the following incorrect states to be observed by users:\n\n* Devices incorrectly marked as Inactive,\n* Multiple inactionable \u201cDevice Stopped Streaming\u201d events,\n* Multiple inactionable \u201cHigh Streaming Latency\u201d events\n\nDuring this time period, executing device provisioning actions may have been delayed or failed. There was no data loss. However, data ingested from actively streaming devices into CVaaS may have only become accessible after some delay. This may have impacted users accessing the UI, or other services consuming that data from CloudVision via API integrations. \n\nBetween June 26, 2026 12:30PM PDT - June 27th, 12:30PM PDT, some users may have experienced the above behaviors intermittently impact their devices, but not block device provisioning activities.\n\nBy June 27th, 2026, all mitigations were in place, and we transitioned to mitigating intermittent instances of elevated tail latency along the data ingestion path into NetDL. Between June 27th, 2026 and July 6th, 2026 a small subset of users of the cv-prod-us-central1-b service region may have experienced rare, but intermittent instances where CloudVision reported Event \u201cHigh Streaming Latency\u201d, potentially due to brief delays in NetDL ingestion. Users were not blocked from performing device provisioning activities.\n\n\u200c\n\n**Root Cause**\n\nNetwork performance degradation and instabilities in our underlying cloud provider were the ultimate root causes of delays ingesting data into the part of the system responsible for storing, processing, and updating device streaming status and streaming latency. Our mitigation activities between June 26th, 2026 and June 27th, 2026 stabilized the vast majority of the impact, but the changing underlying conditions prolonged the total duration of incident. This incident was not caused by software change\\(s\\), monitoring gaps, or software bugs in CloudVision as-a-Service.\n\n\u200c\n\n**Our Response**\n\nMultiple teams at Arista engaged around the clock from June 26th, 2026 until July 6th, 2026 to ensure we fully resolved this incident, as well as reviewed all details in our internal reviews. We continue to actively monitor this service region, as well as all of our CloudVision as-a-Service service regions.\n\nArista takes full responsibility for the performance and availability of the service regardless of the underlying cloud platform conditions. We are committed to making changes in both the short and long term that will provide greater resilience to underlying provider instabilities and changing real-time conditions.\n\nThank you for using CloudVision as-a-Service.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-07T22:57:18.224Z",
"resolved_inferred": false,
"started_at": "2026-06-26T17:27:17.754Z",
"state": "postmortem",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2026-07-20T23:53:28.660Z",
"url": "https://stspg.io/18tdp593wh9y"
},
{
"body": "We identified the source of the problem and the data ingestion latency has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-10T16:03:13.608Z",
"resolved_inferred": false,
"started_at": "2026-06-10T11:48:01.850Z",
"state": "resolved",
"title": "High Streaming Latency",
"updated_at": "2026-06-10T16:03:13.623Z",
"url": "https://stspg.io/3gf2fjjrbf35"
},
{
"body": "**Incident Report: CVaaS Service Disruption - May 29, 2026**\n\nOn May 29th, 2026, CloudVision as-a-Service delivered a software change for a set of services that provide the Network Provisioning workflows in the product. All services regions were impacted by this Network Provisioning feature update.\u00a0\n\nThis update introduced a critical bug across all service regions. As a result, customers utilizing the Network Provisioning workflows \\(see [https://www.arista.io/help/articles/provisioning-network-provisioning#network-provisioning](https://www.arista.io/help/articles/provisioning-network-provisioning#network-provisioning)\\) may have experienced instances where devices were mapped to the incorrect containers in the network provisioning hierarchy, creating a risk that unintended configuration states could be applied if customers then attempted to roll out additional changes to devices. The Network Provisioning workflows were disabled while we recovered from the issue, meaning that customers could not make any changes to their network configuration during this time.\n\nCustomers only defining their network configuration using Studios workflows \\(see [https://www.arista.io/help/articles/provisioning-studios](https://www.arista.io/help/articles/provisioning-studios)\\) were not impacted.\n\nThe software change that caused this issue was rolled back on May 29th, 2026. The delay in mitigation was due to gaps in our automated monitoring systems.\n\nFAQ:\n\n* _Did this bug cause a network outage for customers?_ No.\n* _Was there any data loss?_ No.\n* Was overall CloudVision service availability impacted?No.\n* _Are there any additional steps to recovery?_ No; the vast majority of impacted customers were recovered without requiring customer intervention. At this moment if you have not been directly contacted by us, no further action is required from you.\n\n\u200c\n\n**Root Cause**\n\nThe bug was due to logic applied to an incorrect data state within the Network Provisioning feature. This caused an incorrect device container mapping during the device state reconciliation phase. This was not caught during testing or during the post deployment evaluation phase in various environments prior to being released to production. Additionally, the rollout strategy used in the continuous delivery applicable for this particular set of services allowed the bug to propagate quickly across all CloudVision as-a-Service regions.\n\n\u200c\n\n**Our Response**\n\nOnce the bug was identified on May 29th, 2026, our team rolled back the update responsible within approximately a five hour period on all production regions. In addition, API usage restrictions were established as a protective measure against customers that may inadvertently execute a configuration change on their network without knowledge of this bug and device state change. Between May 29th and June 1st, 2026, our team engaged in continuous efforts to restore services for all affected customers and devices. The majority of these recovery operations were successfully concluded by May 30th, 2026. Throughout this period, we maintained regular updates on Statuspage to keep our customers informed regarding our progress.\n\nWe understand a disruption of this nature is unacceptable for our customers. We are conducting a full review of design, testing, validation, delivery, monitoring, and incident response as part of the postmortem review, and we are committed to ensuring we do not run into incidents of this nature in the future.\u00a0\n\nThank you for using CloudVision as-a-Service.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-04T00:50:38.220Z",
"resolved_inferred": false,
"started_at": "2026-05-29T20:24:49.338Z",
"state": "postmortem",
"title": "Network Provisioning - Device is present in an unexpected container",
"updated_at": "2026-06-04T00:52:03.604Z",
"url": "https://stspg.io/g523jwb8tppj"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-29T21:02:17.763Z",
"resolved_inferred": false,
"started_at": "2026-05-29T17:45:17.916Z",
"state": "resolved",
"title": "Network Provisioning/Studios - Incorrect End Configurations Generated",
"updated_at": "2026-05-29T21:02:17.785Z",
"url": "https://stspg.io/mthnpxskt9jl"
},
{
"body": "This incident has been resolved. We will follow up with a postmortem.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-27T01:02:39.759Z",
"resolved_inferred": false,
"started_at": "2026-05-26T15:38:23.965Z",
"state": "resolved",
"title": "Issues logging into the platform",
"updated_at": "2026-05-27T01:02:39.773Z",
"url": "https://stspg.io/knr5jghlqt8h"
},
{
"body": "We experienced high device streaming latency on this affected cluster. \n\nSome impact may be user visible, such as:\n- 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.\n- There may be some stale data, or sporadic timeouts viewing parts of the UI.\n- Some provisioning features may be delayed or timeout due to the high latency.\n\nThis 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-18T13:35:22.839Z",
"resolved_inferred": false,
"started_at": "2026-05-18T13:35:22.776Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2026-05-18T13:35:22.851Z",
"url": "https://stspg.io/b893bs84mcf1"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-15T17:30:14.843Z",
"resolved_inferred": false,
"started_at": "2026-05-15T17:24:21.000Z",
"state": "resolved",
"title": "Partial outage in network provisioning",
"updated_at": "2026-05-15T17:30:14.858Z",
"url": "https://stspg.io/ctb1hj1wj8sy"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-15T12:34:33.103Z",
"resolved_inferred": false,
"started_at": "2026-04-15T12:04:42.879Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2026-04-15T12:34:33.120Z",
"url": "https://stspg.io/x2sxcyxjb967"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-19T00:57:11.179Z",
"resolved_inferred": false,
"started_at": "2026-03-19T00:38:53.548Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2026-03-19T00:57:11.197Z",
"url": "https://stspg.io/ndcyq9g5f69v"
},
{
"body": "The fix has been successfully deployed to all regions. Customers will have to reload the UI for the changes to take effect.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-12T21:57:50.933Z",
"resolved_inferred": false,
"started_at": "2026-03-12T15:33:08.562Z",
"state": "resolved",
"title": "Performance Degradation in Provisioning Tasks Window",
"updated_at": "2026-03-12T21:57:50.950Z",
"url": "https://stspg.io/fgkbqpyv25l9"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-04T06:43:05.682Z",
"resolved_inferred": false,
"started_at": "2026-03-04T05:23:36.000Z",
"state": "resolved",
"title": "Partial Outage of Secured ZTP (sztp) / License management functionality",
"updated_at": "2026-03-04T06:53:02.918Z",
"url": "https://stspg.io/611dxxsf35ct"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-03T04:31:27.923Z",
"resolved_inferred": false,
"started_at": "2026-03-03T04:15:47.058Z",
"state": "resolved",
"title": "Elevated request errors",
"updated_at": "2026-03-03T04:31:27.938Z",
"url": "https://stspg.io/snztb2krq9s7"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-17T16:54:04.498Z",
"resolved_inferred": false,
"started_at": "2026-02-13T01:30:08.000Z",
"state": "resolved",
"title": "Device configuration diff is not loading on Change Control page",
"updated_at": "2026-02-17T16:54:04.520Z",
"url": "https://stspg.io/y4ck2vv7qvfz"
},
{
"body": "**Incident Report: Platform Outage - January 31st, 2026**\n\nOn January 31, 2026, CloudVision as-a-Service experienced a platform-wide incident within the cv-prod-us-central1-a region that lasted a total of 1 hour and 18 minutes. During the first hour of this window, the platform remained operational despite intermittent connectivity disruptions that impacted <1% of total traffic. In the final 18 minutes of the incident, traffic loss increased to approximately 2%. During this period, users likely experienced a gradual loss of connectivity and platform access. This included disruptions to device streaming, where devices may have started to coalesce data to resume streaming once platform stabilized, which is the standard failure-mode behavior designed to preserve data integrity during network instability.\n\nThis incident was not the result of a security breach, unauthorized intrusion, or any malicious activity.\n\n\u200c\n\n**Root Cause**\n\nThe root cause of this disruption was identified as a catastrophic networking loss within our third-party cloud infrastructure provider.\n\n\u200c\n\n**Our Response**\n\nOur team detected the outage within five minutes of the initial failure and remained in constant communication with the provider to manage triage, recovery, and remediation efforts. During the incident, we made the strategic decision not to initiate a full site disaster recovery. Our technical assessment concluded that a full failover would have been significantly more disruptive to the user experience and would have ultimately prolonged the duration of the incident.\n\n\u200c\n\nWe understand that any service interruption is an unacceptable outcome for our users. We are currently working on internal initiatives to make our architecture more resilient to these specific modes of failure while simultaneously partnering with our cloud provider to ensure better stability of the underlying infrastructure.\n\n\u200c\n\nWe appreciate your patience and your continued use of CloudVision as-a-Service.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-31T01:42:31.826Z",
"resolved_inferred": false,
"started_at": "2026-01-31T00:16:11.984Z",
"state": "postmortem",
"title": "Platform Disruption",
"updated_at": "2026-02-13T21:02:12.322Z",
"url": "https://stspg.io/rzt9svj2jbxr"
},
{
"body": "**Incident Report: Login By Email Service Outage - January 30th, 2026**\n\nOn January 30, 2026, CloudVision as-a-Service experienced a service outage affecting the \"Login By Email\" functionality lasting 2 hours and 36 minutes. During this window, customers attempting to access their accounts using Login By Email failed to receive the invitation emails. This incident was isolated strictly to the Login By Email service; SSO and SAML based login remained fully operational.\n\nThere was no data loss or compromise of customer information. This outage was not the result of a security breach, unauthorized intrusion, or any malicious activity.\n\n**Root Cause**\n\nOur investigation identified a gap in monitoring for a critical third-party integration. Because this specific telemetry was missing, early warning signals were missed, leading to the eventual service disruption. Additionally, we identified internal process failures that contributed to the duration of the outage.\n\n**Our Response**\n\nInternal escalation protocols successfully engaged subject matter experts within 30 minutes of the first reported case. Initial delays in resolution were primarily due to various process failures including delays in required coordination with third party vendor. We are implementing the missing monitoring triggers for third-party integrations to ensure early detection, as well as reviewing our processes as part of various fixes we are addressing.\n\nWe understand that any service disruption is impactful. We are committed to implementing changes identified during our internal investigation to prevent this type of failure from happening again.\n\nThank you for using CloudVision as-a-Service.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-30T16:05:26.723Z",
"resolved_inferred": false,
"started_at": "2026-01-30T14:36:34.310Z",
"state": "postmortem",
"title": "Outage affecting 'Log in with Email'",
"updated_at": "2026-02-05T22:19:52.333Z",
"url": "https://stspg.io/dcfd52klkydx"
},
{
"body": "Telemetry was delayed for up to 30 minutes due to an disruptive infrastructure reconfiguration. The incident has now been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-23T12:13:47.702Z",
"resolved_inferred": false,
"started_at": "2026-01-23T09:28:30.595Z",
"state": "resolved",
"title": "Platform disruption",
"updated_at": "2026-01-23T12:13:54.636Z",
"url": "https://stspg.io/ybxqyqxxsl56"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-15T23:49:30.238Z",
"resolved_inferred": false,
"started_at": "2026-01-15T20:53:52.525Z",
"state": "resolved",
"title": "Temporary service disruption",
"updated_at": "2026-01-15T23:49:30.254Z",
"url": "https://stspg.io/821vk6kdfwnp"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-13T00:11:03.157Z",
"resolved_inferred": false,
"started_at": "2026-01-12T21:48:47.442Z",
"state": "resolved",
"title": "Temporary Surge of \"Device Stopped Streaming\" Events",
"updated_at": "2026-01-13T00:11:03.179Z",
"url": "https://stspg.io/r6lmj99y1kz3"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-19T22:17:01.161Z",
"resolved_inferred": false,
"started_at": "2025-12-19T17:22:14.735Z",
"state": "resolved",
"title": "Intermittent network issues possible in several regions.",
"updated_at": "2025-12-19T22:17:01.184Z",
"url": "https://stspg.io/8yz1dn5ckbzv"
},
{
"body": "Closing this courtesy notice.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-09T23:59:34.329Z",
"resolved_inferred": false,
"started_at": "2025-12-09T17:42:18.000Z",
"state": "resolved",
"title": "Delayed ingesting device streaming state",
"updated_at": "2025-12-09T23:59:34.351Z",
"url": "https://stspg.io/06qtrt76594f"
},
{
"body": "Hello CloudVision as a Service customers,\n\nWe 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.\n\nImpacted customers may have observed this incorrect streaming status displayed for several consecutive hours or days since November 25th, 2025. \n\nWe 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.\n\nIf you have any questions about this issue or if your tenant was affected, please reach out to support@arista.com.\n\nThank you for being a valued CloudVision as a Service customer.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-08T23:57:38.551Z",
"resolved_inferred": false,
"started_at": "2025-12-08T23:57:38.505Z",
"state": "resolved",
"title": "Incorrect Device Streaming State affecting some Customers",
"updated_at": "2025-12-08T23:57:38.563Z",
"url": "https://stspg.io/hyq2hskymxbf"
},
{
"body": "The data processing pipeline has fully recovered, and the service is now operating in a healthy state.\n\nThe ingestion of device telemetry data was not impacted during the incident. There was no data loss.\n\nPostmortem for this incident is still pending. Our team is currently actively working on reviewing this incident, and postmortem update.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-12T14:15:00.312Z",
"resolved_inferred": false,
"started_at": "2025-10-12T11:05:27.234Z",
"state": "resolved",
"title": "Platform outage",
"updated_at": "2025-10-12T14:39:40.216Z",
"url": "https://stspg.io/jxcpq0jpkhmw"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-16T19:01:13.690Z",
"resolved_inferred": false,
"started_at": "2025-09-16T18:38:05.616Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2025-09-16T19:01:13.708Z",
"url": "https://stspg.io/4pwdt4c6rzdd"
},
{
"body": "This incident is resolved",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-11T23:17:38.156Z",
"resolved_inferred": false,
"started_at": "2025-09-11T18:00:35.380Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2025-09-11T23:17:38.175Z",
"url": "https://stspg.io/q8tlf5431zjr"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-11T00:32:19.636Z",
"resolved_inferred": false,
"started_at": "2025-09-10T23:18:33.114Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2025-09-11T00:32:19.660Z",
"url": "https://stspg.io/yp8j39m55pnz"
},
{
"body": "**Incident Report: CVaaS Service Disruption - September 8, 2025**     \nOn 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.\n\nWe 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.\n\n\u200c\n\n**Root Cause**\n\nAn 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.\n\n\u200c\n\n**Our Response**\n\nOur 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.\n\nWe 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.\n\nThank you for using CloudVision as-a-Service.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-08T15:35:04.842Z",
"resolved_inferred": false,
"started_at": "2025-09-08T12:56:47.000Z",
"state": "postmortem",
"title": "Elevated connections and requests failure",
"updated_at": "2025-09-16T18:55:04.079Z",
"url": "https://stspg.io/m766hyp5tgn2"
},
{
"body": "## **Incident Report: CVaaS Service Disruption - September 1, 2025**\n\nOn 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.\u200c\n\n**Root Cause**\n\nThe 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.\n\nThank you for using CloudVision as-a-Service.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-02T05:38:02.043Z",
"resolved_inferred": false,
"started_at": "2025-09-02T03:38:10.444Z",
"state": "postmortem",
"title": "Device state and updates may be delayed",
"updated_at": "2025-09-09T00:45:01.603Z",
"url": "https://stspg.io/j5tc6yvmrbpd"
},
{
"body": "## **Incident Report: CVaaS Service Disruption - September 1, 2025**\n\nOn 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.\n\n  \n**Root cause**\n\nThis 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\u2019s 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.\n\n  \n**Our Response**\n\nOur 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.\n\nWe 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.  \n\nThank you for using CloudVision as-a-Service.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-02T05:27:01.000Z",
"resolved_inferred": false,
"started_at": "2025-09-01T17:39:23.067Z",
"state": "postmortem",
"title": "Flow data processing outage",
"updated_at": "2025-09-08T18:10:51.602Z",
"url": "https://stspg.io/gdtd4l618z7f"
},
{
"body": "The fix has been deployed and this incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-01T14:26:29.658Z",
"resolved_inferred": false,
"started_at": "2025-09-01T14:09:08.656Z",
"state": "resolved",
"title": "Issue with Image Repository",
"updated_at": "2025-09-01T14:26:29.675Z",
"url": "https://stspg.io/17gl7r8l4c9j"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-26T23:14:51.685Z",
"resolved_inferred": false,
"started_at": "2025-08-26T20:59:19.277Z",
"state": "resolved",
"title": "Issues building workspaces",
"updated_at": "2025-08-26T23:14:51.699Z",
"url": "https://stspg.io/kyfh45n30vxy"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-21T18:36:43.756Z",
"resolved_inferred": false,
"started_at": "2025-08-21T17:41:34.013Z",
"state": "resolved",
"title": "Issues building workspaces",
"updated_at": "2025-08-21T18:36:43.774Z",
"url": "https://stspg.io/jg778prvdx6k"
},
{
"body": "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.\n\nSome impact may have been user visible, such as:\n- Some events, such as \"Device stopped streaming\" or \"Streaming Latency Breached Threshold\" may have fired incorrectly during this period.\n- There may have been sporadic timeouts when viewing parts of the UI.\n- There may have been general slowdown of provisioning activities, potentially resulting in timeouts or errors.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-13T15:27:32.710Z",
"resolved_inferred": false,
"started_at": "2025-08-13T15:27:32.652Z",
"state": "resolved",
"title": "High Processing Latency",
"updated_at": "2025-08-13T15:27:32.722Z",
"url": "https://stspg.io/snyk3bqbxm1g"
},
{
"body": "A fix has been implemented and performance has returned to normal.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-13T13:23:16.832Z",
"resolved_inferred": false,
"started_at": "2025-08-13T13:04:53.609Z",
"state": "resolved",
"title": "High Device Streaming Latency experienced on the Platform",
"updated_at": "2025-08-14T02:37:10.991Z",
"url": "https://stspg.io/454nr8gz0vdd"
}
]
}