Errori di lavoro intermittenti a causa di problemi di rete a monte
Inizio 22 ottobre 2026 alle ore 18:12 UTC · 0m
Pending
resolved
Tra le 16:17 e le 16:31 PM UTC, il nostro provider a monte ha sperimentato problemi di rete intermittenti. Durante questa finestra, alcuni lavori su un sottoinsieme di cluster possono aver fallito in modo intermittente.
Il problema è stato risolto e tutti i sistemi sono operativi normalmente. Se avete visto lavori falliti durante questo periodo, re-running loro dovrebbero avere successo. Si prega di contattare il supporto se si continua a vedere i problemi.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Clusters Stuck sulla creazione
Inizio 3 ottobre 2026 alle ore 07:27 UTC · 1h 27m
Pending
investigating
Stiamo attualmente indagando su questo problema.
resolved
L'incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Problemi di Dashboard e API
Inizio 24 settembre 2026 alle ore 05:55 UTC · 44m
Pending
investigating
Stiamo attualmente esaminando il problema.
resolved
L'incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Errori di lavoro relativi alle connessioni Salesforce
Inizio 1 settembre 2026 alle ore 18:37 UTC · 3h 21m
Pending
monitoring
Una soluzione è stata implementata e stiamo monitorando i risultati.
resolved
Stiamo continuando a monitorare per ulteriori problemi.
I lavori stanno andando bene finora.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Clusters Stuck sulla creazione
Inizio 27 agosto 2026 alle ore 04:14 UTC · 2h 29m
Pending
investigating
Stiamo attualmente indagando su questo problema.
resolved
L'incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Increased Cluster Creation Time
Inizio 11 agosto 2026 alle ore 16:25 UTC · 1d 1h
Pending
investigating
We are currently investigating this issue.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
The incident has been resolved.
Lavori con aggiornamenti ritardati
Inizio 28 luglio 2026 alle ore 15:26 UTC · 11m
Pending
investigating
Stiamo indagando su questo argomento
resolved
L'incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Clusters Stuck on Creating, Jobs Not Running
Inizio 25 giugno 2026 alle ore 20:25 UTC · 3h 45m
Pending
investigating
We are currently investigating the issue.
identified
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.
resolved
The incident has been resolved.
Salesforce related jobs are failing with "system down" error
Inizio 21 maggio 2026 alle ore 22:27 UTC · 6h 41m
Pending
Componenti interessati
Salesforce Destination
investigating
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" }
resolved
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]
Job Failures on Postgres Destination
Inizio 21 aprile 2026 alle ore 19:27 UTC · 15h 14m
OutageIncidente maggiore
identified
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.
resolved
The incident has been resolved. We will be following up with an RCA soon.
postmortem
## 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.
Job Failures Related to Google-Related Services (Ads, Analytics, Sheets, Drive)
Inizio 2 aprile 2026 alle ore 13:53 UTC · 3h 25m
Pending
monitoring
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.
resolved
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.
Job Failures Related to Snowflake Connections
Inizio 2 aprile 2026 alle ore 11:50 UTC · 1h 55m
Pending
investigating
We are currently investigating this issue
identified
The issue has been identified and a fix has been implemented.
Please rerun the jobs on a newly created cluster.
resolved
The incident has been resolved.
Intermittent DNS Failures
Inizio 10 febbraio 2026 alle ore 17:24 UTC · 6d 10h
Pending
identified
The issue has been identified with our upstream provider and a fix is being implemented.
monitoring
A fix has been implemented by our upstream provider and services are starting to recover. We are monitoring the results.
resolved
The incident has been resolved.
BigQuery V1 Job Failures
Inizio 9 febbraio 2026 alle ore 16:18 UTC · 51d 19h
Pending
identified
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.
monitoring
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.
resolved
This incident has been resolved.
Some Clusters Stuck on Creating and Dashboard Inaccessible
Inizio 19 gennaio 2026 alle ore 00:45 UTC · 15h 26m
Pending
investigating
We are currently investigating the issue.
investigating
The issue has been identified with the upstream provided and we are continuing to work with them to fix.
identified
We’re seeing an improvement in our applications and currently working on restoring processing engine workloads.
identified
We are continuing to recover the processing engine workloads and jobs should now be working moving forward.
resolved
The incident has been resolved. We will be writing a post-mortem report soon.
Clusters Stuck on Creating, Jobs Not Running
Inizio 3 dicembre 2025 alle ore 04:18 UTC · 1h 40m
Pending
Componenti interessati
Processing Engine
investigating
We are currently investigating the issue.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
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.
Partial Job Executions Failure
Inizio 21 novembre 2025 alle ore 07:00 UTC · 0m
Pending
resolved
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.
Due to AWS's incident some components are still impacted
Inizio 20 ottobre 2025 alle ore 11:47 UTC · 1d 15h
IssuesIncidente minore
Componenti interessati
AWS - US East (N. Virginia)Live Chat
monitoring
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
resolved
This incident has been resolved.
Clusters Stuck on Creating, Jobs Not Running
Inizio 27 settembre 2025 alle ore 01:27 UTC · 1h 2m
Pending
investigating
We are currently investigating the issue.
resolved
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.
Clusters Taking Longer Time to Provision and Terminate
Inizio 14 agosto 2025 alle ore 08:12 UTC · 1h 40m
Pending
investigating
We are currently investigating this issue.
monitoring
A fix has been implemented and we are monitoring the results. Job workloads aren't affected and should still run as normal.
