Live / Weave / Incident
Weave: Message delays
Weave · getweave.comMinor incidentResolved2026-11-04 19:18 UTC
Public — what happened
Summary
Weave reported a minor incident involving delays in messages, which began on November 3, 2026 at 17:50 UTC. The company said it had found the cause and attributed it to one of its third-party providers, and it said it was working with that provider on a fix. By 00:37 UTC on November 4, Weave said text and picture messaging traffic was looking stable, and the incident was marked resolved at 19:18 that day.
Affected
SMS (texting) Service
Timeline
- Started — 2026-11-03 17:50 UTC
- Identified — 2026-11-03 17:50 UTC
- Monitoring — 2026-11-04 00:37 UTC
- Resolved — 2026-11-04 19:18 UTC · 25h 27m 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 46, 2026, our weekly internet health report.