Captivated Outage History

Captivated is up right now

Captivated had 5 outages in the last 2 years totaling 28h 16m of downtime — averaging 0.2 incidents per month.

There were 5 Captivated outages since September 29, 2025 totaling 28h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://captivated.statuspage.io

Notice July 30, 2026

Video Chat Service Disruption

Detected by Pingoru
Jul 30, 2026, 09:19 PM UTC
Resolved
Jul 31, 2026, 01:20 AM UTC
Duration
4h
Affected: app.captivated.works
Timeline · 4 updates
  1. investigating Jul 30, 2026, 09:19 PM UTC

    We're currently investigating an issue affecting video chats and related messaging features. Some users may experience failures when attempting to start or join video calls. Our team has identified the root cause and is working on a resolution. We'll post an update as soon as we have more information.

  2. monitoring Jul 31, 2026, 12:43 AM UTC

    We've applied a fix for the issue affecting video chats. We're currently monitoring to confirm full resolution and will update this page once we've verified the fix.

  3. monitoring Jul 31, 2026, 01:19 AM UTC

    This issue has been resolved and video chats are fully operational. We apologize for any inconvenience this may have caused.

  4. resolved Jul 31, 2026, 01:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 22, 2026

Downstream Provider Incident

Detected by Pingoru
May 22, 2026, 06:56 PM UTC
Resolved
May 21, 2026, 07:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 22, 2026, 06:56 PM UTC

    For a brief period of time, an isolated incident with a downstream provider resulted in a small subset of 10DLC Messages to fail to deliver as expected. Traffic has since recovered and we consider this incident resolved.

Read the full incident report →

Minor October 20, 2025

AWS Outage Impacting Services

Detected by Pingoru
Oct 20, 2025, 03:31 PM UTC
Resolved
Oct 21, 2025, 03:46 PM UTC
Duration
1d
Affected: app.captivated.worksMessage SendingMessage Receiving
Timeline · 4 updates
  1. investigating Oct 20, 2025, 03:31 PM UTC

    We are currently experiencing service disruptions due to an ongoing AWS outage affecting multiple regions. Our team is actively monitoring the situation and working to restore full functionality as quickly as possible. We’ll post additional updates here as more information becomes available.

  2. investigating Oct 20, 2025, 03:47 PM UTC

    Realtime Degradation — We’re investigating intermittent WebSocket disconnects linked to upstream cloud provider issues. You may see delayed/live updates fail to load. We’re rebalancing traffic now and will update when stabilized.

  3. monitoring Oct 20, 2025, 06:39 PM UTC

    Our metrics remain stable and AWS has indicated they have identified the issue and a fix. However, residual issues persist across several dependent vendors still recovering from the earlier outage. Traffic is flowing normally, though some requests may continue to experience intermittent latency or retries. We’ll continue to monitor until all upstream providers confirm full resolution.

  4. resolved Oct 21, 2025, 03:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 3, 2025

Deployment Regression: Contact Records Missing Phone Numbers

Detected by Pingoru
Oct 03, 2025, 12:23 PM UTC
Resolved
Oct 03, 2025, 12:23 PM UTC
Duration
—
Affected: app.captivated.worksMessage Sending
Timeline · 1 update
  1. resolved Oct 03, 2025, 12:23 PM UTC

    Between 11:00 PM ET on October 2 and 8:20 AM ET on October 3, new contact records were not being created correctly. In some cases, contacts were saved without phone numbers. The issue was caused by a recent deployment. Once detected, we rolled out a fix to restore normal behavior. All new contacts created after 8:30 AM ET on October 3 are persisting correctly. Some contacts created during the incident window may be incomplete or missing. Unfortunately, phone numbers entered during this time were not recoverable. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Minor September 29, 2025

API message Sends

Detected by Pingoru
Sep 29, 2025, 01:15 PM UTC
Resolved
Sep 29, 2025, 01:15 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 29, 2025, 04:23 PM UTC

    Between late Friday, September 26, and Monday morning, September 29, API-originated messages (including scheduled sends) failed to deliver due to a defect introduced in a deployment. The issue did not result in data loss, but messages attempted during this period were not sent. Service was fully restored on Monday morning. We apologize for the disruption and are implementing additional safeguards to prevent similar issues in the future.

Read the full incident report →