Harness: Some failures on http://config.ff.harness.io/client/auth end point.
Timeline of updates
- resolved
At 1:47am GMT, automated synthetic checks simulating SDK traffic for the Feature Flags service began failing. Some requests to http://config.ff.harness.io/client/auth (opens in new tab) received 502 responses. Subsequent investigation revealed that one of the service dependencies and partially degraded due to a missing container image in Google Artifact Registry (GAR). During a routine deployment, Kubernetes rescheduled some pods onto new nodes that did not have the image cached locally. To mitigate the missing image was restored to Google Artifact Registry.
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: minor) posted by Harness, started 2025-10-29 00:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Some failures on http://config.ff.harness.io/client/auth end point.
- Vendor
- Harness
- Date
- URL
- https://rewindex.com/company/harness/incidents/2jkj4ryrktd8
Harness profileRecent Harness incidentsAll outages on October 29, 2025Harness in October 2025MarkdownJSON