rewindex

ChangesHarnessdeveloper.harness.io not responding to HTTPS requests

Harness: Incident updated: developer.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: monitoring
After: resolved
AddedResolved time#2
Before: not present
After: 2026-11-04 02:33 UTC
AddedUpdateresolved#3
Before: not present
After: The provider has resolved the issue and service is restored.

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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

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

History of this incident

Wednesday, November 4

1 incident change

Tuesday, November 3

1 rewrite, 3 incident changes

Cite this

Incident updated: developer.harness.io not responding to HTTPS requests on Harness’s status page, changed 2026-11-04 02:43 UTC (change 5 of 5).

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

All Harness changesHarness profileMarkdownJSON