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 27 min ago. Last stored result reached it in 363 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 17 | 0 | 0.0 | 275 ms | 0 |
| Tue 19 | 0 | 0.0 | 341 ms | 0 |
| Tue 22 | 0 | 0.0 | 162 ms | 0 |
| Wed 00 | 0 | 0.0 | 165 ms | 0 |
| Wed 02 | 0 | 0.0 | 170 ms | 0 |
| Wed 04 | 0 | 0.0 | 126 ms | 0 |
| Wed 07 | 0 | 0.0 | 369 ms | 0 |
| Wed 09 | 0 | 0.0 | 179 ms | 0 |
| Wed 11 | 0 | 0.0 | 267 ms | 0 |
| Wed 13 | 0 | 0.0 | 205 ms | 0 |
| Wed 15 | 0 | 0.0 | 137 ms | 0 |
| Wed 17 | 0 | 0.0 | 274 ms | 0 |
| Wed 20 | 0 | 0.0 | 279 ms | 0 |
| Wed 22 | 0 | 0.0 | 159 ms | 0 |
| Thu 00 | 0 | 0.0 | 188 ms | 0 |
| Thu 01 | 0 | 0.0 | 196 ms | 0 |
| Thu 03 | 0 | 0.0 | 305 ms | 0 |
| Thu 05 | 0 | 0.0 | 274 ms | 0 |
| Thu 07 | 0 | 0.0 | 256 ms | 0 |
| Thu 09 | 0 | 0.0 | 272 ms | 0 |
| Thu 11 | 0 | 0.0 | 231 ms | 0 |
| Thu 13 | 0 | 0.0 | 213 ms | 0 |
| Thu 15 | 0 | 0.0 | 245 ms | 0 |
| Thu 17 | 0 | 0.0 | 319 ms | 0 |
| Thu 19 | 0 | 0.0 | 524 ms | 0 |
| Thu 21 | 0 | 0.0 | 252 ms | 0 |
| Thu 23 | 0 | 0.0 | 179 ms | 0 |
| Fri 02 | 0 | 0.0 | 182 ms | 0 |
| Fri 04 | 0 | 0.0 | 167 ms | 0 |
| Fri 06 | 0 | 0.0 | 315 ms | 0 |
| Fri 08 | 0 | 0.0 | 103 ms | 0 |
| Fri 10 | 0 | 0.0 | 261 ms | 0 |
| Fri 11 | 0 | 0.0 | 241 ms | 0 |
| Fri 13 | 0 | 0.0 | 257 ms | 0 |
| Fri 15 | 0 | 0.0 | 222 ms | 0 |
| Fri 17 | 0 | 0.0 | 281 ms | 0 |
| Fri 18 | 0 | 0.0 | 170 ms | 0 |
| Fri 20 | 0 | 0.0 | 209 ms | 0 |
| Fri 22 | 0 | 0.0 | 252 ms | 0 |
| Sat 00 | 0 | 0.0 | 293 ms | 0 |
| Sat 02 | 0 | 0.0 | 322 ms | 0 |
| Sat 04 | 0 | 0.0 | 244 ms | 0 |
| Sat 05 | 0 | 0.0 | 163 ms | 0 |
| Sat 06 | 0 | 0.0 | 159 ms | 0 |
| Sat 07 | 0 | 0.0 | 260 ms | 0 |
| Sat 09 | 0 | 0.0 | 270 ms | 0 |
| Sat 11 | 0 | 0.0 | 158 ms | 0 |
| Sat 14 | 0 | 0.0 | 363 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 Lucky Orange 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 Lucky Orange goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Lucky Orange alerts to Slack, Discord or a webhook — free.
Lucky Orange is listed in our AI category and checked at luckyorange.com. Lucky Orange gives you heatmaps, session recordings, funnels, surveys, and Discovery AI — connected tools that show you where visitors drop off and what to fix first.
Lucky Orange publishes an official status page at status.luckyorange.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with 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: 240 ms average, 158–363 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Lucky Orange incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
240 ms on average over the last 24 hours (158–363 ms).
Yes, at https://status.luckyorange.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 Lucky Orange here at once, the problem is on Lucky Orange'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 Lucky Orange. 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.