Captivate Outage History

Captivate is up right now

Captivate had 8 outages in the last 2 years totaling 1h 11m of downtime, averaging 0.3 incidents per month.

There were 8 Captivate outages since November 18, 2025 totaling 1h 11m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.captivatechat.ai

Major October 21, 2026

Livechat Gateway is down

Detected by Pingoru
Oct 21, 2026, 04:43 AM UTC
Resolved
Oct 21, 2026, 04:43 AM UTC
Duration
–
Timeline · 2 updates
  1. investigating Oct 21, 2026, 10:02 AM UTC

    Livechat Gateway went down.

  2. resolved Oct 21, 2026, 10:08 AM UTC

    Livechat Gateway recovered.

Read the full incident report →

Major October 13, 2026

Main Page (https://www.captivatechat.ai) is down

Detected by Pingoru
Oct 13, 2026, 06:43 AM UTC
Resolved
Oct 13, 2026, 06:49 AM UTC
Duration
6m
Affected: Main Page (https://www.captivatechat.ai)
Timeline · 2 updates
  1. investigating Oct 13, 2026, 06:43 AM UTC

    Main Page (https://www.captivatechat.ai) went down.

  2. resolved Oct 13, 2026, 06:49 AM UTC

    Main Page (https://www.captivatechat.ai) recovered.

Read the full incident report →

Major September 30, 2026

Chatbot Gateway is down

Detected by Pingoru
Sep 30, 2026, 06:27 PM UTC
Resolved
Sep 30, 2026, 06:39 PM UTC
Duration
12m
Timeline · 2 updates
  1. investigating Sep 30, 2026, 06:27 PM UTC

    Chatbot Gateway went down.

  2. resolved Sep 30, 2026, 06:39 PM UTC

    Chatbot Gateway recovered.

Read the full incident report →

Major August 28, 2026

Attendee is down

Detected by Pingoru
Aug 28, 2026, 11:25 PM UTC
Resolved
Aug 28, 2026, 11:31 PM UTC
Duration
6m
Affected: Attendee
Timeline · 2 updates
  1. investigating Aug 28, 2026, 11:25 PM UTC

    Attendee went down.

  2. resolved Aug 28, 2026, 11:31 PM UTC

    Attendee recovered.

Read the full incident report →

Major July 29, 2026

Channel Gateway, Livechat Gateway, and 3 other services are down

Detected by Pingoru
Jul 29, 2026, 11:48 AM UTC
Resolved
Jul 29, 2026, 11:54 AM UTC
Duration
6m
Timeline · 7 updates
  1. investigating Jul 29, 2026, 11:48 AM UTC

    Channel Gateway and Livechat Gateway went down.

  2. investigating Jul 29, 2026, 11:49 AM UTC

    Slack went down.

  3. investigating Jul 29, 2026, 11:49 AM UTC

    Microsoft Teams and Microsoft Teams Webhook went down.

  4. resolved Jul 29, 2026, 11:54 AM UTC

    Slack recovered.

  5. investigating Jul 29, 2026, 11:54 AM UTC

    Microsoft Teams Webhook recovered.

  6. investigating Jul 29, 2026, 11:54 AM UTC

    Microsoft Teams recovered.

  7. investigating Jul 29, 2026, 11:54 AM UTC

    Channel Gateway and Livechat Gateway recovered.

Read the full incident report →

Major July 7, 2026

Chatbot Gateway, Channel Gateway, and 3 other services are down

Detected by Pingoru
Jul 07, 2026, 07:09 PM UTC
Resolved
Jul 07, 2026, 07:16 PM UTC
Duration
7m
Timeline · 6 updates
  1. investigating Jul 07, 2026, 07:09 PM UTC

    Livechat Gateway went down.

  2. investigating Jul 07, 2026, 07:09 PM UTC

    Chatbot Gateway and Channel Gateway went down.

  3. investigating Jul 07, 2026, 07:10 PM UTC

    Microsoft Teams Webhook went down.

  4. investigating Jul 07, 2026, 07:10 PM UTC

    Microsoft Teams went down.

  5. resolved Jul 07, 2026, 07:16 PM UTC

    Microsoft Teams Webhook recovered.

  6. investigating Jul 07, 2026, 07:16 PM UTC

    Chatbot Gateway, Channel Gateway, Livechat Gateway, and 1 other resource recovered.

Read the full incident report →

Major November 18, 2025

Cloudflare DNS Outage

Detected by Pingoru
Nov 18, 2025, 11:24 AM UTC
Resolved
Nov 18, 2025, 11:24 AM UTC
Duration
–
Timeline · 1 update
  1. investigating Nov 18, 2025, 11:24 AM UTC

    Update: All services are currently operating normally. We are experiencing issues related to an ongoing Cloudflare global outage and are actively monitoring the situation. We will continue to provide updates as more information becomes available. For details, please refer to Cloudflare’s status page: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We apologize for any inconvenience this may have caused and appreciate your patience.

Read the full incident report →