Integrate.io Outage History
Integrate.io is up right nowPingoru has recorded 51 incidents for Integrate.io: 17 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 3 | 15 of 720 (2%) |
| May 2026 | 1 | 0 of 744 (0%) |
| June 2026 | 1 | 0 of 720 (0%) |
| July 2026 | 1 | 0 of 744 (0%) |
| August 2026 | 2 | 0 of 744 (0%) |
| September 2026 | 2 | 0 of 720 (0%) |
| October 2026 | 2 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 146 (0%) |
Incidents, newest first
Notice October 22, 2026 Intermittent Job Failures Due to Upstream Networking Issues 14m
Started Oct 22, 2026, 04:17 PM UTC· resolved Oct 22, 2026, 04:31 PM UTC
- resolved Oct 22, 2026, 06:12 PM UTC
Between 4:17 PM and 4:31 PM UTC, our upstream provider experienced intermittent networking issues. During this window, some jobs on a subset of clusters may have failed intermittently. The issue has been resolved and all systems are operating normally. If you saw failed jobs during this period, re-running them should succeed. Please contact support if you continue to see issues.
Notice October 3, 2026 Clusters Stuck on Creating 1h 26m
Started Oct 03, 2026, 07:27 AM UTC· resolved Oct 03, 2026, 08:54 AM UTC
- investigating Oct 03, 2026, 07:27 AM UTC
We are currently investigating this issue.
- resolved Oct 03, 2026, 08:54 AM UTC
The incident has been resolved.
Notice September 24, 2026 Dashboard and API Issues 43m
Started Sep 24, 2026, 05:55 AM UTC· resolved Sep 24, 2026, 06:39 AM UTC
- investigating Sep 24, 2026, 05:55 AM UTC
We are currently investigating the issue.
- resolved Sep 24, 2026, 06:39 AM UTC
The incident has been resolved.
Notice September 1, 2026 Job failures related to Salesforce connections 3h 20m
Started Sep 01, 2026, 06:37 PM UTC· resolved Sep 01, 2026, 09:58 PM UTC
- monitoring Sep 01, 2026, 06:37 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 01, 2026, 09:58 PM UTC
We are continuing to monitor for any further issues. Jobs are running fine so far.
Notice August 27, 2026 Clusters Stuck on Creating 2h 29m
Started Aug 27, 2026, 04:14 AM UTC· resolved Aug 27, 2026, 06:44 AM UTC
- investigating Aug 27, 2026, 04:14 AM UTC
We are currently investigating this issue.
- resolved Aug 27, 2026, 06:44 AM UTC
The incident has been resolved.
Notice August 11, 2026 Increased Cluster Creation Time 1d 1h
Started Aug 11, 2026, 04:25 PM UTC· resolved Aug 12, 2026, 05:47 PM UTC
- investigating Aug 11, 2026, 04:25 PM UTC
We are currently investigating this issue.
- monitoring Aug 11, 2026, 04:49 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 12, 2026, 05:47 PM UTC
The incident has been resolved.
Notice July 28, 2026 Jobs With Delayed Updates 11m
Started Jul 28, 2026, 03:26 PM UTC· resolved Jul 28, 2026, 03:37 PM UTC
- investigating Jul 28, 2026, 03:26 PM UTC
We are currently investigating this issue
- resolved Jul 28, 2026, 03:37 PM UTC
The incident has been resolved.
Notice June 25, 2026 Clusters Stuck on Creating, Jobs Not Running 3h 45m
Started Jun 25, 2026, 08:25 PM UTC· resolved Jun 26, 2026, 12:10 AM UTC
- investigating Jun 25, 2026, 08:25 PM UTC
We are currently investigating the issue.
- identified Jun 25, 2026, 10:38 PM UTC
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 Jun 26, 2026, 12:10 AM UTC
The incident has been resolved.
Notice May 21, 2026 Salesforce related jobs are failing with "system down" error 6h 41m Salesforce Destination
Started May 21, 2026, 10:27 PM UTC· resolved May 22, 2026, 05:09 AM UTC
- investigating May 21, 2026, 10:27 PM UTC
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 May 22, 2026, 05:09 AM UTC
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]
Major April 21, 2026 Job Failures on Postgres Destination 15h 13m
Started Apr 21, 2026, 07:27 PM UTC· resolved Apr 22, 2026, 10:40 AM UTC
- identified Apr 21, 2026, 07:27 PM UTC
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 Apr 22, 2026, 10:40 AM UTC
The incident has been resolved. We will be following up with an RCA soon.
- postmortem Apr 22, 2026, 11:01 AM UTC
## 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.
Notice April 2, 2026 Job Failures Related to Google-Related Services (Ads, Analytics, Sheets, Drive) 3h 24m
Started Apr 02, 2026, 01:53 PM UTC· resolved Apr 02, 2026, 05:18 PM UTC
- monitoring Apr 02, 2026, 01:53 PM UTC
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 Apr 02, 2026, 05:18 PM UTC
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.
Notice April 2, 2026 Job Failures Related to Snowflake Connections 1h 55m
Started Apr 02, 2026, 11:50 AM UTC· resolved Apr 02, 2026, 01:45 PM UTC
- investigating Apr 02, 2026, 11:50 AM UTC
We are currently investigating this issue
- identified Apr 02, 2026, 12:29 PM UTC
The issue has been identified and a fix has been implemented. Please rerun the jobs on a newly created cluster.
- resolved Apr 02, 2026, 01:45 PM UTC
The incident has been resolved.
Notice February 10, 2026 Intermittent DNS Failures 6d 10h
Started Feb 10, 2026, 05:24 PM UTC· resolved Feb 17, 2026, 03:39 AM UTC
- identified Feb 10, 2026, 05:24 PM UTC
The issue has been identified with our upstream provider and a fix is being implemented.
- monitoring Feb 10, 2026, 07:08 PM UTC
A fix has been implemented by our upstream provider and services are starting to recover. We are monitoring the results.
- resolved Feb 17, 2026, 03:39 AM UTC
The incident has been resolved.
Notice February 9, 2026 BigQuery V1 Job Failures 51d 19h
Started Feb 09, 2026, 04:18 PM UTC· resolved Apr 02, 2026, 11:50 AM UTC
- identified Feb 09, 2026, 04:18 PM UTC
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 Feb 17, 2026, 03:48 AM UTC
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 Apr 02, 2026, 11:50 AM UTC
This incident has been resolved.
Notice January 19, 2026 Some Clusters Stuck on Creating and Dashboard Inaccessible 15h 26m
Started Jan 19, 2026, 12:45 AM UTC· resolved Jan 19, 2026, 04:12 PM UTC
- investigating Jan 19, 2026, 12:45 AM UTC
We are currently investigating the issue.
- investigating Jan 19, 2026, 04:05 AM UTC
The issue has been identified with the upstream provided and we are continuing to work with them to fix.
- identified Jan 19, 2026, 10:03 AM UTC
We’re seeing an improvement in our applications and currently working on restoring processing engine workloads.
- identified Jan 19, 2026, 10:22 AM UTC
We are continuing to recover the processing engine workloads and jobs should now be working moving forward.
- resolved Jan 19, 2026, 04:12 PM UTC
The incident has been resolved. We will be writing a post-mortem report soon.
Notice December 3, 2025 Clusters Stuck on Creating, Jobs Not Running 1h 40m Processing Engine
Started Dec 03, 2025, 04:18 AM UTC· resolved Dec 03, 2025, 05:58 AM UTC
- investigating Dec 03, 2025, 04:18 AM UTC
We are currently investigating the issue.
- monitoring Dec 03, 2025, 05:57 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 03, 2025, 05:58 AM UTC
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.
Notice November 21, 2025 Partial Job Executions Failure –
Started Nov 21, 2025, 07:00 AM UTC· resolved Nov 21, 2025, 07:00 AM UTC
- resolved Nov 21, 2025, 07:00 AM UTC
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.
Minor October 20, 2025 Due to AWS's incident some components are still impacted 1d 15h Live Chat, AWS - US East (N. Virginia)
Started Oct 20, 2025, 11:47 AM UTC· resolved Oct 22, 2025, 03:00 AM UTC
- monitoring Oct 20, 2025, 11:47 AM UTC
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 Oct 22, 2025, 03:00 AM UTC
This incident has been resolved.
Notice September 27, 2025 Clusters Stuck on Creating, Jobs Not Running 1h 2m
Started Sep 27, 2025, 01:27 AM UTC· resolved Sep 27, 2025, 02:30 AM UTC
- investigating Sep 27, 2025, 01:27 AM UTC
We are currently investigating the issue.
- resolved Sep 27, 2025, 02:30 AM UTC
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.
Notice August 14, 2025 Clusters Taking Longer Time to Provision and Terminate 1h 40m
Started Aug 14, 2025, 08:12 AM UTC· resolved Aug 14, 2025, 09:52 AM UTC
- investigating Aug 14, 2025, 08:12 AM UTC
We are currently investigating this issue.
- monitoring Aug 14, 2025, 09:23 AM UTC
A fix has been implemented and we are monitoring the results. Job workloads aren't affected and should still run as normal.
- resolved Aug 14, 2025, 09:52 AM UTC
The incident has been resolved.
Notice August 8, 2025 Clusters Stuck on Creating, Jobs Not Running 2h 7m
Started Aug 08, 2025, 08:13 AM UTC· resolved Aug 08, 2025, 10:21 AM UTC
- investigating Aug 08, 2025, 08:13 AM UTC
We are currently investigating the issue.
- monitoring Aug 08, 2025, 08:24 AM UTC
The issue has been identified and a fix has been implemented. We are currently monitoring.
- resolved Aug 08, 2025, 10:21 AM UTC
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.
Notice July 4, 2025 Clusters Stuck on Creating 3h 59m
Started Jul 04, 2025, 10:32 PM UTC· resolved Jul 05, 2025, 02:31 AM UTC
- investigating Jul 04, 2025, 10:32 PM UTC
We are currently investigating the issue.
- monitoring Jul 04, 2025, 10:40 PM UTC
A fix has been implemented and we are monitoring the results. We apologize for the inconvenience caused.
- resolved Jul 05, 2025, 02:31 AM UTC
The incident has been resolved.
Notice June 19, 2025 Reverse SSH connectivity issue 1h 48m AWS - US East (N. Virginia)
Started Jun 19, 2025, 08:41 PM UTC· resolved Jun 19, 2025, 10:30 PM UTC
- investigating Jun 19, 2025, 08:41 PM UTC
Hi All, We are experiencing an issue with our Reverse SSH connections, and the jobs are failing. Action: Investigating the issue
- identified Jun 19, 2025, 08:51 PM UTC
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
- monitoring Jun 19, 2025, 09:47 PM UTC
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.
- resolved Jun 19, 2025, 10:30 PM UTC
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.
Notice May 28, 2025 Intermittent Dashboard Errors 1h 46m
Started May 28, 2025, 06:03 PM UTC· resolved May 28, 2025, 07:50 PM UTC
- investigating May 28, 2025, 06:03 PM UTC
We are currently investigating the issue which is causing the dashboard to return intermittent errors.
- monitoring May 28, 2025, 07:26 PM UTC
A fix has been implemented and we are monitoring the result. We apologize for the inconvenience caused here.
- resolved May 28, 2025, 07:50 PM UTC
The incident has been resolved. We apologize for the inconvenience caused.
Notice May 5, 2025 Jobs Stuck on Pending 8m
Started May 05, 2025, 01:26 AM UTC· resolved May 05, 2025, 01:34 AM UTC
- investigating May 05, 2025, 01:26 AM UTC
We are currently investigating an issue which caused jobs to be stuck on pending.
- monitoring May 05, 2025, 01:31 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 05, 2025, 01:34 AM UTC
The incident has been resolved.