Live  /  Weave  /  Incident

Weave: Slowness in loading filters for auto messages.

Weave · getweave.comMinor incidentResolved2026-10-21 18:38 UTC
Public — what happened

Summary

Weave reported a minor issue that began at 17:15 UTC on 2026-10-21, in which the filters on its auto-message settings were taking a long time to load. The company said this made the configuration page slow but did not affect messages being sent. Weave marked the incident resolved at 18:38 UTC the same day, and its posted text did not name a cause.

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 44, 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.