Aug <var data-var='date'>17</var>, <var data-var='time'>14:24</var> UTC Resolved - The issue affecting access to the Upwind Console UI and API for a subset of customers has been resolved. Service has been fully restored, and we are continuing to monitor the system to ensure stability. Aug <var data-var='date'>17</var>, <var data-var='time'>12:52</var> UTC Investigating - We are investigating an issue affecting access to the Upwind Console UI and API for a subset of customers. Our team is actively investigating the root cause and working to restore normal service as quickly as possible.

Console UI Issue

Jul <var data-var='date'>16</var>, <var data-var='time'>10:30</var> UTC Resolved - The issue affecting access to the Upwind Console UI has been resolved. AWS continues to report an ongoing Amazon CloudFront service issue; however, it is no longer impacting the Upwind Console UI. We will continue to monitor the AWS incident until it is fully resolved. Jul <var data-var='date'>16</var>, <var data-var='time'>09:05</var> UTC Monitoring - We have implemented a workaround that restores access to the Upwind Console UI, and the issue is considered resolved on our side. The issue has been confirmed by AWS as an ongoing Amazon CloudFront service disruption. We will continue to monitor the AWS incident until it is fully resolved. Runtime protection remains unaffected. For the latest AWS updates, please refer to the AWS Health Dashboard: https://health.aws.amazon.com/health/status?path=open-issues Jul <var data-var='date'>16</var>, <var data-var='time'>08:32</var> UTC Investigating - We are investigating an issue affecting access to the Upwind Console UI only. The issue appears to be related to an AWS CloudFront service disruption. Runtime protection is not affected. Our team is actively working to verify the root cause and restore normal service as quickly as possible.

Jul <var data-var='date'> 3</var>, <var data-var='time'>14:00</var> UTC Resolved - The issue has been resolved. A subset of customers may have experienced issues accessing the Catalog Service through the UI and API. The impact was limited to the Catalog only. Runtime protection and detections were not affected. Our team has restored service and verified that the Catalog service is operating normally. We will continue to monitor the environment and review the incident to help prevent similar occurrences in the future. Jul <var data-var='date'> 3</var>, <var data-var='time'>12:15</var> UTC Identified - We have identified the issue affecting access to the Catalog through the UI and API for a subset of customers. Runtime protection and detections are not affected. Our team is implementing a fix and working to restore full functionality as quickly as possible. Jul <var data-var='date'> 3</var>, <var data-var='time'>11:45</var> UTC Investigating - We are investigating an issue affecting access to the Catalog through the UI and API for a subset of customers. Runtime protection and detections are not affected. Our team is actively working to identify the root cause and restore normal service as quickly as possible.

Catalog Service UI and API Degradation

Nov <var data-var='date'>11</var>, <var data-var='time'>15:26</var> UTC Resolved - The issue has been fully resolved by the team, and the system is fully operational. Nov <var data-var='date'>11</var>, <var data-var='time'>15:10</var> UTC Identified - The issue has been identified as a temporary problem with the API service, affecting login and several other operations for a subset of customers. Nov <var data-var='date'>11</var>, <var data-var='time'>15:07</var> UTC Investigating - We are investigating reports of errors returning from our Console and API, impacting a limited number of customers.

Console & API Errors - Partial Service Degradation

Oct <var data-var='date'>20</var>, <var data-var='time'>22:01</var> UTC Resolved - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>09:20</var> UTC Monitoring - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>07:25</var> UTC Identified - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>07:20</var> UTC Investigating - 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.

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

Jun <var data-var='date'>17</var>, <var data-var='time'>10:36</var> UTC Resolved - We’ve resolved the connectivity issue—services are now fully operational Jun <var data-var='date'>17</var>, <var data-var='time'>10:25</var> UTC Investigating - We’re currently investigating connectivity issues affecting parts of our system. Our team is actively working on it and we expect resolution shortly.

Intermittent Connectivity Issues Under Investigation

Mar <var data-var='date'>25</var>, <var data-var='time'>18:58</var> UTC Resolved - The issue with our authentication provider (Auth0) has been resolved. Access to the Upwind platform has been fully restored, and users can now log in as expected. Thank you for your patience. Mar <var data-var='date'>25</var>, <var data-var='time'>18:16</var> UTC Identified - We’re currently experiencing an authentication issue that is preventing users from logging into the Upwind platform. The root cause is an outage with our identity provider, Auth0. Our R&D team is actively investigating the issue in collaboration with the Auth0 team to resolve it as quickly as possible. We’ll provide updates as soon as we have more information. If you have any urgent concerns, please reach out to our support team. Thank you for your patience and understanding.

Authentication Service Outage Impacting Login

Jul <var data-var='date'> 1</var>, <var data-var='time'>06:53</var> UTC Resolved - The login issue for SSO SAML customers has been resolved. All functionalities are now operating normally. Jul <var data-var='date'> 1</var>, <var data-var='time'>04:09</var> UTC Identified - We are currently experiencing login issues affecting some of our customers using SSO

Is Upwind down?

Upwind status is UP

Lastest published events

Console UI Issue

Console UI Issue

Catalog Service UI and API Degradation

Upwind Services, Components and Regions

Recent Upwind events

Console UI Issue

Console UI Issue

Catalog Service UI and API Degradation

Console & API Errors - Partial Service Degradation

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

Intermittent Connectivity Issues Under Investigation