Live / Harness / Incident
Harness: Palo Alto Networks Firewall Blocking Harness Connections
Harness · split.ioResolved2026-09-25 17:10 UTC
Public — what happened
Summary
Harness reported that some customers using Palo Alto Networks firewalls found their connections to Harness being blocked, beginning on September 23, 2026 at 20:17 UTC. According to Harness, after talking with Palo Alto Networks it learned that the firewall vendor had moved app.harness.io from its Computer and Internet Info category into an AI Platform Service category on that date, a change Palo Alto Networks had announced to its customers in August. Harness explained that whether access is affected depends on each customer's own firewall policy settings, and it advised affected customers to raise the matter with their internal network teams and Palo Alto Networks. The incident was marked resolved on September 25, 2026 at 17:10.
Timeline
- Started — 2026-09-23 20:17 UTC
- Resolved — 2026-09-25 17:10 UTC · 44h 54m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Harness against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Harness: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Harness report →
More from Harness
Covered in The Squid’s Ink, Week 40, 2026, our weekly internet health report.