Operational Greenhouse outage dossier
greenhouse.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
Clear skies: official status: Operational
At a glance
90-day timeline (1 day tracked)
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
Impact mix, 90 d
- 5 major
- 13 minor
- 1 none
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- → resolved · lasted 55 minIssues with Integrationsmajor resolved · Silo 1, Silo 2, Silo 3, Silo 4 · official notice ↗ · replay & discuss
- → resolved · lasted 18.1 hDelayed candidate emailsmajor resolved · Silo 1, Silo 2, Silo 3, Silo 4 · official notice ↗ · replay & discuss
- → resolved · lasted 27 minEmails sent from Greenhouse may not have been logged to the Activity Feedminor resolved · Silo 1, Silo 2, Silo 3, Silo 4 · official notice ↗ · replay & discuss
- → resolved · lasted 3.7 daysOutlook calendar integrations for scheduling experiencing 10-15% error ratesminor resolved · Outlook 365 · official notice ↗ · replay & discuss
- → resolved · lasted 28 minVoice AI: Certain Calls To Open AI Are Failingminor resolved · Greenhouse Voice AI · official notice ↗ · replay & discuss
- → resolved · lasted 3.2 hIssues with Adobe Signminor resolved · Adobe Acrobat Sign · official notice ↗ · replay & discuss
- → resolved · lasted 5.7 hOnboarding UKG Pro Issuesmajor resolved · HRIS Link - UKG · official notice ↗ · replay & discuss
- → resolved · lasted 3.5 hPartial Service Disruptionnone resolved · official notice ↗ · replay & discuss
- → resolved · lasted 7 minPerformance Degradation - Voice AI Interview Evaluationsminor resolved · Greenhouse Voice AI · official notice ↗ · replay & discuss
- → resolved · lasted 2.2 hPerformance Degradation - Voice AI Interview Evaluationsminor resolved · Greenhouse Voice AI · official notice ↗ · replay & discuss
- → resolved · lasted 52 minGreenhouse Report Connector Outageminor resolved · Silo 101, Silo 201 · official notice ↗ · replay & discuss
- → resolved · lasted 2.8 hPartial Service Disruption - Indeed Applicationsminor resolved · Greenhouse Job Boards · official notice ↗ · replay & discuss
- → resolved · lasted 18.1 hDegraded Performance in Job Board Updatesminor resolved · Greenhouse Job Boards · official notice ↗ · replay & discuss
- → resolved · lasted 39 minMyGreenhouse: Job Search unavailablemajor resolved · MyGreenhouse · official notice ↗ · replay & discuss
- → resolved · lasted 2.5 hCandidates are reporting issues with submitting job formsminor resolved · Silo 1, Silo 2, Silo 3, Silo 4 · official notice ↗ · replay & discuss
- → resolved · lasted 47 minUsers reporting Delivery Issues to Outlook email addressesminor resolved · Silo 1, Silo 2, Silo 3, Silo 4 · official notice ↗ · replay & discuss
- → resolved · lasted 14.1 hSecurity codes on job application CAPTCHA failures have temporarily been disabledminor resolved · Greenhouse Job Boards · official notice ↗ · replay & discuss
- → resolved · lasted 2.5 hCandidates may be receiving errors when utilizing scheduling links with buffer linksminor resolved · Silo 1, Silo 2, Silo 3, Silo 4 · official notice ↗ · replay & discuss
- → resolved · lasted 27 minPartial Service Disruptionmajor resolved · Silo 201 · official notice ↗ · replay & discuss
Related services
- no official feedDocusignno official feed→
- no official feedIntercomno official feed→
- no official feedZendeskno official feed→
- no official feedFreshworksno official feed→
- OperationalHubSpotOperational→
- OperationalSalesforceOperational→
- OperationalQuickBooks OnlineOperational→
- Degraded / minor incidentXeroDegraded / minor incident→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- 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.
- 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.
- 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).
- 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.
- 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.
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.
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.