Dizzion experienced a major incident on October 20, 2025 affecting Frame Platform (use.difr.com), lasting 21h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Oct 20, 2025, 09:55 AM UTC
Frame services on the USE backplane experienced an outage due to a major incident affecting multiple AWS services in the US-EAST-1 (N. Virginia) region. We are observing signs of recovery and closely monitoring system performance to ensure full restoration.
- monitoring Oct 20, 2025, 10:18 AM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 11:10 AM UTC
The Dizzion USE-platform has recovered, and we are continuing to monitor for any remaining issues. According to AWS, the underlying DNS issue has been fully resolved, and most services are now operating normally. However, while the majority of operations have recovered, requests to launch new EC2 instances in the US-EAST-1 Region may still experience elevated error rates.
- monitoring Oct 20, 2025, 12:26 PM UTC
The Dizzion USE-platform remains stable, and we are continuing to actively monitor the environment. AWS is still working to address the ongoing issue affecting the launch of new EC2 instances in the US-EAST-1 Region. We will continue to monitor the situation closely and provide further updates.
- monitoring Oct 20, 2025, 02:07 PM UTC
AWS continues to work toward fully resolving the issue affecting the launch of new EC2 instances in the US-EAST-1 Region. We are actively monitoring the situation and will provide additional updates as they become available.
- monitoring Oct 20, 2025, 03:37 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 07:20 PM UTC
AWS continues to work toward fully resolving the issue affecting the launch of new EC2 instances in the US-EAST-1 Region. Progress can be viewed directly by visiting the AWS status page: https://health.aws.amazon.com/health/status We are continuing to monitor for any further issues.
- resolved Oct 21, 2025, 06:56 AM UTC
This incident has been resolved.