TitanX experienced a major incident on October 20, 2025 affecting TitanX Platform Status (app.titanx.io), lasting 1d 15h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2025, 06:49 AM UTC
Platform Monitoring Alert - AWS Service Disruption - October 20, 2025 Description Amazon Web Services (AWS) is experiencing service disruptions in their US-EAST-1 (Northern Virginia) region beginning at approximately 2:49 AM ET. While TitanX does not directly use AWS, many of our critical service providers rely on AWS infrastructure. Current Situation: AWS has publicly acknowledged increased error rates and latencies in the US-EAST-1 region affecting multiple services including DynamoDB. This is an actively developing situation with potential for widespread impact across thousands of applications globally. TitanX Platform Status: We are currently assessing potential impacts to our platform and services. Initial evaluation shows our primary infrastructure (Supabase) is hosted in US-WEST-1, not the affected US-EAST-1 region. However, we are monitoring all critical systems for indirect impacts. Services Being Assessed: We are evaluating potential impacts to our third-party service providers. What We're Doing: Our engineering team has been alerted and is actively monitoring all critical systems. We are tracking AWS status updates and evaluating our service providers for any downstream effects. We will implement workarounds or contingency measures as needed. AWS Status: Real-time AWS service health updates can be tracked at health.aws.amazon.com/health/status We will provide updates as we complete our impact assessment and as the AWS situation develops. If you experience any issues accessing the platform, please contact [email protected] immediately.
- resolved Oct 21, 2025, 10:01 PM UTC
Platform Monitoring Alert - AWS Service Disruption - RESOLVED - October 19-21, 2025 Description Amazon Web Services experienced a major regional outage in US-EAST-1 (Northern Virginia) lasting over 15 hours that affected thousands of services globally. TitanX experienced minimal impact and maintained operational status throughout the incident. Root Cause: AWS experienced a race condition in DynamoDB's DNS management automation system that caused cascading failures across multiple services in the US-EAST-1 region. This affected over 50,000 applications globally, including major platforms like Snapchat, Slack, Coinbase, and thousands of other AWS-dependent services. Timeline: - Oct 19, 11:49 PM PDT / Oct 20, 2:49 AM ET - AWS US-EAST-1 issues began - Oct 20, Throughout Day - Continuous monitoring; platform remained operational with manual workarounds where needed - Oct 21, 6:01 PM ET - All clear confirmed; no lingering platform impacts TitanX Impact: - Platform error spike detected between 3:00-7:00 AM ET on October 20, which self-resolved - Core platform functionality remained operational throughout the incident - A number of our thrid-party vendor experienced issues that we were able to manage operationally. - No customer-facing service interruptions occurred Why TitanX Was Minimally Affected: Our database infrastructure is not hosted in the affected US-EAST-1 (Northern Virginia) region. The AWS outage was specific to US-EAST-1, allowing our platform to maintain normal operations. Resolution: AWS has fully resolved the US-EAST-1 regional issues. All TitanX platform services are operating normally with no lingering impacts. Our team successfully implemented manual workarounds during the incident to ensure continuous service delivery. The TitanX platform experienced zero customer-facing service disruption during this major cloud infrastructure event. No action is required from customers.