Blip incident

Active Message Sending Instability

Notice Resolved View vendor source →

Blip experienced a notice incident on September 15, 2026 affecting Agendador, lasting 1h 30m. The incident has been resolved; the full update timeline is below.

Started
Sep 15, 2026, 01:03 PM UTC
Resolved
Sep 15, 2026, 02:34 PM UTC
Duration
1h 30m
Detected by Pingoru
Sep 15, 2026, 01:03 PM UTC

Affected components

Agendador

Update timeline

  1. investigating Sep 15, 2026, 01:29 PM UTC

    We are investigating an issue that may be causing difficulties when sending active messages, with some messages appearing as "NOT PROCESSED". Technical teams are actively analyzing the situation. The next update is expected within 30 minutes or as soon as new information becomes available.

  2. investigating Sep 15, 2026, 01:48 PM UTC

    We are continuing to investigate an issue that may be causing difficulties when sending active messages, with some messages appearing as "NOT PROCESSED". Technical teams are performing sending tests and analyzing information to identify the cause of the processing errors. The next update is expected within 30 minutes or as soon as new information becomes available.

  3. identified Sep 15, 2026, 02:07 PM UTC

    We are continuing to investigate an issue that may be causing difficulties when sending active messages, with some messages appearing as "NOT PROCESSED". Technical teams are performing sending tests and analyzing information to identify the cause of the processing errors. The next update is expected within 30 minutes or as soon as new information becomes available.

  4. resolved Sep 15, 2026, 02:37 PM UTC

    The incident has been resolved. The issue was caused by a peak in the volume of individual campaign sends, which overloaded message processing and caused slowness. Adjustments were applied to improve processing performance, reduce excessive resource consumption, and separate individual and batch campaign processing. The service is now fully normalized.