- Level
- confirmed
- Worst impact
- Major outage
- Components
- Cloud, Authentication, Billing, Integrations, Analytics, Accessibility, UI Coverage
- Regions
- us, us-east-1
- Down Index
- 53of 100
What to do
Check whether you use Cypress Cloud Cloud, Authentication, Billing, Integrations and 3 more in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 11h 54m it lasted.
Anything that failed between 2025-10-20 09:46 UTC and 2025-10-20 21:40 UTC may need a replay.Subscribe to Cypress Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cypress-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cypress Cloud 13
- investigating
We are currently investigating this issue.
provider
- investigating
AWS Operational Issue affecting multiple services in N. Virginia (https://health.aws.amazon.com/health/status?path=open-issues) identified as root cause
provider
- investigating
AWS services are incrementally recovering; but compute services are still experiencing issues & capacity remains constrained, impacting service restoration.
provider
- identified
Flagging incident as identified; recovery still in progress with resource constraints impacting services restoration
provider
- identified
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.
provider
- identified
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 actively working on resolving the same.
provider
- identified
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 processing delays Services that handle recordings and other critical areas of Cypress Cloud are operating normally. The team continues to attempt mitigation strategies as we work towards recovering remaining services as quickly as we can.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
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.
provider
- identified
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 words, we are still recovering and are not yet at usual activity volume. As more resources are regained, we will be improving throughput into services as well.
provider
- identified
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 are ramping up infrastructure there as well. Recording services and analytics are normal UI is at normal levels of activity + supply Billing and Integrations still have some third party dependencies which are recovering Application quality is significantly lagged
provider
- monitoring
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 noted as degrated). Setting incident status to `monitoring`.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-30be99d654
Is Cypress Cloud still down?
No, this incident was resolved 2025-10-20 21:40 UTC. For Cypress Cloud's live state, see https://down.guide/cypress-cloud.
How long did it last?
11h 54m, from 2025-10-20 09:46 UTC to 2025-10-20 21:40 UTC, by the times Cypress Cloud posted.
What was affected?
Cypress Cloud named Cloud, Authentication, Billing, Integrations and 3 more in us, us-east-1.
What caused it?
Cypress Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cypress Cloud's official status page, https://www.cypressstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.