Replicon incident
Performance Degradation in NA4, NA6, and NA8 – Linked to AWS Outage
Replicon experienced a minor incident on October 20, 2025 affecting na4 and na6 and 1 more component, lasting 12h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Oct 20, 2025, 10:37 AM UTC
Earlier today, AWS experienced an outage in one of its US East regions, impacting multiple AWS services as well as other platforms hosted on AWS. As a result, our status page was also temporarily unavailable, preventing us from posting timely updates. Starting at 7:10 AM UTC, we observed an elevated level of errors affecting customers hosted on our NA4, NA6, and NA8 tenant environments. This issue was directly related to the AWS outage. We are actively working with the AWS Support team to monitor their recovery efforts and ensure full service stability. Further updates will be shared as more information becomes available.
- monitoring Oct 20, 2025, 10:56 AM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 11:50 AM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 01:29 PM UTC
We are actively working with the AWS Support team to investigate and monitor their recovery efforts. Most services remain available, though some users may experience occasional disruptions. We are closely tracking progress to ensure full service stability and will share further updates as more information becomes available.
- monitoring Oct 20, 2025, 03:57 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 06:41 PM UTC
We continue to work with the AWS Support team as recovery efforts progress in the affected region. Most services remain available, though some users may still experience intermittent performance issues. We are closely monitoring the situation and will share further updates as recovery continues.
- monitoring Oct 20, 2025, 10:45 PM UTC
The system has now returned to normal operation. We are continuing to monitor for any further issues.
- resolved Oct 20, 2025, 10:58 PM UTC
This incident has been resolved.