Historial de interrupciones de Trifacta

1. September 3, 2026 at 10:24 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta las conexiones con el Plano de Datos de Alteryx en la región US1. Un proveedor de servicios de terceros está experimentando un problema que está afectando la conectividad de Plane de Datos de Alteryx. Nuestro equipo está monitoreando activamente la situación y trabajando para minimizar el impacto. Proporcionaremos actualizaciones adicionales a medida que se disponga de más información.

2. September 3, 2026 at 10:48 PM UTCmonitoring

   Estamos viendo señales de recuperación para conexiones con Alteryx Data Plane en la región US1 ya que el proveedor de servicios de terceros continúa recuperándose. Nuestro equipo está monitoreando activamente la situación y la conectividad de Plane de Datos Alteryx a medida que regresa a la normalidad. Seguiremos monitoreando para la recuperación completa y proporcionaremos actualizaciones adicionales a medida que se disponga de más información.

3. September 3, 2026 at 10:49 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

4. September 4, 2026 at 8:26 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 15, 2026 at 9:21 PM UTCinvestigating

   Some users may experience delays or jobs appearing stuck when running file conversions in Designer Cloud. Our team is actively investigating the issue and working to restore normal performance as quickly as possible. We will share additional updates as more information becomes available.

2. June 16, 2026 at 1:03 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. June 16, 2026 at 1:05 PM UTCresolved

   Resolved.

1. May 25, 2026 at 6:52 AM UTCinvestigating

   We are currently investigating reports of slow login and application load performance in the US1 environment. Some users may experience delays accessing workspaces, loading the home screen, or using application features.

2. May 25, 2026 at 8:54 AM UTCinvestigating

   We are investigating elevated latency and login issues impacting some users in the US1 environment. Our teams are actively working to identify the root cause and mitigate the issue.

3. May 25, 2026 at 10:52 AM UTCidentified

   We have identified the issue and are actively working to resolve it. Some users may continue to experience intermittent latency or delays while recovery efforts are in progress.

4. May 25, 2026 at 2:59 PM UTCmonitoring

   We have resolved the issue at 11:30 AM UTC. We are continuing to closely monitor the environment to ensure stability.

5. May 26, 2026 at 7:53 AM UTCresolved

   The issue impacting login and application performance has been resolved.

1. May 4, 2026 at 6:45 PM UTCinvestigating

   We are currently investigating an issue in US1 that is impacting some Alteryx One customers. The impact to users would potentially be in pages related to assets, library and data sets. There is likely related to an issue with a 3rd party provider.

2. May 4, 2026 at 11:55 PM UTCmonitoring

   We've implemented a fix and will continue to monitor the environment. If issues persist, please open a support case with Alteryx support. Thank you.

3. May 5, 2026 at 3:36 PM UTCmonitoring

   We're experiencing degraded performance in US1. Users may encounter slowness when navigating Alteryx One assets, library, and data sets.

4. May 7, 2026 at 2:51 PM UTCmonitoring

   We have deployed a fix to address performance issues affecting datasets, workflows, and job history. System performance has improved, and we are continuing to monitor to ensure full recovery.

5. May 12, 2026 at 6:44 PM UTCresolved

   This incident has been resolved.

1. May 4, 2026 at 5:21 PM UTCinvestigating

   We are currently investigating authentication failures in US1. We will provide updates shortly.

2. May 4, 2026 at 8:53 PM UTCresolved

   We've identified the problem and have determined impact to only a small subset of users. In the event issues continue, please open a support case with Alteryx support. Thank you.

1. April 2, 2026 at 9:11 PM UTCidentified

   New assets in Designer Cloud are delayed when viewing in Library.

2. April 2, 2026 at 9:23 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. April 2, 2026 at 9:36 PM UTCresolved

   This incident has been resolved.

1. March 21, 2026 at 7:53 AM UTCinvestigating

   We are currently investigating this issue

2. March 21, 2026 at 7:56 AM UTCinvestigating

   We are continuing to investigate this issue.

3. March 21, 2026 at 10:06 AM UTCidentified

   We have identified the issue impacting AU1 plan jobs and are actively working with the GCP support team to resolve it. Further updates will be shared as progress is made.

4. March 21, 2026 at 10:15 AM UTCidentified

   The issue has been identified, and a fix is being implemented

5. March 21, 2026 at 10:17 AM UTCmonitoring

   The issue impacting AU1 plan jobs has been resolved. We will continue to monitor the system to ensure stability.

6. March 21, 2026 at 11:13 AM UTCresolved

   The issue impacting AU1 plan jobs has been resolved. This was related to a Google Kubernetes Engine (GKE) incident in australia-southeast1, where network traffic throttling between internal services caused disruptions to cluster operations; the issue has since been mitigated by Google.

1. March 20, 2026 at 6:24 PM UTCinvestigating

   We’re aware of an issue impacting the AU1 region (https://au1.alteryxcloud.com/) and are currently investigating. We will be providing updates as soon as we have more information.

2. March 20, 2026 at 7:29 PM UTCidentified

   There is an ongoing Google Cloud incident in the region that is directly related to the AlteryxCloud incident.

3. March 20, 2026 at 7:40 PM UTCmonitoring

   Au1 environment is back up and running. We are still monitoring and confirming all functionality. Also waiting on Google incident to be fully resolved.

4. March 20, 2026 at 10:06 PM UTCresolved

   This incident has been resolved.

1. February 11, 2026 at 12:22 PM UTCinvestigating

   We are currently investigating issues with us1.alteryxcloud.com

2. February 11, 2026 at 2:31 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. February 11, 2026 at 2:31 PM UTCresolved

   This incident has been resolved.

1. January 22, 2026 at 8:53 PM UTCinvestigating

   We are currently investigating login issues in all production regions.

2. January 22, 2026 at 9:30 PM UTCidentified

   We've identified our Alteryx One SSO vendor is currently experiencing a service disruption as a result of multiple Microsoft 365 service disruptions. This may cause degraded functionality or access to Alteryx One. We're monitoring the incident closely and will share updates as they become available (last update: Jan 22, 2026 9:11 PM UTC).

3. January 23, 2026 at 7:02 AM UTCidentified

   The issue with our Alteryx One SSO vendor, caused by upstream Microsoft 365 service disruptions, has now been resolved on their end. Services are operating normally, and OTP delivery has been verified as successful. We will continue to monitor the situation closely for a period of time before marking the incident as fully resolved.

4. January 23, 2026 at 7:04 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. January 23, 2026 at 8:40 AM UTCresolved

   The issue impacting Alteryx One SSO, caused by upstream Microsoft 365 service disruptions, has been fully resolved. Following a monitoring period, all services are operating normally, and OTP delivery is functioning as expected. This incident is now resolved.

1. January 7, 2026 at 10:59 PM UTCinvestigating

   We're actively investigating latency issues in US1. Updates will be provided shortly.

2. January 8, 2026 at 6:10 PM UTCresolved

   This incident has been resolved.

1. November 18, 2025 at 2:40 PM UTCidentified

   The issue has been identified and a fix is being implemented.

2. November 19, 2025 at 10:02 AM UTCresolved

   This incident has been resolved.

1. October 29, 2025 at 5:19 PM UTCidentified

   We are currently aware of an issue with a third-party vendor that is impacting authentication services. As a result, some users may be unable to log in at this time. We are monitoring the vendor’s recovery efforts and will provide updates as they become available.

2. October 29, 2025 at 7:47 PM UTCmonitoring

   The third-party vendor has resolved the issue causing login failures. Logins are now functioning normally, and we are monitoring the situation to ensure continued stability.

3. October 30, 2025 at 3:58 PM UTCresolved

   This incident has been resolved.

1. October 16, 2025 at 9:23 AM UTCinvestigating

   We are currently investigating this issue. ` latest status: login works now, but there could be still minor outages caused by external services

2. October 16, 2025 at 12:01 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. October 16, 2025 at 12:02 PM UTCmonitoring

   We have confirmed normal access and login functionality for all users and will continue monitoring to ensure stability.

4. October 16, 2025 at 12:10 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. October 16, 2025 at 5:35 PM UTCresolved

   This incident has been resolved.

1. September 25, 2025 at 8:29 PM UTCmonitoring

   All attempts at Alteryx One license activation via online or offline methods are currently unavailable due to a vendor outage. Product access for licenses already activated is not affected. We recommend not assigning or removing licenses if avoidable until the issue is resolved

2. September 25, 2025 at 10:26 PM UTCmonitoring

   Our vendor has completed remediation and failover steps. License activation services for Alteryx One have been restored, and we are monitoring to confirm full stability.

3. September 25, 2025 at 11:21 PM UTCresolved

   This incident has been resolved.

1. August 14, 2025 at 10:12 PM UTCinvestigating

   We are currently experiencing elevated error rates, relating to job executions. We are actively working to resolve the issue.

2. August 14, 2025 at 11:06 PM UTCidentified

   We've identified the cause of error rates increasing in US1. The team is working to implement a fix.

3. August 14, 2025 at 11:14 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. August 14, 2025 at 11:22 PM UTCresolved

   This incident has been resolved.

1. July 14, 2025 at 5:06 PM UTCidentified

   Auto Insights in US1 is experiencing elevated error rates when in Datasets. We've identified the issue and are working towards a solution.

2. July 14, 2025 at 6:28 PM UTCmonitoring

   A fix has been implemented and Auto Insights is operational. We will continue to monitor the environment.

3. July 14, 2025 at 8:10 PM UTCresolved

   This incident has been resolved.

1. June 24, 2025 at 9:04 PM UTCidentified

   We've identified an issue when making connections to third party endpoints for customers in the US1 region. A fix has been implemented and we are actively monitoring the environment.

2. June 24, 2025 at 9:09 PM UTCmonitoring

   Services are stable. We'll continue to monitor the environment.

3. June 24, 2025 at 10:54 PM UTCresolved

   This incident has been resolved. Services are working as expected.

1. June 12, 2025 at 7:45 PM UTCinvestigating

   Customers may experience service interruptions for all regions due to Google Cloud Platform Outage. We are currently investigating further impact. For more information on the GCP outage, please refer to https://status.cloud.google.com/.

2. June 12, 2025 at 7:52 PM UTCmonitoring

   Customers may experience service interruptions for all regions due to Google Cloud Platform Outage. We are currently investigating further impact. For more information on the GCP outage, please refer to https://status.cloud.google.com/.

3. June 12, 2025 at 11:15 PM UTCresolved

   This incident has been resolved.

1. May 21, 2025 at 4:24 PM UTCinvestigating

   We're currently investigating login issues affecting the US1 region. Our team is working to resolve the problem and will provide updates as soon as possible.

2. May 21, 2025 at 4:29 PM UTCinvestigating

   Updated product statuses in the status page, investigation is still ongoing.

3. May 21, 2025 at 4:38 PM UTCinvestigating

   The issue has been identified and should be resolved soon.

4. May 21, 2025 at 5:57 PM UTCmonitoring

   A fix has been implemented and we will continue monitoring.

5. May 21, 2025 at 11:00 PM UTCresolved

   The incident has been resolved.