Operational Harness status
harness.io · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Harness problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Platform
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 58 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: postmortem on “Palo Alto Networks Firewall Blocking Harness Connections”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Harness' own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “postmortem”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Harness. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Harness, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Harness may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Harness. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Palo Alto Networks Firewall Blocking Harness Connections
none postmortem · started · resolved
4 updates
- investigating
We are currently investigating connectivity issues affecting customers whose environments are protected by Palo Alto Networks firewalls. These firewalls are blocking connections to Harness APIs, which may result in: - Failed pipeline executions - Inability to deploy applications - Intermittent timeouts when accessing Harness platform features - Integration failures with third-party tools - Delegate connectivity with Harness platform This issue is not caused by a Harness service outage, but rather by firewall rules on your network side. We are advising customers to make an exception for our DNS endpoints.
- monitoring
Mitigation Available: Harness Traffic Blocked by Network Security Policy We have identified an issue where some customers may be unable to access Harness because Harness traffic is being categorized as “AI-Platform” by Palo Alto network security controls and subsequently blocked by the customer's firewall/INET policy. If you are experiencing this issue: Please contact your organization's Network/Firewall/CyberSecurity team and request that the required Harness traffic be allowed through your Palo Alto firewall policy. As a mitigation, customers can allow the “AI-Platform” URL category for the required Harness endpoints, or add the affected Harness domains/FQDNs to their organization's approved/allow list, in accordance with their security policies. After the firewall policy is updated, access to Harness should be restored. Important: The firewall policy is managed by the customer's netwo
- resolved
After consultation with Palo Alto Networks, we can confirm that on Sept 23rd 2026, app.harness.io was categorized as an AI Platform Service by the Palo Alto Networks Team. Palo Alto Networks sent a notice to customers in August about the reclassification. This change may place AI Platform Service under a different policy than app.harness.io's previous ruleset categorization, Computer and Internet Info. The policy applied is dependent on customer settings. Harness Customers should discuss this categorization and the alerts with their internal network team and Palo Alto Networks.
- postmortem
.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.