On this page
Is Greenhouse Down? How to Tell and What to Do
Greenhouse is an applicant tracking system (ATS) used by HR and recruiting teams to manage the full hiring lifecycle — from posting jobs and reviewing applications to scheduling interviews, collaborating on scorecards, and sending offer letters. When Greenhouse goes down, candidates can't submit applications, interviewers can't access scorecards, recruiting coordinators can't schedule interviews, and the entire hiring pipeline grinds to a halt.
Statusfield brings reported Greenhouse incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
Follow Greenhouse incidents with your team
Statusfield brings reported status for Greenhouse together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
Common Signs of a Greenhouse Outage
| Symptom | What's likely happening |
|---|---|
| Greenhouse app fails to load or shows a server error | Core application API is down |
| Job application form on your careers page returns an error | Candidate-facing application ingestion is failing |
| Interview schedule links (via Calendly or GH Scheduling) broken | Scheduling integration or Greenhouse calendar sync is down |
| Scorecards won't save after an interview | Scorecard submission API is failing |
| Offer letters can't be generated or sent | Offer management service is degraded |
| Greenhouse notifications and email alerts not arriving | Outbound notification service is down |
| HRIS sync (Workday, BambooHR) not running | Integration/API layer is degraded |
How to Confirm It's Greenhouse, Not You
Before pulling engineering into a debugging session, rule out local issues:
1. Check browser console for Greenhouse API errors
Open Chrome DevTools (F12 → Network tab) and reload Greenhouse. Look for requests to app.greenhouse.io or api.greenhouse.io returning 500, 502, 503, or timeout errors. Failures on those domains confirm the issue is external.
2. Check your public-facing job board
Navigate to your company's Greenhouse-powered careers page (typically boards.greenhouse.io/yourcompany or your embedded job board). If it fails to load or returns an error, the candidate-facing infrastructure is also affected — which means candidates may be failing to apply right now.
3. Test interview scheduling from a candidate link If you have a pending interview scheduling link sent to a candidate, try opening it. A broken scheduling link during a Greenhouse outage is a strong signal that the calendar sync or scheduling service is affected.
4. Test on a second browser or incognito window A corrupted Greenhouse session or a cached broken asset can produce symptoms that look identical to an outage. Open a fresh incognito window, log in, and check whether the same issues persist.
5. Ask a colleague on a different network If a recruiter in a different office or using a different internet connection sees the same problem, you've effectively ruled out anything local to your network, VPN, or machine.
Use vendor reports as investigation context
Statusfield brings reported Greenhouse incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
A reported incident can help you decide where to investigate and what to tell your team. An operational status does not prove that your account, region or complete workflow is working. Review the affected components and timestamps alongside your own logs and checks.
What to Do During a Greenhouse Outage
Immediate (first 5 minutes)
- Review reported vendor incidents alongside your own request logs. A matching incident adds context but does not establish the cause of your failure.
- Identify which Greenhouse components are affected. If only interview scheduling is down, you may still be able to access candidate pipelines and scorecards. If the core API is down, everything is blocked.
- Alert your recruiting coordinator team so they can notify candidates and interviewers with impending sessions — a brief heads-up prevents no-shows caused by broken calendar links.
- Check whether any time-sensitive offers or application deadlines are affected by the outage.
Communication (first 15 minutes)
- Post a brief update in your HR/recruiting team Slack channel: "Greenhouse is experiencing an outage. Candidate applications, scheduling, and scorecards may be temporarily unavailable. We're monitoring and will update when service is restored."
- If you have interviews scheduled in the next 60 minutes, proactively reach out to interviewers via email or calendar invite to confirm they have the interview details they need — don't rely on them pulling from Greenhouse during the outage.
- For candidates with active applications or pending scheduling links, send a brief email acknowledging the disruption rather than leaving them waiting on a broken link.
Recovery
- Once Greenhouse restores service, verify that any applications submitted through your job board during the outage were received and are visible in the pipeline.
- Check for any scorecards that interviewers may have attempted to submit during the outage — some may have failed silently and need to be re-submitted.
- Review HRIS sync logs to confirm Greenhouse pushed updates to Workday, BambooHR, or your other HRIS for any status changes made during the recovery window.
- Confirm that offer letters generated during the outage window sent successfully and were received by candidates.
Greenhouse Components and What Each Outage Looks Like
| Component | Impact when degraded |
|---|---|
| Core Application API | App inaccessible; recruiters and hiring managers fully blocked |
| Job Board / Application Ingestion | Candidates can't apply; application forms return errors |
| Interview Scheduling | Scheduling links broken; calendar sync fails; interviewers can't confirm sessions |
| Scorecard Submission | Interviewers can't save feedback; hiring decisions delayed |
| Offer Management | Offer letters can't be generated, sent, or tracked |
| Notifications & Email Alerts | Greenhouse-triggered emails don't send; teams don't receive updates on candidate status |
| HRIS / ATS Integrations | Workday, BambooHR, or other HRIS sync paused; headcount data lags |
Match the check to the failure you need to catch
Follow supported Greenhouse components for vendor-reported incidents. Add a public HTTPS check for your own website or API and define acceptable response codes, response time and body checks. A successful request is evidence about that endpoint, not proof that an entire customer journey works.
Use application logs and end-to-end tests for authenticated workflows, data correctness and transactions. Statusfield brings the monitoring results and vendor context together; it does not run a complete checkout or login flow.
Bring Greenhouse updates to your team
Follow reported Greenhouse status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Eligible first-time customers can start a free trial, no credit card required.
Follow Greenhouse incidents with your team
Follow Greenhouse and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
FAQ
Is Greenhouse down right now?
This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.
How can I get alerts about Greenhouse incidents?
Follow reported Greenhouse status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Does an operational Greenhouse status mean my application is working?
No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.
Browse the service catalog and plans and alert destinations.
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.