Trifacta driftsforstyrrelser

1. 3. september 2026 kl. 22.24 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker forbindelserne til Alteryx Data Plane i US1-regionen. En tredjeparts tjenesteudbyder oplever i øjeblikket et problem, der påvirker Ateryx Data Plane forbindelse. Vores team overvåger situationen og arbejder på at minimere virkningen. Vi vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 3. september 2026 kl. 22.48 UTCmonitoring

   Vi ser tegn på opsving for forbindelser til Alteryx Data Plane i US1 regionen som tredjeparts tjenesteudbyder fortsætter med at inddrive. Vores team er aktivt at overvåge situationen og Alteryx Data Plane forbindelse som det vender tilbage til normal. Vi vil fortsætte med at overvåge for fuld inddrivelse og give yderligere opdateringer, når flere oplysninger bliver tilgængelige.

3. 3. september 2026 kl. 22.49 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

4. 4. september 2026 kl. 08.26 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. juni 2026 kl. 21.21 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. 16. juni 2026 kl. 01.03 UTCmonitoring

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

3. 16. juni 2026 kl. 13.05 UTCresolved

   Resolved.

1. 25. maj 2026 kl. 06.52 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. 25. maj 2026 kl. 08.54 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. 25. maj 2026 kl. 10.52 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. 25. maj 2026 kl. 14.59 UTCmonitoring

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

5. 26. maj 2026 kl. 07.53 UTCresolved

   The issue impacting login and application performance has been resolved.

1. 4. maj 2026 kl. 18.45 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. 4. maj 2026 kl. 23.55 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. 5. maj 2026 kl. 15.36 UTCmonitoring

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

4. 7. maj 2026 kl. 14.51 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. 12. maj 2026 kl. 18.44 UTCresolved

   This incident has been resolved.

1. 4. maj 2026 kl. 17.21 UTCinvestigating

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

2. 4. maj 2026 kl. 20.53 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. 2. april 2026 kl. 21.11 UTCidentified

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

2. 2. april 2026 kl. 21.23 UTCmonitoring

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

3. 2. april 2026 kl. 21.36 UTCresolved

   This incident has been resolved.

1. 21. marts 2026 kl. 07.53 UTCinvestigating

   We are currently investigating this issue

2. 21. marts 2026 kl. 07.56 UTCinvestigating

   We are continuing to investigate this issue.

3. 21. marts 2026 kl. 10.06 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. 21. marts 2026 kl. 10.15 UTCidentified

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

5. 21. marts 2026 kl. 10.17 UTCmonitoring

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

6. 21. marts 2026 kl. 11.13 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. 20. marts 2026 kl. 18.24 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. 20. marts 2026 kl. 19.29 UTCidentified

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

3. 20. marts 2026 kl. 19.40 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. 20. marts 2026 kl. 22.06 UTCresolved

   This incident has been resolved.

1. 11. februar 2026 kl. 12.22 UTCinvestigating

   We are currently investigating issues with us1.alteryxcloud.com

2. 11. februar 2026 kl. 14.31 UTCmonitoring

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

3. 11. februar 2026 kl. 14.31 UTCresolved

   This incident has been resolved.

1. 22. januar 2026 kl. 20.53 UTCinvestigating

   We are currently investigating login issues in all production regions.

2. 22. januar 2026 kl. 21.30 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. 23. januar 2026 kl. 07.02 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. 23. januar 2026 kl. 07.04 UTCmonitoring

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

5. 23. januar 2026 kl. 08.40 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. 7. januar 2026 kl. 22.59 UTCinvestigating

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

2. 8. januar 2026 kl. 18.10 UTCresolved

   This incident has been resolved.

1. 18. november 2025 kl. 14.40 UTCidentified

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

2. 19. november 2025 kl. 10.02 UTCresolved

   This incident has been resolved.

1. 29. oktober 2025 kl. 17.19 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. 29. oktober 2025 kl. 19.47 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. 30. oktober 2025 kl. 15.58 UTCresolved

   This incident has been resolved.

1. 16. oktober 2025 kl. 09.23 UTCinvestigating

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

2. 16. oktober 2025 kl. 12.01 UTCidentified

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

3. 16. oktober 2025 kl. 12.02 UTCmonitoring

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

4. 16. oktober 2025 kl. 12.10 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 16. oktober 2025 kl. 17.35 UTCresolved

   This incident has been resolved.

1. 25. september 2025 kl. 20.29 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. 25. september 2025 kl. 22.26 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. 25. september 2025 kl. 23.21 UTCresolved

   This incident has been resolved.

1. 14. august 2025 kl. 22.12 UTCinvestigating

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

2. 14. august 2025 kl. 23.06 UTCidentified

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

3. 14. august 2025 kl. 23.14 UTCmonitoring

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

4. 14. august 2025 kl. 23.22 UTCresolved

   This incident has been resolved.

1. 14. juli 2025 kl. 17.06 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. 14. juli 2025 kl. 18.28 UTCmonitoring

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

3. 14. juli 2025 kl. 20.10 UTCresolved

   This incident has been resolved.

1. 24. juni 2025 kl. 21.04 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. 24. juni 2025 kl. 21.09 UTCmonitoring

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

3. 24. juni 2025 kl. 22.54 UTCresolved

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

1. 12. juni 2025 kl. 19.45 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. 12. juni 2025 kl. 19.52 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. 12. juni 2025 kl. 23.15 UTCresolved

   This incident has been resolved.

1. 21. maj 2025 kl. 16.24 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. 21. maj 2025 kl. 16.29 UTCinvestigating

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

3. 21. maj 2025 kl. 16.38 UTCinvestigating

   The issue has been identified and should be resolved soon.

4. 21. maj 2025 kl. 17.57 UTCmonitoring

   A fix has been implemented and we will continue monitoring.

5. 21. maj 2025 kl. 23.00 UTCresolved

   The incident has been resolved.