Lusha Outage History
10 incidents recorded over the last 365 days, 10 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 Lusha Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 7, 2026 | Investigating issues with ProspectingThis incident has been resolved. | 48 min | Resolved |
| Aug 3, 2026 | Elevated error rates affecting some API requestsAll services are fully operational. Support has confirmed customers are back to normal operation. | 3h 14m | Resolved |
| Jul 6, 2026 | Empty results from WorkspaceThis incident has been resolved. | 4h 34m | Resolved |
| Jun 1, 2026 | Conversational Intelligence returning 504 errorsConversational Intelligence (EU) is fully restored — the routing issue that caused errors between 07:45–09:05 UTC has been fixed and monitoring is in place to prevent recurrence. | 1h 9m | Resolved |
| May 13, 2026 | Latency issues with API requestsThis incident has been resolved. | 18 min | Resolved |
| May 5, 2026 | Investigating: Service Disruption in ProspectingThis incident has been resolved. | 1h 8m | Resolved |
| Apr 21, 2026 | Lusha's services are not availableThis incident has been resolved. | 51 min | Resolved |
| Jan 5, 2026 | Search Services – Partial AvailabilityThis incident has been resolved. | 2h 6m | Resolved |
| Dec 5, 2025 | Cloudflare issuesThe incident has been resolved, and all services are operating normally. We will continue monitoring to ensure stability. | 22 min | Resolved |
| Nov 11, 2025 | Lusha Service DisruptionThis incident has been resolved. | 44 min | 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 Lusha 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 Lusha 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 Lusha 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 Lusha outage in this window ran 4h 34m, against a mean recovery of 1h 31m. If you depend on Lusha 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.