Blip status history
Current state: operational — “All Systems Operational” per https://status.blip.ai (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Blip incidents last?
From 32 incidents with a vendor-posted start and resolve time. Longest on record: Pausa temporária no envio de mensagens via BSUID — 18.9 days (2026-07-24 21:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (32)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-15 13:03 UTC | Active Message Sending Instability | resolved | none | 1 h 30 min |
| 2026-08-24 11:50 UTC | Blip Portal and Desk Loading Issues | resolved | none | 1 h 44 min |
| 2026-08-20 12:50 UTC | Widespread Failure in Sending and Receiving Emails | resolved | critical | 9 h 47 min |
| 2026-08-06 20:47 UTC | Slowness or delays in bot responses | resolved | minor | 13 min |
| 2026-08-05 15:58 UTC | Message visibility issues in Blip Desk and Portal | resolved | minor | 24 h 49 min |
| 2026-07-24 21:00 UTC | Pausa temporária no envio de mensagens via BSUID | resolved | none | 18 d 22 h |
| 2026-06-23 23:09 UTC | Slow message sending and media sending failures | resolved | major | 1 h 30 min |
| 2026-06-16 14:40 UTC | WhatsApp Media Sending Instability | resolved | minor | 4 h 23 min |
| 2026-06-12 13:30 UTC | Degradation in WhatsApp message delivery service | resolved | minor | 4 h 45 min |
| 2026-06-02 01:50 UTC | Degradation in WhatsApp message delivery service | resolved | none | 20 min |
| 2026-05-05 18:51 UTC | Degradation in platform services | resolved | none | 13 min |
| 2026-05-05 16:54 UTC | Degradation in platform services | resolved | none | 15 min |
| 2026-05-05 14:52 UTC | Degradation in platform services | resolved | none | 3 min |
| 2026-04-22 13:37 UTC | Instability in AI Agents Responses | resolved | critical | 21 h 47 min |
| 2026-04-08 12:26 UTC | Ticket Distribution Instability on Blip Desk | resolved | critical | 1 h 39 min |
| 2026-04-02 11:19 UTC | AI Response Failure on Blip Studio Bots | resolved | critical | 2 h 20 min |
| 2026-03-02 00:56 UTC | BlipChat [Low performance] | resolved | major | 23 min |
| 2026-02-23 13:19 UTC | Contact Search Failure on Bots | resolved | critical | 6 h 42 min |
| 2026-02-03 19:21 UTC | WhatsApp [Low performance] | resolved | none | 38 min |
| 2026-01-20 13:31 UTC | Slow Loading Time - Contact Tab | resolved | minor | 2 d 3 h |
| 2026-01-19 11:40 UTC | Problem loading contacts | resolved | minor | 13 h 19 min |
| 2025-12-19 12:33 UTC | Instability on the blip portal due to a failure in the provider's servers | resolved | minor | 1 h 41 min |
| 2025-12-11 14:26 UTC | Failure in the AI application | resolved | none | 0 min |
| 2025-12-10 13:46 UTC | Lentidão no fluxo de mensagens do Whatsapp | resolved | minor | 2 h 14 min |
| 2025-12-10 12:15 UTC | Lentidão para acesso ao portal e desk | resolved | minor | 49 min |
| 2025-12-05 09:24 UTC | Instability on the Blip portal due to a provider outage. | resolved | minor | 1 h 36 min |
| 2025-12-04 11:30 UTC | Problema na busca pelo histórico de contatos | resolved | major | 2 h 40 min |
| 2025-11-24 13:12 UTC | Problema na busca por contatos | resolved | minor | 6 h 15 min |
| 2025-11-06 11:00 UTC | Duplicate messages being delivered on Whatsapp | resolved | minor | 4 h 27 min |
| 2025-10-29 16:18 UTC | Portal and Desk Outage | resolved | critical | 7 h 46 min |
| 2025-08-30 21:30 UTC | Conversational Flow [Low Performace] | resolved | major | 1 h 56 min |
| 2025-08-22 11:30 UTC | Blip Desk & Growth [Low performance] | resolved | minor | 4 h 25 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Blip with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"blip"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}