Workable Outage History
Workable is up right nowPingoru has recorded 52 incidents for Workable: 10 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 4 of 720 (1%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 2 | 4 of 744 (0%) |
| November 2026 | 0 | 0 of 108 (0%) |
Incidents, newest first
Critical March 6, 2025 AI Recruiter unavailable 1h 39m Sourcing with Search with AI
Started Mar 06, 2025, 07:58 AM UTC· resolved Mar 06, 2025, 09:38 AM UTC
- investigating Mar 06, 2025, 07:58 AM UTC
The AI Recruiter tool for sourcing candidates is currently not working and displays the following error: "An error occurred while loading more candidates. Try again." Our team is investigating the issue.
- resolved Mar 06, 2025, 09:38 AM UTC
This incident has been resolved.
Critical December 10, 2024 E-Signature service disruption 1h 30m E-signatures
Started Dec 10, 2024, 12:07 PM UTC· resolved Dec 10, 2024, 01:37 PM UTC
- investigating Dec 10, 2024, 12:07 PM UTC
We are currently experiencing a service disruption with the e-signature functionality. Users may encounter errors when sending, approving, signing, or updating e-signature templates. This issue affects e-signature workflows, including Offer Letters. We are actively investigating and working with our provider to resolve the issue. Updates will be shared as they become available.
- resolved Dec 10, 2024, 01:37 PM UTC
This incident has been resolved. Thank you for your patience!
Major December 4, 2024 Errors when moving/disqualifying candidates 33m Recruiting and applicant tracking
Started Dec 04, 2024, 10:10 AM UTC· resolved Dec 04, 2024, 10:44 AM UTC
- investigating Dec 04, 2024, 10:10 AM UTC
You might experience issues when moving/disqualifying candidates - we are investigating.
- resolved Dec 04, 2024, 10:44 AM UTC
The issue has been resolved now. Apologies for the disruption!