Cypress Cloud

Affected: Authentication, GitHub API Requests, GitHub Actions, GitHub Copilot, GitHub Git Operations, GitHub Issues, GitHub Pages, GitHub Pull Requests, GitHub Visit www.githubstatus.com for more information, GitHub Webhooks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-17 15:55 UTC

   We are experiencing problems related to a major outage in Github

2. investigating 2026-08-17 15:57 UTC

   We are continuing to investigate this issue.

3. investigating 2026-08-17 17:10 UTC

   Update from Github: The degradation affecting API Requests, Actions, Git Operations, Issues, Pages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

4. resolved 2026-08-17 17:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-13 01:23 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. investigating 2026-08-13 01:27 UTC

   The backend service powering enterprise reporting is experiencing issues. We are monitoring the issue

3. monitoring 2026-08-13 01:54 UTC

   We have implemented a fix and are monitoring the system

4. resolved 2026-08-13 02:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 21:14 UTC

   We have identified an issue with the Data Extract API that may be preventing some users from retrieving data. Engineering resources are engaged.

2. monitoring 2026-08-06 22:14 UTC

   Engineers have identified the problem and are implementing a fix. We're monitoring the system and will update when complete.

3. resolved 2026-08-06 22:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Accessibility, UI Coverage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 20:16 UTC

   An issue has been detected with the Cypress Cloud service related to viewing Accessibility and UI Coverage results. Engineering resources are engaged and troubleshooting.

2. investigating 2026-08-05 20:19 UTC

   We are continuing to investigate this issue.

3. identified 2026-08-05 20:25 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-08-05 20:28 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-08-05 21:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Accessibility, UI Coverage

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-17 11:30 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. investigating 2026-07-17 11:34 UTC

   An issue has been detected with App Quality reporting. Some users may see degradation in the speed with which their reports are being processed. Engineering resources are engaged and troubleshooting.

3. monitoring 2026-07-17 12:23 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-17 13:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-16 20:40 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. investigating 2026-07-16 20:58 UTC

   This is only affecting Studio AI recommendations and cy.prompt

3. resolved 2026-07-16 21:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-29 17:42 UTC

   We are experiencing rendering errors on the Test Replay feature. The problem has been identified and a fix is being prepared.

2. monitoring 2026-06-29 18:51 UTC

   A fix has been deployed; team will continue to monitor

3. resolved 2026-06-29 19:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-25 09:27 UTC

   We're experiencing a performance degradation of Cypress Cloud and are investigating

2. monitoring 2026-06-25 11:25 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-25 14:26 UTC

   This incident is resolved

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-07 14:36 UTC

   We are currently investigating this issue.

2. investigating 2026-05-07 14:37 UTC

   We are currently working on a fix

3. resolved 2026-05-07 16:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Test Recording

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 17:28 UTC

   We are currently investigating this issue.

2. investigating 2026-05-06 17:29 UTC

   We are continuing to investigate this issue.

3. identified 2026-05-06 17:38 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-05-06 17:47 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2026-05-06 17:48 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-05-06 18:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-01-08 17:46 UTC

   We are currently experiencing delays in Test Replay processing and are continuing to monitor the backlog of data.

2. resolved 2026-01-08 18:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-07 23:00 UTC

   Yesterday, Jan. 7th 2026, Cypress Cloud started experiencing significant delays in Test Replay availability around 23:00 UTC and is currently ongoing. A new incident will be opened shortly as we monitor the backlog of processing.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-12-17 19:00 UTC

   Yesterday, Dec. 17th 2025, Cypress Cloud was experiencing significant delays in Test Replay availability starting 19:00 UTC lasting for approximately 5 hours. The processing of Test Replay data returned to nominal processing times at approximately 00:00 UTC on Dec. 18th, 2025.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Test Recording, Authentication, Billing, Integrations, Download, Documentation, Analytics, Upstream Service Provider, Accessibility, UI Coverage

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-18 16:34 UTC

   We're still experiencing intermittent issues with upstream providers

2. monitoring 2025-11-18 17:49 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-11-18 17:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 12:48 UTC

   We are seeing impacts of an upstream provider (Cloudflare) impacting our services.

2. identified 2025-11-18 13:11 UTC

   Marking this as Identified as the cause is known (upstream networking outages). We have confirmed the partial nature of this outage impacting our customers.

3. resolved 2025-11-18 14:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-12 22:29 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. monitoring 2025-11-12 22:37 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-11-12 22:56 UTC

   The issue was identified and related changes were rolled back. Systems have returned to normal response times.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Authentication, Billing, Integrations, Analytics, Accessibility, UI Coverage

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:50 UTC

   We are currently investigating this issue.

2. investigating 2025-10-20 09:46 UTC

   AWS Operational Issue affecting multiple services in N. Virginia (https://health.aws.amazon.com/health/status?path=open-issues) identified as root cause

3. investigating 2025-10-20 10:37 UTC

   AWS services are incrementally recovering; but compute services are still experiencing issues & capacity remains constrained, impacting service restoration.

4. identified 2025-10-20 10:38 UTC

   Flagging incident as identified; recovery still in progress with resource constraints impacting services restoration

5. identified 2025-10-20 13:02 UTC

   AWS Services are experiencing network connectivity issues in the US-EAST-1 region. While there are early signs of recovery, multiple Cypress Cloud services continue to experience outages and we are actively pursuing parallel approaches to restore capacity.

6. identified 2025-10-20 14:55 UTC

   We have confirmed Test Recordings to Cypress Cloud are operating normally. UI Coverage and Accessibility processing for recorded runs are operational, but experiencing elevated latencies due to limited compute capacity. Dashboard continues to experience a major outage and we are...

7. identified 2025-10-20 15:50 UTC

   The ongoing AWS outage in US-EAST-1 region have impacted several services that we rely on, especially around message routing and cluster provisioning. We continue to see an outage with our Dashboard. Application quality services are operational, but experiencing significant...

8. identified 2025-10-20 15:52 UTC

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

9. identified 2025-10-20 16:14 UTC

   We have some initial mitigation in place for the Cypress Cloud UI. We are still experiencing degraded service and underlying outages; we are continuing to take mitigation steps.

10. identified 2025-10-20 18:31 UTC

    Some of the key bottlenecks in our recovery process on the AWS side of the infrastructure are beginning to show significant improvement. We have tightened some volumes in order to help with recovery throughput, which results in intermittency with the affected services. In other...

11. identified 2025-10-20 19:43 UTC

    We are continuing to onramp additional infrastructure; however, we are not yet at our default levels of activity in all places. Upgrading to `monitoring` to communicate the improvement. Note that applicaiton quality services are still significantly lagging other services, but we...

12. monitoring 2025-10-20 20:52 UTC

    Services have reached normal operational levels. We are still seeing slowness in the same services cited as still-recovering in the broader aws outage (e.g., lambda and compute provisioning). Some Cypress Cloud functions are working through backlogs and remain lagged (they are...

13. resolved 2025-10-20 21:40 UTC

    We are observing normal operations and performance, and mitigations that put into effect earlier have served their purposes and are now unnecessary and thusly rolled off.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-14 12:17 UTC

   We are currently investigating this issue.

2. identified 2025-10-14 12:35 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-10-14 14:23 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-10-14 14:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Upstream Service Provider

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. monitoring 2025-10-09 15:10 UTC

   GitHub is currently having issues with many services: https://www.githubstatus.com/

2. resolved 2025-10-09 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-28 12:07 UTC

   We are currently investigating this issue.

2. investigating 2025-08-28 13:00 UTC

   We are still investigating the issue and will provide updates.

3. monitoring 2025-08-28 13:09 UTC

   Impact from the detected issue with the Cypress Cloud has been mitigated. Engineers are monitoring for stability.

4. resolved 2025-08-28 13:51 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-21 18:21 UTC

   We are currently investigating this issue.

2. identified 2025-08-21 19:13 UTC

   We have identified this issue as being related to an upstream service provider incident. We will continue to monitor and provide updates here until the upstream incident is resolved.

3. monitoring 2025-08-21 19:25 UTC

   We have seen significant upstream improvement and will continue to monitor.

4. resolved 2025-08-21 19:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-08 13:33 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. monitoring 2025-08-08 14:26 UTC

   Impact from the detected issue with the Cypress Cloud has been mitigated. Engineers are monitoring for stability.

3. resolved 2025-08-08 15:34 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Upstream Service Provider

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2025-08-05 16:03 UTC

   We are seeing impacts to GitHub integrations from the ongoing GitHub incident. See https://www.githubstatus.com/ for more information. We will continue to monitor the situation and update here if conditions change.

2. monitoring 2025-08-05 16:21 UTC

   GitHub has resolved their issue. We will continue to monitor, and resolve this incident once we've seen our GitHub integrations stabilize

3. resolved 2025-08-05 16:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Test Recording

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-05 10:06 UTC

   We are currently investigating this issue.

2. investigating 2025-08-05 10:28 UTC

   We are continuing to investigate this issue.

3. resolved 2025-08-05 12:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Test Recording, Analytics, Accessibility, UI Coverage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-05 23:42 UTC

   We are currently investigating this issue.

2. identified 2025-07-05 23:48 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-07-05 23:56 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-07-06 00:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Upstream Service Provider

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-06-17 19:53 UTC

   Waiting for Github issues to be resolved

2. resolved 2025-06-17 20:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Download, Upstream Service Provider, Accessibility, UI Coverage

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-06-12 19:18 UTC

   The ongoing NPM incident is impacting our Results API

2. identified 2025-06-12 20:08 UTC

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

3. identified 2025-06-12 20:10 UTC

   We are also monitoring an outage at Cloudflare which could impact Cypress Cloud

4. monitoring 2025-06-12 21:01 UTC

   Upstream provider services are coming back online, we will continue to monitor Cypress service health

5. resolved 2025-06-12 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Test Recording, Authentication, Integrations, Analytics, Accessibility, UI Coverage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-02 23:26 UTC

   We are currently investigating this issue.

2. identified 2025-06-02 23:26 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-06-03 02:16 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-06-03 02:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2025-05-26 08:56 UTC

   A service degradation has been reported by GitHub. Cypress is monitoring those services for resolution.

2. resolved 2025-05-26 10:33 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-07 12:20 UTC

   We are currently investigating an issue with cloud performance.

2. monitoring 2025-05-07 14:07 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-05-07 14:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-03-27 17:30 UTC

   Between 1:35 PM EST and 1:52 PM EST, the database experienced performance issues. At 1:46 PM EST, we began mitigation procedures, and service was restored at 1:52 PM.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-21 00:02 UTC

   We are currently investigating this issue.

2. monitoring 2025-03-21 00:19 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-03-21 00:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud, Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-05 15:54 UTC

   We are currently investigating this issue.

2. resolved 2025-03-05 17:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-30 13:39 UTC

   We've identified an issue in viewing Test Replays that is affecting some customers. We are actively investigating.

2. monitoring 2025-01-30 14:02 UTC

   We have identified the issue and implemented a fix. Monitoring for results.

3. resolved 2025-01-30 14:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-27 22:51 UTC

   We have identified an issue that is preventing some Slack and Microsoft Teams messages from being delivered. Engineers are engaged and troubleshooting.

2. resolved 2025-01-28 02:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-12-06 15:20 UTC

   We have detected performance degradation in Cypress Cloud. Engineers are engaged and troubleshooting.

2. monitoring 2024-12-06 15:53 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-12-06 20:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Accessibility, UI Coverage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-12 19:22 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. investigating 2024-11-12 19:27 UTC

   We are currently investigating issues with Accessibility and UI Coverage reports

3. identified 2024-11-12 19:35 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2024-11-12 19:38 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2024-11-12 20:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-31 17:26 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. resolved 2024-10-31 18:05 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-10-28 06:00 UTC

   Starting from 2:37EST to 5:13EST We had an incident that has since been resolved that affected runs during this period. The issue has been resolved; however, screenshots, videos, and Test Replays will not be available for runs during this time period.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Accessibility, UI Coverage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-24 18:20 UTC

   We have detected a degradation in a small number of Accessibility and UI Coverage runs in Cypress Cloud. Engineers are engaged and troubleshooting.

2. monitoring 2024-09-24 20:20 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-09-24 21:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-24 09:31 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. identified 2024-09-24 09:42 UTC

   The issue has been identified

3. resolved 2024-09-24 09:55 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-16 16:16 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. resolved 2024-09-16 16:19 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-04 21:47 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. monitoring 2024-09-04 22:00 UTC

   Impact from the detected issue with the Cypress Cloud has been mitigated. Engineers are monitoring for stability.

3. resolved 2024-09-04 22:13 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-30 13:01 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. monitoring 2024-08-30 13:28 UTC

   Impact from the detected issue with the Cypress Cloud has been mitigated. Engineers are monitoring for stability.

3. resolved 2024-08-30 13:43 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-30 13:01 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. resolved 2024-08-30 14:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-30 16:01 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. investigating 2024-07-30 16:10 UTC

   We've are investigating an issue with the Cypress Cloud's Accessibility & UI Coverage service processing

3. monitoring 2024-07-30 17:26 UTC

   Impact from the detected issue with the Cypress Cloud has been mitigated. Engineers are monitoring for stability.

4. resolved 2024-07-30 18:16 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-29 15:35 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. identified 2024-07-29 16:14 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-07-29 17:59 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-07-29 19:00 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-17 17:11 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. monitoring 2024-07-17 17:21 UTC

   Impact from the detected issue with the Cypress Cloud has been mitigated. Engineers are monitoring for stability.

3. resolved 2024-07-17 17:38 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Affected: Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-18 19:38 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. resolved 2024-06-18 23:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-04 18:28 UTC

   An issue has been detected with the Cypress Cloud service. Engineering resources are engaged and troubleshooting.

2. identified 2024-06-04 22:07 UTC

   We have identified an issue relating to github comment updates. There is no observed impact with Cypress runs. The team is working on a fix.

3. resolved 2024-06-05 00:06 UTC

   The detected issue with the Cypress Cloud service has been successfully resolved.

Excerpts are shortened. Read the full incident on Cypress Cloud's status page.