Leadfeeder Outage History
14 incidents recorded over the last 365 days, 14 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 Leadfeeder Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Service downtimeThis incident has been resolved. | 10h 34m | Resolved |
| Aug 20, 2026 | Degraded performance in ListsThis incident has been resolved. | 41 min | Resolved |
| Jul 21, 2026 | Leadfeeder platform Email delivery issuesThis incident has been resolved. Email delivery is working normally. | 0 min | Resolved |
| Jun 22, 2026 | Issues with "Find More Contact Details" functionalityThe "Find More Contact Details" feature in Lists and the Company profile (Web Visitors, Target and Campaigns) is working again normally. | 4h 57m | Resolved |
| Jun 14, 2026 | Increased delay in leads processingThis incident has been resolved. | 2 min | Resolved |
| Jun 12, 2026 | Degraded performance in LeadfeederThis incident has been resolved. | 15 min | Resolved |
| May 29, 2026 | Lists Enrich Enable Web Search functionality degradedThis incident has been resolved. | 1h 5m | Resolved |
| Apr 17, 2026 | Issues with Company Profile and Integration features.This incident has been resolved. | 1h 16m | Resolved |
| Mar 20, 2026 | Some lists operations might be impacted from the UI and API.This incident has been resolved. | 27 min | Resolved |
| Mar 10, 2026 | Some lists operations might be impacted from the UI and API.This incident has been resolved. | 22h 28m | Resolved |
| Jan 5, 2026 | Issues with Echobot API and MonitoringThis incident has been resolved. | 2h 18m | Resolved |
| Nov 28, 2025 | We are experiencing errors across the Platform productsThis incident has been resolved. | 18 min | Resolved |
| Nov 21, 2025 | We are observing increased latency in registering some leads and visitsThis incident has been resolved. | 22h 22m | Resolved |
| Nov 13, 2025 | Echobot API is currently downThis incident has been resolved. | 16 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 Leadfeeder 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 Leadfeeder 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 Leadfeeder 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 Leadfeeder outage in this window ran 22h 28m, against a mean recovery of 4h 47m. If you depend on Leadfeeder 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.