Be My Eyes Outage History
4 incidents recorded over the last 365 days, 4 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Be My Eyes Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 1, 2026 | Call Connection Delays and Service DisruptionWe experienced degraded call routing between approximately 16:38 and 17:15 CEST (14:38–15:15 UTC) on June 1, 2026. During this time, some calls experienced delays of up to 60 seconds before connecting, and some callers… | 0 min | Resolved |
| Apr 16, 2026 | Service degradation - platform instabilityWe experienced a period of service degradation on April 14, 2026, affecting some users' ability to connect. The issue began around 19:22 UTC and was resolved by 20:30 UTC (approximately 60-70 minutes). Volunteer calls… | -2154 min | Resolved |
| Mar 10, 2026 | Call Push Notification Delivery Failure Affecting Be My Eyes CallsUsers were unable to connect calls due to call push notifications not being delivered to volunteers and some support agents among Service Directory partners. Timeline - 16:17 UTC: We detected elevated failure rates with… | 0 min | Resolved |
| Nov 18, 2025 | Connectivity Issues With Third-Party ProviderThe global internet outage impacting our systems has been resolved. Services have returned to normal, and users should no longer experience call or chat failures. Our engineering team has confirmed that all affected… | 2h 9m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Be My Eyes incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Be My Eyes Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Be My Eyes acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Be My Eyes outage in this window ran 2h 9m, against a mean recovery of 43 min. If you depend on Be My Eyes in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.