Spark Hire Meet Outage History
2 incidents 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 Spark Hire Meet Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 20, 2026 | Live video interview connectivity issueA fix has been implemented and live video interviews should be functioning as expected. If you continue to experience issues, please clear your cache. | 1h 38m | Resolved |
| Aug 1, 2026 | Scheduled maintenanceScheduled maintenance is now complete. Thank you for your patience! If you encounter any issues from here on out, please submit a support ticket here: https://support.sparkhire.com/hc/en-us/requests/new | 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 Meet 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 Meet 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 Meet 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 Meet outage in this window ran 1h 38m, against a mean recovery of 1h 19m. If you depend on Spark Hire Meet 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.