- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Upstream Service Provider
- Down Index
- 27of 100
What to do
Check whether you use Cypress Cloud Upstream Service Provider. 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 32m it lasted.
Anything that failed between 2025-08-05 16:03 UTC and 2025-08-05 16:34 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 3
- identified
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.
provider
- monitoring
GitHub has resolved their issue. We will continue to monitor, and resolve this incident once we've seen our GitHub integrations stabilize
provider
- resolved
This incident has been resolved.
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-8922478fd9
Is Cypress Cloud still down?
No, this incident was resolved 2025-08-05 16:34 UTC. For Cypress Cloud's live state, see https://down.guide/cypress-cloud.
How long did it last?
32m, from 2025-08-05 16:03 UTC to 2025-08-05 16:34 UTC, by the times Cypress Cloud posted.
What was affected?
Cypress Cloud named Upstream Service Provider.
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.