Resolved after 16 hours 14 minutes, affecting Web Application and Public API and 1 more, on October 20, 2025.
Error rates have decreased substantially but remain above zero. Our team is now working on recovering lost connections.
Affected components
Update timeline
- monitoring Oct 20, 2025, 07:37 AM UTC
One of our upstream providers has reported experiencing several technical issues. We are monitoring the development of the situation.
- monitoring Oct 20, 2025, 07:45 AM UTC
We are monitoring updates at: https://health.aws.amazon.com/health/status
- monitoring Oct 20, 2025, 08:49 AM UTC
We are seeing signs of recovery in several of our services. We will continue monitoring.
- monitoring Oct 20, 2025, 09:29 AM UTC
The service is operational again but we will continue monitoring for updates in case issues recur.
- identified Oct 20, 2025, 02:13 PM UTC
We have detected a second wave of elevated errors coming from AWS that's affecting our service.
- monitoring Oct 20, 2025, 03:47 PM UTC
We continue monitoring the situation with our upstream provider, AWS.
- monitoring Oct 20, 2025, 05:25 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 20, 2025, 06:18 PM UTC
We are seeing some signs of recovery. Internal routing between services is still degraded but started being operational again.
- monitoring Oct 20, 2025, 08:47 PM UTC
Error rates have decreased substantially but remain above zero. Our team is now working on recovering lost connections.
- resolved Oct 20, 2025, 11:51 PM UTC
AWS is fully operational again. We are considering the incident resolved.
Your product runs on more than 2Chat
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services