Is Greenhouse Down?

No — Greenhouse is up

Reachable from all 8 checked regions

Average response time: 57ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://greenhouse.statuspage.io

Greenhouse uptime

—

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad

50ms

DNS 0ms TCP 1ms TLS 11ms TTFB 41ms

jnb

51ms

DNS 0ms TCP 0ms TLS 14ms TTFB 40ms

lax

78ms

DNS 0ms TCP 1ms TLS 22ms TTFB 69ms

lhr

56ms

DNS 0ms TCP 2ms TLS 13ms TTFB 43ms

nrt

56ms

DNS 0ms TCP 1ms TLS 12ms TTFB 46ms

ord

55ms

DNS 0ms TCP 1ms TLS 12ms TTFB 46ms

sin

64ms

DNS 1ms TCP 1ms TLS 11ms TTFB 55ms

sjc

52ms

DNS 0ms TCP 3ms TLS 12ms TTFB 40ms

syd

45ms

DNS 0ms TCP 1ms TLS 13ms TTFB 34ms

What Greenhouse does

Greenhouse is an applicant tracking system that recruiting teams use to post roles, collect applications, run interview scorecards and manage offers. Its job boards are the public careers pages candidates apply through, hosted by Greenhouse on behalf of the employer, so an outage is visible to job seekers as well as to the company's own recruiters.

What an outage looks like

Recruiters cannot open candidate profiles or move applicants between stages, and the Greenhouse Chrome Extension stops capturing profiles. Candidates hitting the employer's careers page see it fail to load, or an application submit that never completes. Resume parsing and document conversion have their own rows on the status page, so an upload can succeed while the parsed fields stay blank.

What to do about it

Read greenhouse.statuspage.io and check which component is affected: Greenhouse Recruiting, Job Boards, Harvest API and Onboarding fail independently. If only Job Boards is down, internal work continues but candidates cannot apply, which is worth saying publicly. The page also tracks upstreams Greenhouse depends on, including Mailgun and Google Drive, so an email or attachment problem may not be Greenhouse's own.

Is it down for everyone, or just you?

If this page says Greenhouse is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Greenhouse outage FAQ

Are applications lost if Greenhouse Job Boards is down?

A submission that returned an error did not reach Greenhouse, so the candidate has to apply again once the board recovers. Greenhouse tracks Job Boards as its own component precisely because it can fail while the recruiting application stays up. Employers running to a hiring deadline during an incident usually extend it rather than assume the applications arrived.

Does a Greenhouse outage stop interview emails and calendar invites?

It can, and the cause is often an upstream rather than Greenhouse. The status page tracks Mailgun inbound, outbound, SMTP and API alongside Google Gmail and Calendar and Outlook 365, because Greenhouse sends candidate mail and books interviews through them. If those rows are red and Greenhouse Recruiting is green, scheduling is affected while the rest of the product works.

Is the Harvest API affected when the Greenhouse web app is down?

Not necessarily. Harvest API is listed separately from Greenhouse Recruiting, so integrations pulling candidate data can keep working while recruiters cannot sign in, or fail on their own while the interface is fine. If your HRIS sync has stopped, check the HRIS Link rows too, which are broken out per provider for ADP, Workday and UKG.

How do I tell a Greenhouse outage from a problem with my own account?

Check whether the affected component is red on greenhouse.statuspage.io first. If every component is operational and only your team is stuck, the cause is more likely permissions, a browser extension, or a single integration rather than the platform. Audit Log and MyGreenhouse are separate rows, and a fault in either affects only part of the product.

How we measure this

We request Greenhouse's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Greenhouse publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Greenhouse goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required