Integrate.io Outage History

Integrate.io is up right now

Integrate.io had 12 outages in the last 2 years totaling 1489h 4m of downtime — averaging 0.5 incidents per month.

There were 12 Integrate.io outages since July 4, 2025 totaling 1489h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.xplenty.com

Notice June 25, 2026

Clusters Stuck on Creating, Jobs Not Running

Detected by Pingoru
Jun 25, 2026, 08:25 PM UTC
Resolved
Jun 26, 2026, 12:10 AM UTC
Duration
3h 45m
Timeline · 3 updates
  1. investigating Jun 25, 2026, 08:25 PM UTC

    We are currently investigating the issue.

  2. 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.

  3. resolved Jun 26, 2026, 12:10 AM UTC

    The incident has been resolved.

Read the full incident report →

Notice May 21, 2026

Salesforce related jobs are failing with "system down" error

Detected by Pingoru
May 21, 2026, 10:27 PM UTC
Resolved
May 22, 2026, 05:09 AM UTC
Duration
6h 41m
Affected: Salesforce Destination
Timeline · 2 updates
  1. 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" }

  2. 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]

Read the full incident report →

Notice April 2, 2026

Job Failures Related to Google-Related Services (Ads, Analytics, Sheets, Drive)

Detected by Pingoru
Apr 02, 2026, 01:53 PM UTC
Resolved
Apr 02, 2026, 05:18 PM UTC
Duration
3h 24m
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Notice April 2, 2026

Job Failures Related to Snowflake Connections

Detected by Pingoru
Apr 02, 2026, 11:50 AM UTC
Resolved
Apr 02, 2026, 01:45 PM UTC
Duration
1h 55m
Timeline · 3 updates
  1. investigating Apr 02, 2026, 11:50 AM UTC

    We are currently investigating this issue

  2. 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.

  3. resolved Apr 02, 2026, 01:45 PM UTC

    The incident has been resolved.

Read the full incident report →

Notice February 10, 2026

Intermittent DNS Failures

Detected by Pingoru
Feb 10, 2026, 05:24 PM UTC
Resolved
Feb 17, 2026, 03:39 AM UTC
Duration
6d 10h
Timeline · 3 updates
  1. identified Feb 10, 2026, 05:24 PM UTC

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

  2. 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.

  3. resolved Feb 17, 2026, 03:39 AM UTC

    The incident has been resolved.

Read the full incident report →

Notice February 9, 2026

BigQuery V1 Job Failures

Detected by Pingoru
Feb 09, 2026, 04:18 PM UTC
Resolved
Apr 02, 2026, 11:50 AM UTC
Duration
51d 19h
Timeline · 3 updates
  1. 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.

  2. 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.

  3. resolved Apr 02, 2026, 11:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 19, 2026

Some Clusters Stuck on Creating and Dashboard Inaccessible

Detected by Pingoru
Jan 19, 2026, 12:45 AM UTC
Resolved
Jan 19, 2026, 04:12 PM UTC
Duration
15h 26m
Timeline · 5 updates
  1. investigating Jan 19, 2026, 12:45 AM UTC

    We are currently investigating the issue.

  2. 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.

  3. identified Jan 19, 2026, 10:03 AM UTC

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

  4. 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.

  5. resolved Jan 19, 2026, 04:12 PM UTC

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

Read the full incident report →

Notice November 25, 2025

Partial Job Executions Failure

Detected by Pingoru
Nov 25, 2025, 03:15 AM UTC
Resolved
Nov 21, 2025, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 25, 2025, 03:15 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.

Read the full incident report →

Minor October 20, 2025

Due to AWS's incident some components are still impacted

Detected by Pingoru
Oct 20, 2025, 11:47 AM UTC
Resolved
Oct 22, 2025, 03:00 AM UTC
Duration
1d 15h
Affected: Live ChatAWS - US East (N. Virginia)
Timeline · 2 updates
  1. 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

  2. resolved Oct 22, 2025, 03:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 14, 2025

Clusters Taking Longer Time to Provision and Terminate

Detected by Pingoru
Aug 14, 2025, 08:12 AM UTC
Resolved
Aug 14, 2025, 09:52 AM UTC
Duration
1h 40m
Timeline · 3 updates
  1. investigating Aug 14, 2025, 08:12 AM UTC

    We are currently investigating this issue.

  2. 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.

  3. resolved Aug 14, 2025, 09:52 AM UTC

    The incident has been resolved.

Read the full incident report →

Notice July 4, 2025

Clusters Stuck on Creating

Detected by Pingoru
Jul 04, 2025, 10:32 PM UTC
Resolved
Jul 05, 2025, 02:31 AM UTC
Duration
3h 59m
Timeline · 3 updates
  1. investigating Jul 04, 2025, 10:32 PM UTC

    We are currently investigating the issue.

  2. 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.

  3. resolved Jul 05, 2025, 02:31 AM UTC

    The incident has been resolved.

Read the full incident report →