Harness

harness.io (opens in new tab)Status page (opens in new tab)

Status page says: Operational since Oct 19
Last 90 days: 42 incidents, 8 major or critical
Rewrites caught: None so far
Next deprecation: None announced

Harness incidents per day, last 90 days

Select a day to jump to its incidents below.

How Harness reports incidents

Compared with the 152 vendors that have enough incidents to compare. Each tick is one vendor; lower is better on every line.

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

First posted only after it was over

4% 2 of the 50 incidents we have in full detail

The first update already said resolved. Typical vendor: 6%.

Harness: around the middle.

Time to resolve

2 h 30 min median; 9 in 10 within 18 h 28 min

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Harness: around the middle.

Major or critical incidents

2.5 a month 30 in the last 365 days

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Harness: higher than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Dependencies

What Harness relies on and who relies on Harness, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Harness depends on

Provider	Evidence	Signal
Google Cloud (us-west1)	blamed in 4 incidents; named as hosting in 3; together in 2 outage events “…tion, pipeline orchestration, and Feature Management & Experimentation were all affected. Google Cloud Platform experienced a multi-product incident in the us-west1 region affecting Bigtable, Compute…” incident	Strong
GitHub	blamed in 2 incidents “…[Notification] Harness Pipeline executions may be failing due to an ongoing GitHub outage This incident has been resolved.…” incident	Strong
Cloudflare	blamed in 1 incident; together in 2 outage events “…Harness Impacted due to ongoing Cloudflare Incident We can confirm normal operation. Get Ship Done! We will continue to monitor and ensure stability.…” incident	Likely
Tinybird	blamed in 1 incident “…sions data exports on Jul 2, 2026. This issue stemmed from performance degradation within Tinybird's infrastructure, affecting query execution crucial to our export pipeline. Root Cause The core i…” incident	Likely
Timescale	blamed in 1 incident “…Dashboards not loading due to Timescale DB Issue in Prod-1 Cluster This incident has been resolved.…” incident	Likely
AWS	named as hosting in 1; integration affected in 1; together in 1 outage event “…Autostopping service degraded in AWS (Middle East South 1) This incident has been resolved.…” incident	Likely
Microsoft Azure	integration affected in 2 “…Azure connectors failing for some customers This incident has been resolved.…” incident	Likely
Vercel	integration affected in 1 “…Vercel Integration for FME is having delays to synchronize changes This incident has been resolved.…” incident	Weak
Jira	integration affected in 1 “…FME UI errors on creating/updating Flags for subset of customers who have Jira integration. This incident has been resolved.…” incident	Weak
Okta	integration affected in 1 “…Hosted MCP Logins W/ SSO Failing ## Okta Application SP-Initiated SSO Login Failures ‌ # Summary ‌ Between October 5, 2026, 18:18 UTC and October 6, 2026, 00:26 UTC, some Harness customers were unable…” incident	Weak
Zendesk	integration affected in 1 “…tomers in prod1 are not able to file zendesk tickets. Customers cannot create tickets via Zendesk from the module view. But we can create via the Unified view.…” incident	Weak

Runs in (named in its incidents): Google Cloud us-west1 (4).

Outage events: Cloudflare, Dec 5, 2025 (timing), Google Cloud, Jun 12, 2025 (timing), AWS, Sep 28, 2023 (timing), Cloudflare, Jun 21, 2022, Google Cloud, Nov 16, 2021 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.