AWS us-east-1 Incident Causing Platform Instability and Connectivity Issues

Final update

AWS has confirmed that the us-east-1 regional issue causing elevated error rates and latencies between 06:49 AM UTC on October 20 and 22:01 PM UTC on October 20 has been fully mitigated. During this period, Upwind experienced limited impact - primarily login instability to the Console - while all other systems remained operational. Console access has been fully stable since 09:20 AM UTC, and we have continued monitoring until AWS declared full recovery. We appreciate your patience throughout this event and remain committed to maintaining the reliability of our platform.

1. Resolved · Oct 20, 22:01 UTC
   AWS has confirmed that the us-east-1 regional issue causing elevated error rates and latencies between 06:49 AM UTC on October 20 and 22:01 PM UTC on October 20 has been fully mitigated. During this period, Upwind experienced limited impact - primarily login instability to the Console - while all other systems remained operational. Console access has been fully stable since 09:20 AM UTC, and we have continued monitoring until AWS declared full recovery. We appreciate your patience throughout this event and remain committed to maintaining the reliability of our platform.
2. Monitoring · Oct 20, 09:20 UTC
   Console login functionality has been restored, and access is now stable. The underlying AWS incident in us-east-1 is still ongoing, and our team continues to actively monitor system performance to ensure full stability. We'll share a final update once AWS confirms full regional recovery.
3. Identified · Oct 20, 07:25 UTC
   We've identified the issue as related to a regional outage in AWS us-east-1 region. Console login remains intermittently unavailable, while other platform components continue to operate normally. We're tracking AWS's recovery efforts and will provide updates as the situation evolves.
4. Investigating · Oct 20, 07:20 UTC
   We are currently investigating an issue impacting login functionality to the Upwind Console, originating from an ongoing AWS incident in the us-east-1 region. All other platform services remain fully operational at this time. Our team is actively monitoring and collaborating with AWS to identify the root cause.