User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
leadfeeder.com · Cloud & developer
Is Leadfeeder down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → leadfeeder.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 75 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 58 ms | 0 |
| Mon 14 | 0 | 0.0 | 117 ms | 0 |
| Mon 17 | 0 | 0.0 | 59 ms | 0 |
| Mon 19 | 0 | 0.0 | 39 ms | 0 |
| Mon 21 | 0 | 0.0 | 143 ms | 0 |
| Mon 23 | 0 | 0.0 | 139 ms | 0 |
| Tue 01 | 0 | 0.0 | 61 ms | 0 |
| Tue 03 | 0 | 0.0 | 70 ms | 0 |
| Tue 05 | 0 | 0.0 | 89 ms | 0 |
| Tue 07 | 0 | 0.0 | 105 ms | 0 |
| Tue 09 | 0 | 0.0 | 59 ms | 0 |
| Tue 12 | 0 | 0.0 | 61 ms | 0 |
| Tue 14 | 0 | 0.0 | 128 ms | 0 |
| Tue 16 | 0 | 0.0 | 102 ms | 0 |
| Tue 18 | 0 | 0.0 | 62 ms | 0 |
| Tue 21 | 0 | 0.0 | 91 ms | 0 |
| Tue 23 | 0 | 0.0 | 82 ms | 0 |
| Wed 01 | 0 | 0.0 | 59 ms | 0 |
| Wed 03 | 0 | 0.0 | 89 ms | 0 |
| Wed 06 | 0 | 0.0 | 92 ms | 0 |
| Wed 08 | 0 | 0.0 | 94 ms | 0 |
| Wed 10 | 0 | 0.0 | 146 ms | 0 |
| Wed 12 | 0 | 0.0 | 142 ms | 0 |
| Wed 14 | 0 | 0.0 | 42 ms | 0 |
| Wed 16 | 0 | 0.0 | 35 ms | 0 |
| Wed 19 | 0 | 0.0 | 80 ms | 0 |
| Wed 21 | 0 | 0.0 | 89 ms | 0 |
| Wed 23 | 0 | 0.0 | 96 ms | 0 |
| Thu 01 | 0 | 0.0 | 135 ms | 0 |
| Thu 03 | 0 | 0.0 | 171 ms | 0 |
| Thu 05 | 0 | 0.0 | 58 ms | 0 |
| Thu 07 | 0 | 0.0 | 140 ms | 0 |
| Thu 09 | 0 | 0.0 | 97 ms | 0 |
| Thu 11 | 0 | 0.0 | 107 ms | 0 |
| Thu 14 | 0 | 0.0 | 121 ms | 0 |
| Thu 16 | 0 | 0.0 | 35 ms | 0 |
| Thu 18 | 0 | 0.0 | 97 ms | 0 |
| Thu 20 | 0 | 0.0 | 109 ms | 0 |
| Thu 22 | 0 | 0.0 | 38 ms | 0 |
| Fri 00 | 0 | 0.0 | 44 ms | 0 |
| Fri 02 | 0 | 0.0 | 67 ms | 0 |
| Fri 04 | 0 | 0.0 | 103 ms | 0 |
| Fri 06 | 0 | 0.0 | 87 ms | 0 |
| Fri 08 | 0 | 0.0 | 61 ms | 0 |
| Fri 10 | 0 | 0.0 | 117 ms | 0 |
| Fri 11 | 0 | 0.0 | 44 ms | 0 |
| Fri 12 | 0 | 0.0 | 149 ms | 0 |
| Fri 14 | 0 | 0.0 | 75 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Leadfeeder badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Leadfeeder yet. Outages of 10 minutes or more get their own page here.
Having trouble with Leadfeeder?
One report per service every 10 minutes from this network. No account.
Follow Leadfeeder
Get an email when Leadfeeder goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Leadfeeder alerts to Slack, Discord or a webhook — free.
About Leadfeeder
Leadfeeder is listed in our Cloud & developer category and checked at leadfeeder.com. Identify anonymous website visitors, uncover buying intent, and turn traffic into qualified B2B pipeline.
Leadfeeder publishes an official status page at status.leadfeeder.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 83 ms average, 38–149 ms range across 12 successful checks.
Questions
Is Leadfeeder down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Leadfeeder last down?
We have not recorded a public Leadfeeder incident since monitoring began 8 days ago.
What is Leadfeeder's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Leadfeeder respond?
83 ms on average over the last 24 hours (38–149 ms).
Does Leadfeeder have an official status page?
Yes, at https://status.leadfeeder.com.
Leadfeeder not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Leadfeeder here at once, the problem is on Leadfeeder's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Leadfeeder. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.