Harness: Git API rate limit errors
Timeline of updates
- resolved
Two enterprise customers experienced Git API rate limit errors when using remote entities backed by Git repositories on prod1 environment.This prevented loading of services, environments, and other entities stored in Git, and blocked pipeline executions that depended on the remote YAML.
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 2026-02-18 15:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Git API rate limit errors
- Vendor
- Harness
- Date
- URL
- https://rewindex.com/company/harness/incidents/b688y7q8chtm
Harness profileRecent Harness incidentsAll outages on February 18, 2026Harness in February 2026MarkdownJSON