Vendor record
Cypress Cloud
Checked
Front door check counts and Cypress Cloud’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against Cypress Cloud in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Cypress Cloud product, region or your app worked.
How we count front door checksCypress Cloud says
Incident posts from Cypress Cloud’s status page, with its titles, impact levels and times. They say what Cypress Cloud chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
10
incidents Cypress Cloud posted, last 180 days
Median recorded duration: 1h 25m. From 10 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Github Outage
MajorCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(5h 25m)
Enterprise Reporting degradation
MajorCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(51m)
Enterprise Reporting Data Extract API experiencing issues
MajorCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(1h 25m)
Cypress Cloud incident
Not specifiedCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(1h 4m)
Cypress Cloud incident
MajorCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(2h 29m)
5 older records
Cypress Cloud incident
CriticalCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(1h 19m)
Test Replay rendering errors
MinorCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(1h 28m)
Performance Degradation
MinorCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(5h 7m)
Automated emails are not being sent
MajorCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(1h 43m)
Slow App response
MajorCypress Cloud’s postStarted, per Cypress Cloud
Closed in our record(42m)
Your code, your dependencies
See which of your code paths call Cypress Cloud
Connect GitHub or GitLab to find where your public or private repository uses Cypress Cloud. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Cypress Cloud status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Cypress Cloud currently down?
Cypress Cloud's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Cypress Cloud last have an outage?
The most recent closed incident record began 60 days ago and spans 5h 25m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Cypress Cloud?
No. CheckUpstream does not run front door checks against Cypress Cloud. The incident history on this page is what Cypress Cloud reported, not a measure of how often it was available.
How do I monitor Cypress Cloud in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Cypress Cloud?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.