CHYP.ai · ORBIT // Cloudy_Day Security Suite

Outages · Developer tools

Operational Harness outage dossier

harness.io · Official status page (Statuspage-compatible JSON)

Official status now

Operational Operational

checked 0 min ago How we score status

All Systems Operational

Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗

ORBIT score

100

Clear skies: official status: Operational

At a glance

37official incidents, 90 d
100%of our checks clean (9)
2.6 hmedian time to resolve
0visitor reports, 24 h
0reports, last 15 min
0status changes recorded

90-day timeline (1 day tracked)

2026-08-24: no data yet2026-08-25: no data yet2026-08-26: no data yet2026-08-27: no data yet2026-08-28: no data yet2026-08-29: no data yet2026-08-30: no data yet2026-08-31: no data yet2026-09-01: no data yet2026-09-02: no data yet2026-09-03: no data yet2026-09-04: no data yet2026-09-05: no data yet2026-09-06: no data yet2026-09-07: no data yet2026-09-08: no data yet2026-09-09: no data yet2026-09-10: no data yet2026-09-11: no data yet2026-09-12: no data yet2026-09-13: no data yet2026-09-14: no data yet2026-09-15: no data yet2026-09-16: no data yet2026-09-17: no data yet2026-09-18: no data yet2026-09-19: no data yet2026-09-20: no data yet2026-09-21: no data yet2026-09-22: no data yet2026-09-23: no data yet2026-09-24: no data yet2026-09-25: no data yet2026-09-26: no data yet2026-09-27: no data yet2026-09-28: no data yet2026-09-29: no data yet2026-09-30: no data yet2026-10-01: no data yet2026-10-02: no data yet2026-10-03: no data yet2026-10-04: no data yet2026-10-05: no data yet2026-10-06: no data yet2026-10-07: no data yet2026-10-08: no data yet2026-10-09: no data yet2026-10-10: no data yet2026-10-11: no data yet2026-10-12: no data yet2026-10-13: no data yet2026-10-14: no data yet2026-10-15: no data yet2026-10-16: no data yet2026-10-17: no data yet2026-10-18: no data yet2026-10-19: no data yet2026-10-20: no data yet2026-10-21: no data yet2026-10-22: no data yet2026-10-23: no data yet2026-10-24: no data yet2026-10-25: no data yet2026-10-26: no data yet2026-10-27: no data yet2026-10-28: no data yet2026-10-29: no data yet2026-10-30: no data yet2026-10-31: no data yet2026-11-01: no data yet2026-11-02: no data yet2026-11-03: no data yet2026-11-04: no data yet2026-11-05: no data yet2026-11-06: no data yet2026-11-07: no data yet2026-11-08: no data yet2026-11-09: no data yet2026-11-10: no data yet2026-11-11: no data yet2026-11-12: no data yet2026-11-13: no data yet2026-11-14: no data yet2026-11-15: no data yet2026-11-16: no data yet2026-11-17: no data yet2026-11-18: no data yet2026-11-19: no data yet2026-11-20: no data yet2026-11-21: 9 checks, 0 with an official incident (worst: none)90 days agotoday

Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.

Official incidents per week

3 incident(s), week ending 2026-08-2931 incident(s), week ending 2026-09-0512 incident(s), week ending 2026-09-1227 incident(s), week ending 2026-09-1974 incident(s), week ending 2026-09-2644 incident(s), week ending 2026-10-0344 incident(s), week ending 2026-10-1044 incident(s), week ending 2026-10-1741 incident(s), week ending 2026-10-2412 incident(s), week ending 2026-10-3122 incident(s), week ending 2026-11-0722 incident(s), week ending 2026-11-1421 incident(s), week ending 2026-11-21113 weeks agothis weekmax 7/week

Impact mix, 90 d

2 critical2 major26 minor7 none37
  • 26 minor
  • 7 none
  • 2 major
  • 2 critical

Visitor reports, last 24 h

24 h agonow · peak 1/15 min

Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.

Incident history

  1. → resolved · lasted 9.1 hCustomers unable to log into Prod 2minor resolved · Platform · official notice ↗ · replay & discuss
  2. → resolved · lasted 46 minPipeline slowness on prod3minor postmortem · Continuous Delivery - Next Generation (CDNG) · official notice ↗ · replay & discuss
  3. → resolved · lasted 5.4 hDelegate version 26.11.90407/26.10.90316 missing client toolsminor postmortem · Continuous Delivery - Next Generation (CDNG), Continuous Delivery - Next Generation (CDNG), Continuous Delivery - Next Generation (CDNG), Continuous Delivery - Next Generation (CDNG) · official notice ↗ · replay & discuss
  4. → resolved · lasted 6.2 hapidocs.harness.io not responding to HTTPS requestsnone postmortem · official notice ↗ · replay & discuss
  5. → resolved · lasted 15.4 hdeveloper.harness.io not responding to HTTPS requestsnone postmortem · official notice ↗ · replay & discuss
  6. → resolved · lasted Intermittent CI Pipeline using VM Runner slowness and errorsnone postmortem · official notice ↗ · replay & discuss
  7. → resolved · lasted 2.5 hWe are currently seeing delegate selection issue for VM infra executionsminor postmortem · Continuous Integration Enterprise(CIE) - Self Hosted Runners · official notice ↗ · replay & discuss
  8. → resolved · lasted 35 minDegraded performance on prod4minor postmortem · Continuous Delivery - Next Generation (CDNG), Continuous Integration Enterprise(CIE) - Self Hosted Runners, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds · official notice ↗ · replay & discuss
  9. → resolved · lasted Intermittent failures in Policy step evaluations on Prod 7minor postmortem · official notice ↗ · replay & discuss
  10. → resolved · lasted 11 minDegraded performance in UI execution graph in prod3minor postmortem · Continuous Delivery - Next Generation (CDNG) · official notice ↗ · replay & discuss
  11. → resolved · lasted 3.4 hProd1: Intermittent issue with IACM stages in some pipelinesminor postmortem · Infrastructure as Code Management (IaCM) · official notice ↗ · replay & discuss
  12. → resolved · lasted Harness CI Cloud build issues when accessing Maven Centralminor postmortem · Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Mac Cloud Builds, Continuous Integration Enterprise(CIE) - Windows Cloud Builds · official notice ↗ · replay & discuss
  13. → resolved · lasted 58 minProd1: IACM Stages are failing and pipelines are intermittently failing to start.major postmortem · Infrastructure as Code Management (IaCM) · official notice ↗ · replay & discuss
  14. → resolved · lasted 2.7 hProd2 Pipelines with verify step failing intermittentlynone postmortem · Continuous Delivery - Next Generation (CDNG) · official notice ↗ · replay & discuss
  15. → resolved · lasted 4.4 hSingle Customer: IaCM pipeline executions failing intermittently in Prod 1minor postmortem · Infrastructure as Code Management (IaCM) · official notice ↗ · replay & discuss
  16. → resolved · lasted 2.6 hHosted MCP Logins W/ SSO Failingminor postmortem · Platform, Platform, Platform, Platform · official notice ↗ · replay & discuss
  17. → resolved · lasted 2.2 daysSSO login failures for the published Harness Okta applicationnone postmortem · Platform, Platform · official notice ↗ · replay & discuss
  18. → resolved · lasted 3.3 hCI Linux Cloud VM Networking issues - intermittentminor postmortem · Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds · official notice ↗ · replay & discuss
  19. → resolved · lasted 4.1 hProd2: CV is failing with errors for all customersminor postmortem · Continuous Delivery - Next Generation (CDNG) · official notice ↗ · replay & discuss
  20. → resolved · lasted File Store Expression Degraded : Returning Nullminor postmortem · official notice ↗ · replay & discuss
  21. → resolved · lasted 44.9 hPalo Alto Networks Firewall Blocking Harness Connectionsnone postmortem · Platform, Platform, Platform, Platform · official notice ↗ · replay & discuss
  22. → resolved · lasted 2 hInvestigating CI Pipeline Delaysminor postmortem · Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds, Continuous Integration Enterprise(CIE) - Linux Cloud Builds · official notice ↗ · replay & discuss
  23. → resolved · lasted 19 minDashboard export and download APIs are currently facing issue.minor postmortem · Custom Dashboards, Custom Dashboards · official notice ↗ · replay & discuss
  24. → resolved · lasted 1.9 hDashboard aggregator experiencing timeouts across prod2 since 15:04 UTC (Sept 21)minor postmortem · Custom Dashboards · official notice ↗ · replay & discuss
  25. → resolved · lasted 14.5 hProd1: Single Customer Issue : OPA evaluations are failing for a specific workspaceminor postmortem · Infrastructure as Code Management (IaCM) · official notice ↗ · replay & discuss

All 37 incidents →

Related services

"Runs on" links are inferred from public information and may be outdated.

How we score status

  1. Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
  2. Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
  3. Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
  4. Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
  5. Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.

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.

Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.

Where to next