User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Our checks can't reach Landingi right now
Landingi is blocking or timing out our automated checks, so we can't test it directly. We still count user reports and watch the official status page.
Last checked 58 min ago. Last stored result reached it in 13 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 04 | 0 | 0.0 | 27 ms | 0 |
| Tue 06 | 0 | 0.0 | 178 ms | 0 |
| Tue 08 | 0 | 0.0 | 104 ms | 0 |
| Tue 10 | 0 | 0.0 | 43 ms | 0 |
| Tue 13 | 0 | 0.0 | 52 ms | 0 |
| Tue 15 | 0 | 0.0 | 40 ms | 0 |
| Tue 17 | 0 | 0.0 | 65 ms | 0 |
| Tue 19 | 0 | 0.0 | 38 ms | 0 |
| Tue 22 | 0 | 0.0 | 33 ms | 0 |
| Wed 00 | 0 | 0.0 | 37 ms | 0 |
| Wed 02 | 0 | 0.0 | 18 ms | 0 |
| Wed 04 | 0 | 0.0 | 97 ms | 0 |
| Wed 07 | 0 | 0.0 | 33 ms | 0 |
| Wed 09 | 0 | 0.0 | 53 ms | 0 |
| Wed 11 | 0 | 0.0 | 62 ms | 0 |
| Wed 13 | 0 | 0.0 | 52 ms | 0 |
| Wed 15 | 0 | 0.0 | 27 ms | 0 |
| Wed 17 | 0 | 0.0 | 24 ms | 0 |
| Wed 20 | 0 | 0.0 | 90 ms | 0 |
| Wed 21 | 0 | 0.0 | 92 ms | 0 |
| Wed 23 | 0 | 0.0 | 88 ms | 0 |
| Thu 01 | 0 | 0.0 | 103 ms | 0 |
| Thu 03 | 0 | 0.0 | 56 ms | 0 |
| Thu 05 | 0 | 0.0 | 25 ms | 0 |
| Thu 07 | 0 | 0.0 | 15 ms | 0 |
| Thu 09 | 0 | 0.0 | 93 ms | 0 |
| Thu 11 | 0 | 0.0 | 30 ms | 0 |
| Thu 13 | 0 | 0.0 | 51 ms | 0 |
| Thu 15 | 0 | 0.0 | 65 ms | 0 |
| Thu 17 | 0 | 0.0 | 70 ms | 0 |
| Thu 19 | 0 | 0.0 | 63 ms | 0 |
| Thu 21 | 0 | 0.0 | 76 ms | 0 |
| Thu 23 | 0 | 0.0 | 18 ms | 0 |
| Fri 02 | 0 | 0.0 | 47 ms | 0 |
| Fri 04 | 0 | 0.0 | 36 ms | 0 |
| Fri 06 | 0 | 0.0 | 44 ms | 0 |
| Fri 07 | 0 | 0.0 | 88 ms | 0 |
| Fri 09 | 0 | 0.0 | 54 ms | 0 |
| Fri 10 | 0 | 0.0 | 125 ms | 0 |
| Fri 12 | 0 | 0.0 | 30 ms | 0 |
| Fri 14 | 0 | 0.0 | 59 ms | 0 |
| Fri 16 | 0 | 0.0 | 53 ms | 0 |
| Fri 18 | 0 | 0.0 | 77 ms | 0 |
| Fri 19 | 0 | 0.0 | 68 ms | 0 |
| Fri 21 | 0 | 0.0 | 64 ms | 0 |
| Fri 22 | 0 | 0.0 | 144 ms | 0 |
| Sat 00 | 0 | 0.0 | 102 ms | 0 |
| Sat 02 | 0 | 0.0 | 41 ms | 0 |
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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Landingi 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 Landingi goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Landingi alerts to Slack, Discord or a webhook — free.
We track Landingi (landingi.com) as part of the AI group. Scale lead generation faster with AI-powered landing pages, enterprise-grade infrastructure, and proven marketing expertise.
Landingi publishes an official status page at status.landingi.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 67 ms average, 10–144 ms range across 17 successful checks.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
We have not recorded a public Landingi incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
67 ms on average over the last 24 hours (10–144 ms).
Yes, at https://status.landingi.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Landingi here at once, the problem is on Landingi'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 Landingi. 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.