Skip to main content
Greenhouse

Performance Degradation

Degraded Lasted 1h 27m · started · Greenhouse's page

Level
confirmed
Worst impact
Degraded
Components
Resume parsing
Down Index
18of 100

What to do

  • Check whether you use Greenhouse Resume parsing. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 27m it lasted.

    Anything that failed between 2026-03-31 22:03 UTC and 2026-03-31 23:30 UTC may need a replay.
  • Subscribe to Greenhouse's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=greenhouse works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Greenhouse 2

  1. identified

    Talent Matching is experiencing performance degradation. We are currently implementing a fix.

    provider

  2. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-3645b4fe9e

Is Greenhouse still down?

No, this incident was resolved 2026-03-31 23:30 UTC. For Greenhouse's live state, see https://down.guide/greenhouse.

How long did it last?

1h 27m, from 2026-03-31 22:03 UTC to 2026-03-31 23:30 UTC, by the times Greenhouse posted.

What was affected?

Greenhouse named Resume parsing.

What caused it?

Greenhouse hasn't published a root cause. If it does, it shows here.

Where does this come from?

Greenhouse's official status page, https://status.greenhouse.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.