rewindex

CompaniesHarnessIncidents

Harness: Users from Prod2 cluster faced internal error after logging in

MajorStatus: resolvedStarted Resolved (5 min)1 updatestatus.harness.io (opens in new tab)

Timeline of updates

  1. resolved

    The issue was resolved once we did the rollback of the most recent deployment.

From Harness’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.harness.io (opens in new tab).

Cite this

Status incident (vendor impact label: major) posted by Harness, started 2024-01-08 07:23 UTC, resolved after 5 min, 1 update(s).

Title
Users from Prod2 cluster faced internal error after logging in
Vendor
Harness
Date
URL
https://rewindex.com/company/harness/incidents/1sqh0pchkz8l

Harness profileRecent Harness incidentsAll outages on January 8, 2024Harness in January 2024MarkdownJSON