Live / Weave / Incident
Weave: Auto messaging
Weave · getweave.comMinor incidentResolved2026-10-07 23:09 UTC
Public — what happened
Summary
Weave said it was looking into reported problems with its automated messaging feature beginning at 16:52 UTC on October 7, 2026, and rated the incident as minor. The company did not say which customers were affected or what caused the problem. Weave reported putting a fix in place by 19:41 UTC and then watching how it performed, and the incident was marked resolved at 23:09 the same day.
Affected
Automated Schedule Reminders
Timeline
- Started — 2026-10-07 16:52 UTC
- Investigating — 2026-10-07 16:52 UTC (2 updates)
- Monitoring — 2026-10-07 19:41 UTC
- Resolved — 2026-10-07 23:09 UTC · 6h 17m 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 42, 2026, our weekly internet health report.