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 45 min ago. Last stored result reached it in 269 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 349 ms | 0 |
| Mon 21 | 0 | 0.0 | 181 ms | 0 |
| Tue 00 | 0 | 0.0 | 473 ms | 0 |
| Tue 02 | 0 | 0.0 | 408 ms | 0 |
| Tue 04 | 0 | 0.0 | 170 ms | 0 |
| Tue 06 | 0 | 0.0 | 451 ms | 0 |
| Tue 08 | 0 | 0.0 | 410 ms | 0 |
| Tue 10 | 0 | 0.0 | 469 ms | 0 |
| Tue 12 | 0 | 0.0 | 331 ms | 0 |
| Tue 14 | 0 | 0.0 | 223 ms | 0 |
| Tue 17 | 0 | 0.0 | 517 ms | 0 |
| Tue 19 | 0 | 0.0 | 330 ms | 0 |
| Tue 21 | 0 | 0.0 | 428 ms | 0 |
| Tue 23 | 0 | 0.0 | 186 ms | 0 |
| Wed 02 | 0 | 0.0 | 257 ms | 0 |
| Wed 04 | 0 | 0.0 | 394 ms | 0 |
| Wed 06 | 0 | 0.0 | 490 ms | 0 |
| Wed 08 | 0 | 0.0 | 586 ms | 0 |
| Wed 11 | 0 | 0.0 | 325 ms | 0 |
| Wed 13 | 0 | 0.0 | 396 ms | 0 |
| Wed 15 | 0 | 0.0 | 321 ms | 0 |
| Wed 17 | 0 | 0.0 | 392 ms | 0 |
| Wed 19 | 0 | 0.0 | 534 ms | 0 |
| Wed 21 | 0 | 0.0 | 215 ms | 0 |
| Wed 23 | 0 | 0.0 | 539 ms | 0 |
| Thu 01 | 0 | 0.0 | 333 ms | 0 |
| Thu 03 | 0 | 0.0 | 352 ms | 0 |
| Thu 05 | 0 | 0.0 | 185 ms | 0 |
| Thu 07 | 0 | 0.0 | 323 ms | 0 |
| Thu 09 | 0 | 0.0 | 369 ms | 0 |
| Thu 11 | 0 | 0.0 | 268 ms | 0 |
| Thu 13 | 0 | 0.0 | 526 ms | 0 |
| Thu 15 | 0 | 0.0 | 421 ms | 0 |
| Thu 17 | 0 | 0.0 | 292 ms | 0 |
| Thu 20 | 0 | 0.0 | 335 ms | 0 |
| Thu 22 | 0 | 0.0 | 349 ms | 0 |
| Fri 00 | 0 | 0.0 | 203 ms | 0 |
| Fri 02 | 0 | 0.0 | 241 ms | 0 |
| Fri 04 | 0 | 0.0 | 469 ms | 0 |
| Fri 06 | 0 | 0.0 | 163 ms | 0 |
| Fri 08 | 0 | 0.0 | 125 ms | 0 |
| Fri 10 | 0 | 0.0 | 484 ms | 0 |
| Fri 11 | 0 | 0.0 | 326 ms | 0 |
| Fri 12 | 0 | 0.0 | 316 ms | 0 |
| Fri 14 | 0 | 0.0 | 157 ms | 0 |
| Fri 16 | 0 | 0.0 | 499 ms | 0 |
| Fri 17 | 0 | 0.0 | 530 ms | 0 |
| Fri 18 | 0 | 0.0 | 269 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 Beacon 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 Beacon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Beacon alerts to Slack, Discord or a webhook — free.
Beacon, at beacon.li, is one of the AI services we monitor. Reduce implementation effort and timelines by 60%+ with Beacon’s AI orchestration platform. Watch it run on your product in just 7 days.
Beacon publishes an official status page at status.beacon.li; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 321 ms average, 125–530 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Beacon incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
321 ms on average over the last 24 hours (125–530 ms).
Yes, at https://status.beacon.li.
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 Beacon here at once, the problem is on Beacon'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 Beacon. 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.