Cypress Outage History

31 incidents recorded over the last 365 days, 20 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Cypress status99.18% uptime history

Every Recorded Cypress Incident

Cypress incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 17, 2026Github OutageThis incident has been resolved.1h 15mResolved
Aug 13, 2026Enterprise Reporting degradationThis incident has been resolved.43 minResolved
Aug 6, 2026Enterprise Reporting Data Extract API experiencing issuesThis incident has been resolved.1h 18mResolved
Aug 5, 2026Cypress Cloud incidentThis incident has been resolved.1h 1mResolved
Jul 17, 2026Cypress Cloud incidentThis incident has been resolved.2h 26mResolved
Jul 16, 2026Cypress Cloud incidentThis incident has been resolved.1h 11mResolved
Jul 2, 2026Database maintenanceThe scheduled maintenance has been completed.30 minScheduled
Jun 29, 2026Test Replay rendering errorsThis incident has been resolved.1h 24mResolved
Jun 25, 2026Performance DegradationThis incident is resolved4h 58mResolved
May 7, 2026Automated emails are not being sentThis incident has been resolved.1h 37mResolved
May 6, 2026Slow App responseThis incident has been resolved.33 minResolved
Apr 27, 2026Database maintenanceThe scheduled maintenance has been completed.1h 30mScheduled
Apr 24, 2026Database maintenanceThe scheduled maintenance has been completed.8h 0mScheduled
Apr 23, 2026Database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Apr 14, 2026Billing MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Mar 25, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Mar 19, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 21, 2026Extended Database MaintenanceThe scheduled maintenance has been completed.12h 0mScheduled
Feb 14, 2026Database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jan 8, 2026Test Replay Processing DelaysThis incident has been resolved.25 minResolved
Jan 8, 2026Delays in Test Replay availabilityYesterday, 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…-1123 minResolved
Dec 18, 2025Delays in Test Replay availabilityYesterday, 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…-1416 minResolved
Nov 18, 2025Experiencing Upstream Provider IssuesThis incident has been resolved.1h 22mResolved
Nov 18, 2025Services issues due to upstream networking outagesThis incident has been resolved.2h 8mResolved
Nov 18, 2025Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Nov 12, 2025Elevated response timesThe issue was identified and related changes were rolled back. Systems have returned to normal response times.27 minResolved
Oct 20, 2025Cypress Cloud OutageWe 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.11h 54mResolved
Oct 14, 2025Cloud Performance DegradationThis incident has been resolved.2h 15mResolved
Oct 9, 2025GitHub IssuesThis incident has been resolved.1h 30mResolved
Oct 9, 2025Database maintenanceThe scheduled maintenance has been completed.30 minScheduled
Aug 28, 2025Slow API response timesThe detected issue with the Cypress Cloud service has been successfully resolved.1h 44mResolved

How to Read This Cypress Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Cypress acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Cypress outage in this window ran 12h, against a mean recovery of 2h 20m. If you depend on Cypress in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.