Captivated had 5 outages in the last 2 years totaling 32h 56m of downtime — averaging 0.2 incidents per month.
There were 5 Captivated outages since July 24, 2025 totaling 32h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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.
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.
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.
This incident has been resolved.
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.
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.
We are currently experiencing degraded performance in parts of the application due to increased load on our search infrastructure. This may result in slower loading times, delayed search results, or occasional timeouts. Our team has identified the issue and is actively working on a resolution. We appreciate your patience and will provide updates as we make progress.
We’ve implemented a fix to address degraded performance with searching. Initial testing shows improved results, and we are actively monitoring to ensure continued stability.
This incident has been resolved.