Captivated incident

AWS Outage Impacting Services

Minor Resolved View vendor source →

Captivated experienced a minor incident on October 20, 2025 affecting app.captivated.works and Message Sending and 1 more component, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 03:31 PM UTC
Resolved
Oct 21, 2025, 03:46 PM UTC
Duration
1d
Detected by Pingoru
Oct 20, 2025, 03:31 PM UTC

Affected components

app.captivated.worksMessage SendingMessage Receiving

Update timeline

  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.