Live / Harness / Incident
Harness: developer.harness.io not responding to HTTPS requests
Harness · split.ioResolved2026-11-04 02:33 UTC
Public — what happened
Summary
Harness said its developer documentation site, developer.harness.io, was not responding to secure web requests starting at 01:01 UTC on 2026-11-03. One minute later the company said the site was degraded or unavailable and attributed this to a problem at an external hosting provider, which it described as outside Harness's own infrastructure. Harness said it was watching the provider's status and would post an update once service came back. As of the last update the incident was not resolved.
Timeline
- Started — 2026-11-03 01:01 UTC
- Investigating — 2026-11-03 01:01 UTC
- Identified — 2026-11-03 01:02 UTC
- Monitoring — 2026-11-03 03:48 UTC
- Identified — 2026-11-03 11:09 UTC
- Monitoring — 2026-11-03 12:41 UTC
- Resolved — 2026-11-04 02:33 UTC · 25h 32m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.