Live  /  Harness  /  Incident

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

Harness · split.ioResolved2026-11-06 07:13 UTC
Public — what happened

Summary

Harness said its API documentation website, apidocs.harness.io, was not responding to secure web (HTTPS) requests. The company began investigating at 00:59 UTC on 2026-11-06 and reported at 01:16 UTC that it had identified the issue and was putting a fix in place, though it did not describe what the cause was. The incident was marked resolved at 07:13 UTC the same day.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Harness against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Harness: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Harness report →

More from Harness

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Harness status & history page.

Related: Harness status & history. SquidGrid is not affiliated with Harness.