Vendor Status Watch

← all vendors

Blip status history

Current state: operational — “All Systems Operational” per https://status.blip.ai (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

3incidents, last 30 days
7incidents, last 90 days
32incidents on record
Incidents per week, last 12 weeks:

How long do Blip incidents last?

2.1 hmedian incident duration32 measured
21.8 h90th percentile1 in 10 ran longer
2.5 hmedian, major/critical only10 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-15 13:03 UTCActive Message Sending Instabilityresolvednone1 h 30 min
2026-08-24 11:50 UTCBlip Portal and Desk Loading Issuesresolvednone1 h 44 min
2026-08-20 12:50 UTCWidespread Failure in Sending and Receiving Emailsresolvedcritical9 h 47 min
2026-08-06 20:47 UTCSlowness or delays in bot responsesresolvedminor13 min
2026-08-05 15:58 UTCMessage visibility issues in Blip Desk and Portalresolvedminor24 h 49 min
2026-07-24 21:00 UTCPausa temporária no envio de mensagens via BSUIDresolvednone18 d 22 h
2026-06-23 23:09 UTCSlow message sending and media sending failuresresolvedmajor1 h 30 min
2026-06-16 14:40 UTCWhatsApp Media Sending Instabilityresolvedminor4 h 23 min
2026-06-12 13:30 UTCDegradation in WhatsApp message delivery serviceresolvedminor4 h 45 min
2026-06-02 01:50 UTCDegradation in WhatsApp message delivery serviceresolvednone20 min
2026-05-05 18:51 UTCDegradation in platform servicesresolvednone13 min
2026-05-05 16:54 UTCDegradation in platform servicesresolvednone15 min
2026-05-05 14:52 UTCDegradation in platform servicesresolvednone3 min
2026-04-22 13:37 UTCInstability in AI Agents Responsesresolvedcritical21 h 47 min
2026-04-08 12:26 UTCTicket Distribution Instability on Blip Deskresolvedcritical1 h 39 min
2026-04-02 11:19 UTCAI Response Failure on Blip Studio Botsresolvedcritical2 h 20 min
2026-03-02 00:56 UTCBlipChat [Low performance]resolvedmajor23 min
2026-02-23 13:19 UTCContact Search Failure on Botsresolvedcritical6 h 42 min
2026-02-03 19:21 UTCWhatsApp [Low performance]resolvednone38 min
2026-01-20 13:31 UTCSlow Loading Time - Contact Tabresolvedminor2 d 3 h
2026-01-19 11:40 UTCProblem loading contactsresolvedminor13 h 19 min
2025-12-19 12:33 UTCInstability on the blip portal due to a failure in the provider's serversresolvedminor1 h 41 min
2025-12-11 14:26 UTCFailure in the AI applicationresolvednone0 min
2025-12-10 13:46 UTCLentidão no fluxo de mensagens do Whatsappresolvedminor2 h 14 min
2025-12-10 12:15 UTCLentidão para acesso ao portal e deskresolvedminor49 min
2025-12-05 09:24 UTCInstability on the Blip portal due to a provider outage.resolvedminor1 h 36 min
2025-12-04 11:30 UTCProblema na busca pelo histórico de contatosresolvedmajor2 h 40 min
2025-11-24 13:12 UTCProblema na busca por contatosresolvedminor6 h 15 min
2025-11-06 11:00 UTCDuplicate messages being delivered on Whatsappresolvedminor4 h 27 min
2025-10-29 16:18 UTCPortal and Desk Outageresolvedcritical7 h 46 min
2025-08-30 21:30 UTCConversational Flow [Low Performace]resolvedmajor1 h 56 min
2025-08-22 11:30 UTCBlip Desk & Growth [Low performance]resolvedminor4 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
}