Störungsverlauf von Integrateio

1. 22. Oktober 2026 um 18:12 UTCresolved

   Zwischen 16:17 Uhr und 16:31 Uhr UTC hatte unser Upstream-Anbieter intermittierende Netzwerkprobleme. Während dieses Fensters sind einige Jobs in einer Teilmenge von Clustern möglicherweise intermittierend fehlgeschlagen. Das Problem wurde behoben und alle Systeme funktionieren normal. Wenn Sie in diesem Zeitraum gescheiterte Jobs gesehen haben, sollte die Wiederholung erfolgreich sein. Bitte kontaktieren Sie den Support, wenn Sie weiterhin Probleme sehen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. Oktober 2026 um 07:27 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 3. Oktober 2026 um 08:54 UTCresolved

   Der Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. September 2026 um 05:55 UTCinvestigating

   Wir untersuchen das Problem derzeit.

2. 24. September 2026 um 06:39 UTCresolved

   Der Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. September 2026 um 18:37 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

2. 1. September 2026 um 21:58 UTCresolved

   Wir beobachten weiterhin alle weiteren Fragen. Jobs laufen bisher gut.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. August 2026 um 04:14 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 27. August 2026 um 06:44 UTCresolved

   Der Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. August 2026 um 16:25 UTCinvestigating

   We are currently investigating this issue.

2. 11. August 2026 um 16:49 UTCmonitoring

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

3. 12. August 2026 um 17:47 UTCresolved

   The incident has been resolved.

1. 28. Juli 2026 um 15:26 UTCinvestigating

   Wir untersuchen derzeit dieses Problem

2. 28. Juli 2026 um 15:37 UTCresolved

   Der Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 25. Juni 2026 um 20:25 UTCinvestigating

   We are currently investigating the issue.

2. 25. Juni 2026 um 22:38 UTCidentified

   The issue has been identified and it's due to our upstream provider and the affected scope is for newly created clusters. New cluster creation and job runs should now be working. We are working on unblocking clusters that are stuck on Creating.

3. 26. Juni 2026 um 00:10 UTCresolved

   The incident has been resolved.

1. 21. Mai 2026 um 22:27 UTCinvestigating

   Issue - There’s a Salesforce service disruption. During a service disruption, end users can’t access the service. Please refer to more on Salesforce status - https://status.salesforce.com/incidents/20004038 Affected integrate.io jobs having the Salesforce connectors (Source/destination) are failing with an error message : Error Occurred While Authenticating: { "error" : "system_down", "error_description" : "system may be currently unavailable" }

2. 22. Mai 2026 um 05:09 UTCresolved

   Please be advised that the Salesforce incident has been fully resolved. You can view the official status update here: https://status.salesforce.com/incidents/20004038 We kindly ask that you check your jobs utilizing Salesforce connectors; all integrations should now be fully functional. Should you have any further questions or continue to experience issues, please do not hesitate to reach out to us at [email protected]

1. 21. April 2026 um 19:27 UTCidentified

   We are currently aware of job failures on Postgres destination with a non-empty schema field due to a backwards compatibility issue. Please run the jobs on a newly created cluster and it should fix the issue. We apologize for the inconvenience caused.

2. 22. April 2026 um 10:40 UTCresolved

   The incident has been resolved. We will be following up with an RCA soon.

3. 22. April 2026 um 11:01 UTCpostmortem

   ## Summary On **April 22, 2026**, between **02:20 UTC** and **07:33 UTC** \(~5 hours 13 minutes\), Postgres Destination jobs across [Integrate.io](http://Integrate.io) failed. The root cause was a partial rollback: our application layer rolled back successfully, but the deployment to our data processing engine did not, leaving the two components on mismatched versions. A corrective deployment at 07:33 UTC restored service. ## Customer impact * **Scope:** All Postgres Destinations, across all customers and all operation types. * **Window:** April 22, 2026 — 02:20 UTC → 07:33 UTC. * **Symptom:** Postgres Destination job runs failed at execution time. * **Status:** Fully resolved as of 07:33 UTC. Jobs succeed on retry or their next scheduled run. ## Timeline \(UTC\) * **02:20** — A rollback intended to address an earlier Postgres Destination issue deployed successfully to our application layer but silently failed to deploy to our data processing engine. The two components were left on incompatible versions. * **From 02:20 onward** — Postgres Destination jobs began failing for all customers. * **07:33** — Corrective deployment completed. Application and data processing engine are back in sync and Postgres Destination jobs resumed. ## Root cause Our application layer and data processing engine coordinate closely during job execution, so their deployed versions must match. A rollback deployed earlier today was split across both components; the pipeline reported the release as complete when only the application-layer half had actually deployed. For the duration of the skew, every Postgres Destination job failed. The underlying gap is in a **new CI/CD pipeline we recently introduced**, which did not correctly treat a partial deployment as a failure. ## Resolution A corrective deployment at 07:33 UTC brought the data processing engine in line with the application layer. Once versions matched, Postgres Destination jobs resumed normal operation. ## Next steps * Harden the new CI/CD pipeline so that any partial deployment is treated as a failed release and automatically reverts to the previously-matched versions rather than leaving components on mismatched builds. * Add pre-release validation that runs Postgres Destination jobs against every new version pair before promotion. * Publish learnings from this incident internally to inform future deployment-pipeline work. We apologize for the disruption and thank our customers for their patience.

1. 2. April 2026 um 13:53 UTCmonitoring

   We've updated the credentials for our Google integration as part of a security rotation. If you have a Google Ads, Google Analytics, Google Sheets or Google Drive connection, you may need to reconnect it: - Go to your Connections page - Open the affected connection - Click Reconnect and follow the Google authorization prompt If you have any trouble, our support team is here to help.

2. 2. April 2026 um 17:18 UTCresolved

   This incident has been resolved. If you encounter any issues related to Google Ads, GA analytics, or Google Sheets/Drive, please follow the steps suggested in this incident.

1. 2. April 2026 um 11:50 UTCinvestigating

   We are currently investigating this issue

2. 2. April 2026 um 12:29 UTCidentified

   The issue has been identified and a fix has been implemented. Please rerun the jobs on a newly created cluster.

3. 2. April 2026 um 13:45 UTCresolved

   The incident has been resolved.

1. 10. Februar 2026 um 17:24 UTCidentified

   The issue has been identified with our upstream provider and a fix is being implemented.

2. 10. Februar 2026 um 19:08 UTCmonitoring

   A fix has been implemented by our upstream provider and services are starting to recover. We are monitoring the results.

3. 17. Februar 2026 um 03:39 UTCresolved

   The incident has been resolved.

1. 9. Februar 2026 um 16:18 UTCidentified

   We have identified an issue causing job failures with the BigQuery V1 connector. This was introduced by a recent library upgrade that resulted in a regression affecting the connector. We are actively working on a fix. In the meantime, customers may migrate to the BigQuery V2 connector by following our documentation or by reaching out to our support team for assistance. We apologize for the inconvenience and appreciate your patience.

2. 17. Februar 2026 um 03:48 UTCmonitoring

   A fix has been implemented, and we are actively monitoring the results to ensure stability. Please proceed with running the jobs on a newly created cluster. This issue impacts packages that include the ExecuteSQL component and BigQuery V1. We apologize for the inconvenience and appreciate your patience.

3. 2. April 2026 um 11:50 UTCresolved

   This incident has been resolved.

1. 19. Januar 2026 um 00:45 UTCinvestigating

   We are currently investigating the issue.

2. 19. Januar 2026 um 04:05 UTCinvestigating

   The issue has been identified with the upstream provided and we are continuing to work with them to fix.

3. 19. Januar 2026 um 10:03 UTCidentified

   We’re seeing an improvement in our applications and currently working on restoring processing engine workloads.

4. 19. Januar 2026 um 10:22 UTCidentified

   We are continuing to recover the processing engine workloads and jobs should now be working moving forward.

5. 19. Januar 2026 um 16:12 UTCresolved

   The incident has been resolved. We will be writing a post-mortem report soon.

1. 3. Dezember 2025 um 04:18 UTCinvestigating

   We are currently investigating the issue.

2. 3. Dezember 2025 um 05:57 UTCmonitoring

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

3. 3. Dezember 2025 um 05:58 UTCresolved

   The incident has been resolved. The root cause was an issue with our upstream provider, which prevented clusters and jobs from triggering as expected. We are taking steps to improve our monitoring systems to ensure earlier detection in the future. We sincerely apologize for the inconvenience.

1. 25. November 2025 um 03:15 UTCresolved

   Jobs are partially failed to be executed on the clusters due to an issue from our upstream providers. The issue was resolved at Nov 21, 07:30 UTC.

1. 20. Oktober 2025 um 11:47 UTCmonitoring

   Due to AWS's incident the following components are still impacted, SFTP To Go's audit logs and Cron To Go's processing engine For more details please see below AWS status- https://health.aws.amazon.com/health/status

2. 22. Oktober 2025 um 03:00 UTCresolved

   This incident has been resolved.

1. 27. September 2025 um 01:27 UTCinvestigating

   We are currently investigating the issue.

2. 27. September 2025 um 02:30 UTCresolved

   The incident has been resolved. The root cause was an issue with our upstream provider, which prevented clusters and jobs from triggering as expected. We are taking steps to improve our monitoring systems to ensure earlier detection in the future. We sincerely apologize for the inconvenience.

1. 14. August 2025 um 08:12 UTCinvestigating

   We are currently investigating this issue.

2. 14. August 2025 um 09:23 UTCmonitoring

   A fix has been implemented and we are monitoring the results. Job workloads aren't affected and should still run as normal.

3. 14. August 2025 um 09:52 UTCresolved

   The incident has been resolved.