User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 2 hr ago. Last stored result reached it in 158 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 176 ms | 0 |
| Mon 14 | 0 | 0.0 | 63 ms | 0 |
| Mon 16 | 0 | 0.0 | 146 ms | 0 |
| Mon 18 | 0 | 0.0 | 141 ms | 0 |
| Mon 20 | 0 | 0.0 | 160 ms | 0 |
| Mon 22 | 0 | 0.0 | 141 ms | 0 |
| Tue 00 | 0 | 0.0 | 67 ms | 0 |
| Tue 02 | 0 | 0.0 | 136 ms | 0 |
| Tue 04 | 0 | 0.0 | 231 ms | 0 |
| Tue 07 | 0 | 0.0 | 50 ms | 0 |
| Tue 09 | 0 | 0.0 | 41 ms | 0 |
| Tue 11 | 0 | 0.0 | 600 ms | 0 |
| Tue 13 | 0 | 0.0 | 296 ms | 0 |
| Tue 15 | 0 | 0.0 | 129 ms | 0 |
| Tue 18 | 0 | 0.0 | 119 ms | 0 |
| Tue 20 | 0 | 0.0 | 183 ms | 0 |
| Tue 22 | 0 | 0.0 | 124 ms | 0 |
| Wed 00 | 0 | 0.0 | 59 ms | 0 |
| Wed 03 | 0 | 0.0 | 130 ms | 0 |
| Wed 05 | 0 | 0.0 | 649 ms | 0 |
| Wed 07 | 0 | 0.0 | 111 ms | 0 |
| Wed 09 | 0 | 0.0 | 216 ms | 0 |
| Wed 12 | 0 | 0.0 | 162 ms | 0 |
| Wed 14 | 0 | 0.0 | 205 ms | 0 |
| Wed 16 | 0 | 0.0 | 155 ms | 0 |
| Wed 19 | 0 | 0.0 | 558 ms | 0 |
| Wed 21 | 0 | 0.0 | 597 ms | 0 |
| Wed 23 | 0 | 0.0 | 164 ms | 0 |
| Thu 01 | 0 | 0.0 | 162 ms | 0 |
| Thu 03 | 0 | 0.0 | 145 ms | 0 |
| Thu 05 | 0 | 0.0 | 137 ms | 0 |
| Thu 07 | 0 | 0.0 | 82 ms | 0 |
| Thu 09 | 0 | 0.0 | 151 ms | 0 |
| Thu 12 | 0 | 0.0 | 144 ms | 0 |
| Thu 14 | 0 | 0.0 | 162 ms | 0 |
| Thu 16 | 0 | 0.0 | 146 ms | 0 |
| Thu 18 | 0 | 0.0 | 199 ms | 0 |
| Thu 20 | 0 | 0.0 | 187 ms | 0 |
| Thu 22 | 0 | 0.0 | 166 ms | 0 |
| Fri 00 | 0 | 0.0 | 61 ms | 0 |
| Fri 02 | 0 | 0.0 | 80 ms | 0 |
| Fri 04 | 0 | 0.0 | 49 ms | 0 |
| Fri 06 | 0 | 0.0 | 186 ms | 0 |
| Fri 08 | 0 | 0.0 | 137 ms | 0 |
| Fri 10 | 0 | 0.0 | 556 ms | 0 |
| Fri 12 | 0 | 0.0 | 133 ms | 0 |
| Fri 14 | 0 | 0.0 | 51 ms | 0 |
| Fri 16 | 0 | 0.0 | 158 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 Smartness 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 Smartness goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Smartness alerts to Slack, Discord or a webhook — free.
Smartness is listed in our AI category and checked at smartness.com. Automate your property’s key operations with AI: increase revenue, cut OTA commissions, and save hours of manual work.
Smartness publishes an official status page at status.smartness.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 164 ms average, 49–556 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Smartness incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
164 ms on average over the last 24 hours (49–556 ms).
Yes, at https://status.smartness.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 Smartness here at once, the problem is on Smartness'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 Smartness. 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.