Integrateio の障害履歴

1. 2026年9月1日 18:37 UTCmonitoring

   修正を実装し、結果を監視しています.

2. 2026年9月1日 21:58 UTCresolved

   今後もさらなる課題を監視してまいります。 今までの仕事がうまくいっている.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月27日 4:14 UTCinvestigating

   現在、この問題を調査中です.

2. 2026年8月27日 6:44 UTCresolved

   事件が解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月11日 16:25 UTCinvestigating

   We are currently investigating this issue.

2. 2026年8月11日 16:49 UTCmonitoring

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

3. 2026年8月12日 17:47 UTCresolved

   The incident has been resolved.

1. 2026年7月28日 15:26 UTCinvestigating

   現在、この問題について検討中です

2. 2026年7月28日 15:37 UTCresolved

   事件が解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月25日 20:25 UTCinvestigating

   We are currently investigating the issue.

2. 2026年6月25日 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. 2026年6月26日 0:10 UTCresolved

   The incident has been resolved.

1. 2026年5月21日 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. 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日 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. 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日 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. 2026年4月2日 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. 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日 13:45 UTCresolved

   The incident has been resolved.

1. 2026年2月10日 17:24 UTCidentified

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

2. 2026年2月10日 19: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日 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. 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日 0: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日 16: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.

1. 2025年8月8日 8:13 UTCinvestigating

   We are currently investigating the issue.

2. 2025年8月8日 8:24 UTCmonitoring

   The issue has been identified and a fix has been implemented. We are currently monitoring.

3. 2025年8月8日 10:21 UTCresolved

   The incident has been resolved. The issue was caused by an issue on our upstream provider which caused clusters and jobs to not trigger. We will be working on improving our monitoring systems so we can detect the issue early. We apologize for the inconvenience caused.

1. 2025年7月4日 22:32 UTCinvestigating

   We are currently investigating the issue.

2. 2025年7月4日 22:40 UTCmonitoring

   A fix has been implemented and we are monitoring the results. We apologize for the inconvenience caused.

3. 2025年7月5日 2:31 UTCresolved

   The incident has been resolved.

1. 2025年6月19日 20:41 UTCinvestigating

   Hi All, We are experiencing an issue with our Reverse SSH connections, and the jobs are failing. Action: Investigating the issue

2. 2025年6月19日 20:51 UTCidentified

   The issue has been identified, and please find the fix below to resolve the connectivity issue. Please delete/refresh the entry on your known_hosts file. You can do either of the following: Delete the specific line on ~/.ssh/known_hosts file which contains virginia-tunnel.xplenty.com. Make sure to save. Execute ssh-keygen -R "[virginia-tunnel.xplenty.com]:50683" on the tunnel instance

3. 2025年6月19日 21:47 UTCmonitoring

   RCA: It looks like an issue one of our upstream providers. Follow the steps shared to resolve the issue. Detailed RCA will be shared soon.

4. 2025年6月19日 22:30 UTCresolved

   RCA: Initial findings: There seems to have been an issue with our upstream provider, which we're working with them to identify why. The above solution resolves the issue.