hireEZ Outage History
1 incident recorded over the last 365 days, 1 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 hireEZ Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Dec 10, 2025 | Performance issues searching candidateDuring a planned database migration, we experienced sustained and escalating CPU spikes on the new primary database instance shortly after cutover. Despite scaling the infrastructure, adding replicas, creating missing… | 23h 30m | Resolved |
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 hireEZ 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 hireEZ 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 hireEZ 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 hireEZ outage in this window ran 23h 30m, against a mean recovery of 23h 30m. If you depend on hireEZ 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.