Spark Hire Recruit Outage History
9 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Spark Hire Recruit Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 11, 2026 | Investigating Issues with Select AI-Powered FeaturesIssue is resolved | 52 min | Resolved |
| Aug 2, 2026 | Analytics reports are not being generatedThis incident has been resolved. | 3h 44m | Resolved |
| Jun 13, 2026 | Scheduled Maintenance Report for Spark Hire RecruitThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 6, 2026 | Scheduled Maintenance Report for Spark Hire RecruitThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 29, 2026 | Office 365 calendar integration outageThis incident has been resolved, and the Office 365 integration has returned to regular functionality. | 1h 17m | Resolved |
| Mar 28, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Feb 4, 2026 | Spark Hire Recruit users may experience low performanceSpark Hire Recruit is operating normally again and performance has returned to expected levels. We’ll continue monitoring to ensure everything remains stable. We apologize for the inconvenience and appreciate your… | 38 min | Resolved |
| Jan 15, 2026 | Analytics Reports Partial OutageThe issue has been fully resolved and Analytics reports have returned to regular functionality. | 6h 52m | Resolved |
| Dec 5, 2025 | Scheduled maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Spark Hire Recruit incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Spark Hire Recruit Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Spark Hire Recruit acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Spark Hire Recruit outage in this window ran 6h 52m, against a mean recovery of 2h 3m. If you depend on Spark Hire Recruit in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.