Lusha status history
Current state: operational — “All Systems Operational” per https://status.lusha.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Lusha incidents last?
From 12 incidents with a vendor-posted start and resolve time. Longest on record: Empty results from Workspace — 4.6 h (2026-07-06 04:54 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (12)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-07 17:44 UTC | Investigating issues with Prospecting | resolved | minor | 48 min |
| 2026-08-03 10:50 UTC | Elevated error rates affecting some API requests | resolved | major | 3 h 14 min |
| 2026-07-06 04:54 UTC | Empty results from Workspace | resolved | minor | 4 h 34 min |
| 2026-06-01 08:36 UTC | Conversational Intelligence returning 504 errors | resolved | critical | 1 h 09 min |
| 2026-05-13 14:06 UTC | Latency issues with API requests | resolved | major | 18 min |
| 2026-05-05 09:59 UTC | Investigating: Service Disruption in Prospecting | resolved | major | 1 h 08 min |
| 2026-04-21 12:47 UTC | Lusha's services are not available | resolved | none | 51 min |
| 2026-01-05 14:09 UTC | Search Services – Partial Availability | resolved | minor | 2 h 06 min |
| 2025-12-05 09:24 UTC | Cloudflare issues | resolved | critical | 22 min |
| 2025-11-11 09:34 UTC | Lusha Service Disruption | resolved | critical | 44 min |
| 2025-09-07 14:20 UTC | Services outage | resolved | none | 0 min |
| 2025-08-13 13:06 UTC | Lusha Dashboard Access Issue | resolved | major | 1 h 18 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Lusha with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"lusha"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}