User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
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 60 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 02 | 0 | 0.0 | 66 ms | 0 |
| Wed 04 | 0 | 0.0 | 87 ms | 0 |
| Wed 06 | 0 | 0.0 | 136 ms | 0 |
| Wed 08 | 0 | 0.0 | 166 ms | 0 |
| Wed 11 | 0 | 0.0 | 52 ms | 0 |
| Wed 13 | 0 | 0.0 | 142 ms | 0 |
| Wed 15 | 0 | 0.0 | 65 ms | 0 |
| Wed 17 | 0 | 0.0 | 155 ms | 0 |
| Wed 19 | 0 | 0.0 | 135 ms | 0 |
| Wed 21 | 0 | 0.0 | 113 ms | 0 |
| Wed 23 | 0 | 0.0 | 98 ms | 0 |
| Thu 02 | 0 | 0.0 | 116 ms | 0 |
| Thu 04 | 0 | 0.0 | 107 ms | 0 |
| Thu 06 | 0 | 0.0 | 85 ms | 0 |
| Thu 08 | 0 | 0.0 | 116 ms | 0 |
| Thu 10 | 0 | 0.0 | 91 ms | 0 |
| Thu 12 | 0 | 0.0 | 72 ms | 0 |
| Thu 14 | 0 | 0.0 | 75 ms | 0 |
| Thu 16 | 0 | 0.0 | 122 ms | 0 |
| Thu 18 | 0 | 0.0 | 51 ms | 0 |
| Thu 20 | 0 | 0.0 | 67 ms | 0 |
| Thu 22 | 0 | 0.0 | 67 ms | 0 |
| Fri 00 | 0 | 0.0 | 112 ms | 0 |
| Fri 02 | 0 | 0.0 | 100 ms | 0 |
| Fri 04 | 0 | 0.0 | 103 ms | 0 |
| Fri 06 | 0 | 0.0 | 169 ms | 0 |
| Fri 09 | 0 | 0.0 | 67 ms | 0 |
| Fri 11 | 0 | 0.0 | 71 ms | 0 |
| Fri 13 | 0 | 0.0 | 353 ms | 0 |
| Fri 15 | 0 | 0.0 | 145 ms | 0 |
| Fri 17 | 0 | 0.0 | 188 ms | 0 |
| Fri 18 | 0 | 0.0 | 60 ms | 0 |
| Fri 20 | 0 | 0.0 | 227 ms | 0 |
| Fri 22 | 0 | 0.0 | 106 ms | 0 |
| Sat 00 | 0 | 0.0 | 89 ms | 0 |
| Sat 02 | 0 | 0.0 | 39 ms | 0 |
| Sat 04 | 0 | 0.0 | 60 ms | 0 |
| Sat 06 | 0 | 0.0 | 112 ms | 0 |
| Sat 08 | 0 | 0.0 | 113 ms | 0 |
| Sat 10 | 0 | 0.0 | 54 ms | 0 |
| Sat 12 | 0 | 0.0 | 89 ms | 0 |
| Sat 13 | 0 | 0.0 | 86 ms | 0 |
| Sat 16 | 0 | 0.0 | 74 ms | 0 |
| Sat 18 | 0 | 0.0 | 189 ms | 0 |
| Sat 20 | 0 | 0.0 | 89 ms | 0 |
| Sat 23 | 0 | 0.0 | 66 ms | 0 |
| Sun 01 | 0 | 0.0 | 54 ms | 0 |
| Sun 03 | 0 | 0.0 | 60 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 10 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Be My Eyes 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 Be My Eyes goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track Be My Eyes (bemyeyes.com) as part of the Entertainment group. Experience the benefits of accessible technology with Be My Eyes. Connect with volunteers for real-time assistance via video.
Be My Eyes publishes an official status page at status.bemyeyes.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 90 ms average, 54–189 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 Be My Eyes incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
90 ms on average over the last 24 hours (54–189 ms).
Yes, at https://status.bemyeyes.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report Be My Eyes here at once, the problem is on Be My Eyes'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 Be My Eyes. 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.