User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
lusha.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests lusha.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 316 ms · 3 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 218 ms | 0 |
| 03:15 | 0 | 0.0 | 492 ms | 0 |
| 03:30 | 0 | 0.0 | 476 ms | 0 |
| 03:45 | 0 | 0.0 | 252 ms | 0 |
| 04:00 | 0 | 0.0 | 197 ms | 0 |
| 04:15 | 0 | 0.0 | 509 ms | 0 |
| 04:30 | 0 | 0.0 | 404 ms | 0 |
| 04:45 | 0 | 0.0 | 164 ms | 0 |
| 05:00 | 0 | 0.0 | 464 ms | 0 |
| 05:15 | 0 | 0.0 | 324 ms | 0 |
| 05:30 | 0 | 0.0 | 167 ms | 0 |
| 05:45 | 0 | 0.0 | 308 ms | 0 |
| 06:00 | 0 | 0.0 | 181 ms | 0 |
| 06:15 | 0 | 0.0 | 294 ms | 0 |
| 06:30 | 0 | 0.0 | 978 ms | 0 |
| 06:45 | 0 | 0.0 | 377 ms | 0 |
| 07:00 | 0 | 0.0 | 314 ms | 0 |
| 07:15 | 0 | 0.0 | 348 ms | 0 |
| 07:30 | 0 | 0.0 | 332 ms | 0 |
| 07:45 | 0 | 0.0 | 214 ms | 0 |
| 08:00 | 0 | 0.0 | 614 ms | 0 |
| 08:15 | 0 | 0.0 | 211 ms | 0 |
| 08:30 | 0 | 0.0 | 220 ms | 0 |
| 08:45 | 0 | 0.0 | 379 ms | 0 |
| 09:00 | 0 | 0.0 | 349 ms | 0 |
| 09:15 | 0 | 0.0 | 163 ms | 0 |
| 09:30 | 0 | 0.0 | 368 ms | 0 |
| 09:45 | 0 | 0.0 | 887 ms | 0 |
| 10:00 | 0 | 0.0 | 839 ms | 0 |
| 10:15 | 0 | 0.0 | 525 ms | 0 |
| 10:30 | 0 | 0.0 | 451 ms | 0 |
| 10:45 | 0 | 0.0 | 704 ms | 0 |
| 11:00 | 0 | 0.0 | 179 ms | 0 |
| 11:15 | 0 | 0.0 | 212 ms | 0 |
| 11:30 | 0 | 0.0 | 318 ms | 0 |
| 11:45 | 0 | 0.0 | 841 ms | 0 |
| 12:00 | 0 | 0.0 | 348 ms | 0 |
| 12:15 | 0 | 0.0 | 316 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Lusha yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Lusha goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Lusha alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Lusha is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Lusha's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.