Integrateio 장애 기록

1. 2026년 10월 22일 오후 6:12 UTCresolved

   오후 4시 17분과 오후 4시 31분 UTC 사이, 우리의 업스트림 공급자는 간헐적인 네트워킹 문제를 경험했습니다. 이 창에서 클러스터의 하위 세트에 일부 작업은 간헐적으로 실패 할 수 있습니다. 문제는 해결되고 모든 시스템은 일반적으로 작동합니다. 이 기간 동안 작업이 실패하면 다시 실행해야합니다. 자주 묻는 질문.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 3일 오전 7:27 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

2. 2026년 10월 3일 오전 8:54 UTCresolved

   사건이 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 24일 오전 5:55 UTCinvestigating

   현재 이 문제를 조사하고 있습니다.

2. 2026년 9월 24일 오전 6:39 UTCresolved

   사건이 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 1일 오후 6:37 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

2. 2026년 9월 1일 오후 9:58 UTCresolved

   우리는 더 많은 문제를 모니터링하고 있습니다. 작업은 지금까지 잘 실행됩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 27일 오전 4:14 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

2. 2026년 8월 27일 오전 6:44 UTCresolved

   사건이 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 11일 오후 4:25 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 8월 11일 오후 4:49 UTCmonitoring

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

3. 2026년 8월 12일 오후 5:47 UTCresolved

   The incident has been resolved.

1. 2026년 7월 28일 오후 3:26 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다

2. 2026년 7월 28일 오후 3:37 UTCresolved

   사건이 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 25일 오후 8:25 UTCinvestigating

   We are currently investigating the issue.

2. 2026년 6월 25일 오후 10: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. 2026년 6월 26일 오전 12:10 UTCresolved

   The incident has been resolved.

1. 2026년 5월 21일 오후 10: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. 2026년 5월 22일 오전 5: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. 2026년 4월 21일 오후 7: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. 2026년 4월 22일 오전 10:40 UTCresolved

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

3. 2026년 4월 22일 오전 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. 2026년 4월 2일 오후 1: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. 2026년 4월 2일 오후 5: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. 2026년 4월 2일 오전 11:50 UTCinvestigating

   We are currently investigating this issue

2. 2026년 4월 2일 오후 12:29 UTCidentified

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

3. 2026년 4월 2일 오후 1:45 UTCresolved

   The incident has been resolved.

1. 2026년 2월 10일 오후 5:24 UTCidentified

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

2. 2026년 2월 10일 오후 7:08 UTCmonitoring

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

3. 2026년 2월 17일 오전 3:39 UTCresolved

   The incident has been resolved.

1. 2026년 2월 9일 오후 4: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. 2026년 2월 17일 오전 3: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. 2026년 4월 2일 오전 11:50 UTCresolved

   This incident has been resolved.

1. 2026년 1월 19일 오전 12:45 UTCinvestigating

   We are currently investigating the issue.

2. 2026년 1월 19일 오전 4:05 UTCinvestigating

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

3. 2026년 1월 19일 오전 10:03 UTCidentified

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

4. 2026년 1월 19일 오전 10:22 UTCidentified

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

5. 2026년 1월 19일 오후 4:12 UTCresolved

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

1. 2025년 12월 3일 오전 4:18 UTCinvestigating

   We are currently investigating the issue.

2. 2025년 12월 3일 오전 5:57 UTCmonitoring

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

3. 2025년 12월 3일 오전 5: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. 2025년 11월 25일 오전 3: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. 2025년 10월 20일 오전 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. 2025년 10월 22일 오전 3:00 UTCresolved

   This incident has been resolved.

1. 2025년 9월 27일 오전 1:27 UTCinvestigating

   We are currently investigating the issue.

2. 2025년 9월 27일 오전 2: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. 2025년 8월 14일 오전 8:12 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 8월 14일 오전 9: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. 2025년 8월 14일 오전 9:52 UTCresolved

   The incident has been resolved.