Harness: Feature Flag SDK APIs failing intermittently with 502 error code
Timeline of updates
- resolved
All services across all environments are now working as intended. After additional debugging, we have found that a demon for deprecated security configurations from a third party vendor in our production Google Cloud infrastructure may have been a primary contributing cause to the issue. The demon has incorrectly added ip table entries inside the node that is running the FF service causing packet drops. Upon isolating this demon and its corresponding configurations, alongside other changes, we see that all functionality is working as expected over a prolonged period of time, and we have been able to reproduce the restored services across all environments. We will monitor services for reliability while we continue working on a deeper root cause analysis and remediation plan in the coming days.
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: major) posted by Harness, started 2023-01-05 07:43 UTC, resolved after 17 h, 1 update(s).
- Title
- Feature Flag SDK APIs failing intermittently with 502 error code
- Vendor
- Harness
- Date
- URL
- https://rewindex.com/company/harness/incidents/6qg5sy3h8lcz
Harness profileRecent Harness incidentsAll outages on January 5, 2023Harness in January 2023MarkdownJSON