Is Greenhouse Down Right Now? Live Greenhouse Status & Outages | IsDown Outage History

Is Greenhouse Down Right Now? Live Greenhouse Status & Outages | IsDown is up right now

Pingoru has recorded 69 incidents for Is Greenhouse Down Right Now? Live Greenhouse Status & Outages | IsDown: 64 in the last 12 months and 14 in the last 90 days.

Source: status.greenhouse.io

69incidents recorded
64last 12 months
14last 90 days
26 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct4
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct2%
Pingoru began tracking Is Greenhouse Down Right Now? Live Greenhouse Status & Outages | IsDown in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026016 of 720 (2%)
May 20261132 of 744 (4%)
June 2026735 of 720 (5%)
July 20264322 of 744 (43%)
August 20261115 of 744 (15%)
September 2026941 of 720 (6%)
October 2026411 of 592 (2%)

Incidents, newest first

Major October 10, 2025 Sending Offers Issues 4h 44m Silo 1, Silo 2, Silo 3, Silo 4 and 7 more

Started Oct 10, 2025, 04:11 PM UTC· resolved Oct 10, 2025, 08:56 PM UTC

  1. investigating Oct 10, 2025, 04:11 PM UTC

    We are investigating reports of some customers experiencing issues sending offers with Docusign.

  2. identified Oct 10, 2025, 04:32 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 10, 2025, 07:52 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 10, 2025, 08:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 9, 2025 API Credentials Error 1h 58m Silo 1, Silo 2, Silo 3, Silo 4 and 7 more

Started Oct 09, 2025, 05:42 PM UTC· resolved Oct 09, 2025, 07:41 PM UTC

  1. investigating Oct 09, 2025, 05:42 PM UTC

    We are currently investigating reports of customers seeing errors when trying to manage their Greenhouse API credentials.

  2. identified Oct 09, 2025, 05:54 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Oct 09, 2025, 07:41 PM UTC

    This incident has been resolved.

Read the full incident report →