Is Harness Down?

No — Harness is up

Reachable from all 8 checked regions

Average response time: 1957ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.harness.io

Harness uptime

100%

Last 7 days

99.86%

Last 30 days

99.86%

Last 90 days

1829ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 24 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

10-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

1799ms

DNS 161ms TCP 138ms TLS 138ms TTFB 1245ms

arn

2145ms

DNS 68ms TCP 176ms TLS 176ms TTFB 1443ms

bom

3157ms

DNS 159ms TCP 260ms TLS 261ms TTFB 2087ms

cdg

1762ms

DNS 48ms TCP 136ms TLS 136ms TTFB 1218ms

dfw

1160ms

DNS 281ms TCP 52ms TLS 53ms TTFB 949ms

ewr

1246ms

DNS 153ms TCP 66ms TLS 66ms TTFB 984ms

fra

1946ms

DNS 74ms TCP 142ms TLS 142ms TTFB 1379ms

gru

2443ms

DNS 183ms TCP 177ms TLS 177ms TTFB 1912ms

What Harness does

Harness is a software delivery platform covering continuous integration, continuous delivery, feature flags, cloud cost management and security testing. Its SaaS control plane assigns work to Delegates, which are services customers run inside their own network or VPC. Engineering teams depend on it to build, approve and ship changes to production, so an incident stops releases rather than running software.

What an outage looks like

Pipelines queue without ever starting, and delegates report a Not Connected state in the Harness UI. app.harness.io fails to load or loops on sign-in. Because Harness splits its estate into separate production clusters, teams on one cluster can be completely unaffected while another is broken, which makes reports from other companies an unreliable guide to your own situation.

What to do about it

Open status.harness.io and find your own cluster: components are grouped under Prod 1, Prod 2, Prod 3, Prod 4 and Prod Eu 1, and your account URL identifies which one you are on. Check the specific module too, since Continuous Delivery, Continuous Integration, Feature Flags, Code Repository and Artifact Registry are reported independently. Hold releases rather than retrying pipelines, which deepens the queue.

Is it down for everyone, or just you?

If this page says Harness is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Harness outage FAQ

Which Harness cluster am I on?

Your account URL identifies it. Harness runs several separate production clusters, listed on its status page as Prod 1, Prod 2, Prod 3, Prod 4 and Prod Eu 1, each with its own component tree. An incident on one cluster does not affect accounts on another, so checking the wrong group is the most common way to misread the page during an incident.

Do my Delegates keep running if Harness is unreachable?

The Delegate itself runs in your infrastructure, not in Harness cloud. Harness describes it as a service you run in your local network or VPC, connecting outbound to Harness Manager over HTTPS or WSS. When that connection drops, Harness stops receiving delegate heartbeats and shows the delegate as Not Connected, so new work cannot be assigned to it.

Is it my Delegate or is it Harness?

Check the status page for your cluster first. A delegate showing Not Connected is consistent with both a Harness-side incident and a problem on your own network, since the connection is outbound from your VPC. If the cluster is reported healthy and only your delegate is disconnected, the fault is more likely local: firewall changes and expired outbound rules are the usual causes.

Are Feature Flags affected when pipelines are down?

Not automatically. Harness reports Feature Flags and Feature Management and Experimentation as their own components, with the latter broken into SDK API, Admin API, Streaming service and Management Console. Flag evaluation in your application runs through the SDK path, which is separate from the delivery pipeline, so a CD incident does not by itself change flag behaviour in production.

Does a Harness outage roll back a deployment in progress?

Harness does not publish that behaviour on its status page, so treat the state of any in-flight deployment as unknown rather than assuming either outcome. Verify what actually reached your environment directly, using your own cluster or cloud console rather than the Harness UI, before re-running a pipeline that may have partially applied.

How we measure this

We request Harness's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Harness publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Harness goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required