Live / Homey / Incident
Homey: Homey Cloud London degraded performance
Homey · homey.appMinor incidentResolved2026-11-05 17:12 UTC
Public — what happened
Summary
Homey reported a minor incident described as degraded performance on its Homey Cloud London service, which began at 16:17 UTC on 2026-11-05. The company said it has identified the issue and is putting a fix in place. Homey did not say who was affected or give a cause, and the incident had not been marked resolved.
Affected
London
Timeline
- Started — 2026-11-05 16:17 UTC
- Identified — 2026-11-05 16:17 UTC
- Resolved — 2026-11-05 17:12 UTC · 54 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Homey against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Homey: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Homey report →
More from Homey
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.