rewindex

CompaniesHarnessIncidents

Harness: some deployments are failing get, error with null pointer exception and KMS

CriticalStatus: resolvedStarted Resolved (2.7 h)1 updatestatus.harness.io (opens in new tab)

Timeline of updates

  1. resolved

    The previous reported problem scenarios are confirmed working now.

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: critical) posted by Harness, started 2019-09-10 16:27 UTC, resolved after 2.7 h, 1 update(s).

Title
some deployments are failing get, error with null pointer exception and KMS
Vendor
Harness
Date
URL
https://rewindex.com/company/harness/incidents/yv1l4kb1tv5d

Harness profileRecent Harness incidentsAll outages on September 10, 2019Harness in September 2019MarkdownJSON