Live  /  Weave  /  Incident

Weave: Intermittent Outbound SMS Failures

Weave · getweave.comMinor incidentResolved2026-11-02 21:04 UTC
Public — what happened

Summary

Weave said it began investigating at 20:06 UTC on 2 November 2026 after some outbound text messages sent to numbers served by third parties were failing. The company described it as a minor issue affecting a small share of outbound SMS traffic, with affected messages possibly showing a "carrier refused" error. Weave's posted text did not name a cause, and the incident was marked resolved at 21:04.

Affected

SMS (texting) Service

As listed on Weave’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Weave status & history page.

Related: Weave status & history. SquidGrid is not affiliated with Weave.