AWS Infrastructure Incident

Incident Report for TextUs

Resolved

AWS has fully resolved the infrastructure issue in the US-EAST-1 region. All TextUs systems have recovered, and performance has returned to normal.

Our team has verified that all services are operating as expected, and no data was lost during this incident.

We will continue to monitor system health closely, but no further impact is expected at this time.
Posted Oct 20, 2025 - 15:52 MDT

Monitoring

AWS has implemented mitigations for the infrastructure issue impacting the US-EAST-1 region, and services are showing continued signs of recovery.

Most TextUs systems are now operating normally; however, some users may still experience slow performance as AWS completes its recovery and our systems stabilize.

Our engineering team continues to monitor performance closely and is working to ensure all systems return to full health.

You can follow AWS’s latest status at https://health.aws.amazon.com/health/status
Posted Oct 20, 2025 - 13:35 MDT

Update

Update – AWS is actively rolling out mitigations for the infrastructure issue affecting parts of the US-EAST-1 region. They’re seeing early signs of recovery in several Availability Zones, with continued work underway to restore the remaining zones.

Once AWS services are fully restored, our engineering team will begin bringing all TextUs systems back to a healthy state and validating end-to-end functionality before declaring the incident resolved.

You can follow AWS’s updates directly at https://health.aws.amazon.com/health/status.
Posted Oct 20, 2025 - 11:48 MDT

Identified

We are currently experiencing service degradation due to an ongoing incident impacting AWS infrastructure. This may result in intermittent errors, delayed message delivery, or reduced performance for some users.

You can monitor AWS’s status directly at https://health.aws.amazon.com/health/status.

We are actively monitoring the situation and will provide updates as AWS resolves the underlying issue.
Posted Oct 20, 2025 - 07:26 MDT
This incident affected: TextUs Application, TextUs Chrome Extension, and TextUs Mobile App.