User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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.
Reaching it
Last checked 5 min ago. Last stored result reached it in 91 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 05 | 0 | 0.0 | 75 ms | 0 |
| Tue 07 | 0 | 0.0 | 69 ms | 0 |
| Tue 09 | 0 | 0.0 | 62 ms | 0 |
| Tue 11 | 0 | 0.0 | 260 ms | 0 |
| Tue 14 | 0 | 0.0 | 158 ms | 0 |
| Tue 16 | 0 | 0.0 | 136 ms | 0 |
| Tue 18 | 0 | 0.0 | 157 ms | 0 |
| Tue 20 | 0 | 0.0 | 80 ms | 0 |
| Tue 23 | 0 | 0.0 | 162 ms | 0 |
| Wed 01 | 0 | 0.0 | 59 ms | 0 |
| Wed 03 | 0 | 0.0 | 75 ms | 0 |
| Wed 05 | 0 | 0.0 | 53 ms | 0 |
| Wed 08 | 0 | 0.0 | 65 ms | 0 |
| Wed 10 | 0 | 0.0 | 53 ms | 0 |
| Wed 12 | 0 | 0.0 | 50 ms | 0 |
| Wed 14 | 0 | 0.0 | 60 ms | 0 |
| Wed 16 | 0 | 0.0 | 78 ms | 0 |
| Wed 18 | 0 | 0.0 | 103 ms | 0 |
| Wed 21 | 0 | 0.0 | 143 ms | 0 |
| Wed 23 | 0 | 0.0 | 112 ms | 0 |
| Thu 01 | 0 | 0.0 | 276 ms | 0 |
| Thu 03 | 0 | 0.0 | 62 ms | 0 |
| Thu 05 | 0 | 0.0 | 192 ms | 0 |
| Thu 07 | 0 | 0.0 | 274 ms | 0 |
| Thu 09 | 0 | 0.0 | 54 ms | 0 |
| Thu 11 | 0 | 0.0 | 66 ms | 0 |
| Thu 13 | 0 | 0.0 | 146 ms | 0 |
| Thu 16 | 0 | 0.0 | 63 ms | 0 |
| Thu 18 | 0 | 0.0 | 196 ms | 0 |
| Thu 20 | 0 | 0.0 | 496 ms | 0 |
| Thu 22 | 0 | 0.0 | 62 ms | 0 |
| Fri 00 | 0 | 0.0 | 78 ms | 0 |
| Fri 02 | 0 | 0.0 | 42 ms | 0 |
| Fri 04 | 0 | 0.0 | 61 ms | 0 |
| Fri 06 | 0 | 0.0 | 42 ms | 0 |
| Fri 08 | 0 | 0.0 | 54 ms | 0 |
| Fri 10 | 0 | 0.0 | 64 ms | 0 |
| Fri 12 | 0 | 0.0 | 151 ms | 0 |
| Fri 14 | 0 | 0.0 | 77 ms | 0 |
| Fri 16 | 0 | 0.0 | 79 ms | 0 |
| Fri 17 | 0 | 0.0 | 82 ms | 0 |
| Fri 18 | 0 | 0.0 | 65 ms | 0 |
| Fri 19 | 0 | 0.0 | 78 ms | 0 |
| Fri 21 | 0 | 0.0 | 52 ms | 0 |
| Fri 22 | 0 | 0.0 | 125 ms | 0 |
| Sat 00 | 0 | 0.0 | 204 ms | 0 |
| Sat 02 | 0 | 0.0 | 297 ms | 0 |
| Sat 05 | 0 | 0.0 | 91 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Imobilead 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 Imobilead goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Imobilead alerts to Slack, Discord or a webhook — free.
Imobilead, at imobilead.me, is one of the Productivity services we monitor. CRM para imobiliárias gerenciarem times de corretores: distribuição automática de leads, ranking de corretores e funil de vendas. Teste grátis por 7 dias.
Imobilead publishes an official status page at status.imobilead.me; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 109 ms average, 42–308 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Imobilead incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
109 ms on average over the last 24 hours (42–308 ms).
Yes, at https://status.imobilead.me.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Imobilead here at once, the problem is on Imobilead'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 Imobilead. 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.