Live / Weave / Incident
Weave: Weave Chat
Weave · getweave.comResolved2026-10-27 16:05 UTC
Public — what happened
Summary
Weave said its chat feature could not be reached through the contact us page, though it still worked through the question mark widget at the lower right of the home page on weavehelp.com. The report began on 2026-10-26 at 22:50 UTC, when the company said it had already identified the problem and was working on a fix. By 23:40 UTC Weave said a fix was in place and it was monitoring the results, and the incident was marked resolved on 2026-10-27 at 16:05.
Timeline
- Started — 2026-10-26 22:50 UTC
- Identified — 2026-10-26 22:50 UTC
- Monitoring — 2026-10-26 23:40 UTC
- Resolved — 2026-10-27 16:05 UTC · 17h 14m 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 Weave 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 Weave: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Weave report →
More from Weave
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.