rewindex

ChangesHarnessapidocs.harness.io not responding to HTTPS requests

Harness: Incident updated: apidocs.harness.io not responding to HTTPS requests

Incident updateNormal progress (rule, 100%)Changed status.harness.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Harness removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: identified
AddedUpdateidentified#2
Before: not present
After: The issue has been identified and a fix is being implemented.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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.

Rewindex captured this after the last checkpoint; the next run () commits it.

History of this incident

TodayFriday, November 6Fri, Nov 6

2 incident changes

Cite this

Incident updated: apidocs.harness.io not responding to HTTPS requests on Harness’s status page, changed 2026-11-06 01:24 UTC (change 1 of 2).

Title
Incident updated: apidocs.harness.io not responding to HTTPS requests
Vendor
Harness
Date
URL
https://rewindex.com/change/r50b03f29c139de

All Harness changesHarness profileMarkdownJSON