Live  /  Blip  /  Incident

Blip: Active Message Sending Instability

Blip · blip.aiResolved2026-09-15 14:07 UTC
Public — what happened

Summary

Blip reported a problem affecting the sending of active messages, with some messages showing a "NOT PROCESSED" status. The issue began on 2026-09-15 at 13:03 UTC, and the company said its technical teams were running send tests and reviewing data to find what was causing the processing failures. Blip had not named a cause in its update, and the incident was marked resolved at 15:08 the same day.

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 Blip 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 Blip: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Blip report →

More from Blip

Covered in The Squid’s Ink, Week 39, 2026, our weekly internet health report.

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

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