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 1 hr ago. Last stored result reached it in 193 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 285 ms | 0 |
| Mon 18 | 0 | 0.0 | 114 ms | 0 |
| Mon 20 | 0 | 0.0 | 257 ms | 0 |
| Mon 22 | 0 | 0.0 | 127 ms | 0 |
| Tue 00 | 0 | 0.0 | 122 ms | 0 |
| Tue 02 | 0 | 0.0 | 276 ms | 0 |
| Tue 04 | 0 | 0.0 | 121 ms | 0 |
| Tue 06 | 0 | 0.0 | 139 ms | 0 |
| Tue 08 | 0 | 0.0 | 87 ms | 0 |
| Tue 10 | 0 | 0.0 | 100 ms | 0 |
| Tue 13 | 0 | 0.0 | 126 ms | 0 |
| Tue 15 | 0 | 0.0 | 263 ms | 0 |
| Tue 17 | 0 | 0.0 | 218 ms | 0 |
| Tue 19 | 0 | 0.0 | 159 ms | 0 |
| Tue 22 | 0 | 0.0 | 86 ms | 0 |
| Wed 00 | 0 | 0.0 | 302 ms | 0 |
| Wed 02 | 0 | 0.0 | 122 ms | 0 |
| Wed 04 | 0 | 0.0 | 219 ms | 0 |
| Wed 07 | 0 | 0.0 | 103 ms | 0 |
| Wed 09 | 0 | 0.0 | 164 ms | 0 |
| Wed 11 | 0 | 0.0 | 132 ms | 0 |
| Wed 13 | 0 | 0.0 | 123 ms | 0 |
| Wed 15 | 0 | 0.0 | 117 ms | 0 |
| Wed 17 | 0 | 0.0 | 110 ms | 0 |
| Wed 20 | 0 | 0.0 | 211 ms | 0 |
| Wed 22 | 0 | 0.0 | 109 ms | 0 |
| Thu 00 | 0 | 0.0 | 210 ms | 0 |
| Thu 02 | 0 | 0.0 | 124 ms | 0 |
| Thu 04 | 0 | 0.0 | 148 ms | 0 |
| Thu 06 | 0 | 0.0 | 116 ms | 0 |
| Thu 08 | 0 | 0.0 | 245 ms | 0 |
| Thu 10 | 0 | 0.0 | 109 ms | 0 |
| Thu 12 | 0 | 0.0 | 139 ms | 0 |
| Thu 15 | 0 | 0.0 | 151 ms | 0 |
| Thu 16 | 0 | 0.0 | 303 ms | 0 |
| Thu 18 | 0 | 0.0 | 153 ms | 0 |
| Thu 20 | 0 | 0.0 | 156 ms | 0 |
| Thu 22 | 0 | 0.0 | 118 ms | 0 |
| Fri 00 | 0 | 0.0 | 91 ms | 0 |
| Fri 02 | 0 | 0.0 | 186 ms | 0 |
| Fri 04 | 0 | 0.0 | 199 ms | 0 |
| Fri 06 | 0 | 0.0 | 311 ms | 0 |
| Fri 08 | 0 | 0.0 | 87 ms | 0 |
| Fri 11 | 0 | 0.0 | 69 ms | 0 |
| Fri 13 | 0 | 0.0 | 112 ms | 0 |
| Fri 15 | 0 | 0.0 | 263 ms | 0 |
| Fri 17 | 0 | 0.0 | 153 ms | 0 |
| Fri 19 | 0 | 0.0 | 193 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Levitate 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 Levitate goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Levitate alerts to Slack, Discord or a webhook — free.
Levitate is listed in our AI category and checked at levitate.ai. Levitate uses AI to know who needs your attention, what to say and when to reach out, backed by a dedicated Success Specialist. Built for small businesses.
Levitate publishes an official status page at status.levitate.ai; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 162 ms average, 69–311 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 Levitate incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
162 ms on average over the last 24 hours (69–311 ms).
Yes, at https://status.levitate.ai.
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 Levitate here at once, the problem is on Levitate'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 Levitate. 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.