Integrate.io Outage History

Integrate.io is up right now

Integrate.io had 28 outages in the last 2 years totaling 1598h 0m of downtime — averaging 1.2 incidents per month.

There were 28 Integrate.io outages since June 4, 2024 totaling 1598h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.xplenty.com

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 December 3, 2025

Clusters Stuck on Creating, Jobs Not Running

Detected by Pingoru
Dec 03, 2025, 04:18 AM UTC
Resolved
Dec 03, 2025, 05:58 AM UTC
Duration
1h 40m
Affected: Processing Engine
Timeline · 3 updates
  1. investigating Dec 03, 2025, 04:18 AM UTC

    We are currently investigating the issue.

  2. monitoring Dec 03, 2025, 05:57 AM UTC

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

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

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 →

Notice June 19, 2025

Reverse SSH connectivity issue

Detected by Pingoru
Jun 19, 2025, 08:41 PM UTC
Resolved
Jun 19, 2025, 10:30 PM UTC
Duration
1h 48m
Affected: AWS - US East (N. Virginia)
Timeline · 4 updates
  1. 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

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

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

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

Read the full incident report →

Notice May 28, 2025

Intermittent Dashboard Errors

Detected by Pingoru
May 28, 2025, 06:03 PM UTC
Resolved
May 28, 2025, 07:50 PM UTC
Duration
1h 46m
Timeline · 3 updates
  1. investigating May 28, 2025, 06:03 PM UTC

    We are currently investigating the issue which is causing the dashboard to return intermittent errors.

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

  3. resolved May 28, 2025, 07:50 PM UTC

    The incident has been resolved. We apologize for the inconvenience caused.

Read the full incident report →

Notice May 5, 2025

Jobs Stuck on Pending

Detected by Pingoru
May 05, 2025, 01:26 AM UTC
Resolved
May 05, 2025, 01:34 AM UTC
Duration
8m
Timeline · 3 updates
  1. investigating May 05, 2025, 01:26 AM UTC

    We are currently investigating an issue which caused jobs to be stuck on pending.

  2. monitoring May 05, 2025, 01:31 AM UTC

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

  3. resolved May 05, 2025, 01:34 AM UTC

    The incident has been resolved.

Read the full incident report →

Notice April 22, 2025

Issues retrieving data from Bing Ads

Detected by Pingoru
Apr 22, 2025, 12:41 PM UTC
Resolved
Apr 26, 2025, 11:06 AM UTC
Duration
3d 22h
Timeline · 3 updates
  1. investigating Apr 22, 2025, 12:41 PM UTC

    Customers may experience issues with jobs that read data from Bing Ads. Our engineers are investigating the issues.

  2. monitoring Apr 25, 2025, 04:58 PM UTC

    A fix has been implemented. Please reconnect your Bing Ads connection and rerun the jobs on a newly provisioned cluster.

  3. resolved Apr 26, 2025, 11:06 AM UTC

    The incident has been resolved.

Read the full incident report →

Notice March 18, 2025

Some Clusters Stuck on Creating

Detected by Pingoru
Mar 18, 2025, 03:46 AM UTC
Resolved
Mar 18, 2025, 07:26 AM UTC
Duration
3h 40m
Timeline · 3 updates
  1. identified Mar 18, 2025, 03:46 AM UTC

    We are seeing some clusters stuck on Creating on the Virginia region and have identified that it's due to an issue with our upstream provider. Will provide updates as soon as we have it.

  2. monitoring Mar 18, 2025, 06:21 AM UTC

    Clusters are now being created. We are continuing to monitor the issue.

  3. resolved Mar 18, 2025, 07:26 AM UTC

    The incident has been resolved.

Read the full incident report →

Notice February 24, 2025

Job Notification Issue Causing Job Failures

Detected by Pingoru
Feb 24, 2025, 08:13 PM UTC
Resolved
Feb 24, 2025, 08:13 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 24, 2025, 08:13 PM UTC

    From Feb 24th, 14:30 UTC to 19:41 UTC, an issue with our job notification service caused jobs to skip the Running state and display a blank runtime. While Dataflow packages may have run normally (pending further confirmation), Workflows were affected, leading to job failures. The issue has now been resolved. If needed, please rerun the jobs or use "Run One-Off" on the schedule page. A post-mortem will be released soon. We sincerely apologize for the inconvenience.

Read the full incident report →

Notice January 15, 2025

Job Failures on File Storage Destination

Detected by Pingoru
Jan 15, 2025, 01:07 PM UTC
Resolved
Jan 15, 2025, 01:07 PM UTC
Duration
Timeline · 1 update
  1. resolved Jan 15, 2025, 01:07 PM UTC

    From 10:25 UTC to 13:00 UTC, job failures occurred in packages using the file storage destination component due to a faulty deployment. The issue has been resolved. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor December 20, 2024

Dashboard Loading Issue

Detected by Pingoru
Dec 20, 2024, 07:40 PM UTC
Resolved
Dec 21, 2024, 12:45 AM UTC
Duration
5h 4m
Affected: dashboard.xplenty.com
Timeline · 2 updates
  1. investigating Dec 20, 2024, 07:40 PM UTC

    We are aware of an intermittent issue affecting the dashboard. If you encounter this problem, please try refreshing the page. Our development team is actively investigating the root cause and will implement a fix as soon as possible. We apologize for the inconvenience and appreciate your patience.

  2. resolved Dec 21, 2024, 12:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 25, 2024

Dashboard and API Issues

Detected by Pingoru
Nov 25, 2024, 02:12 PM UTC
Resolved
Nov 25, 2024, 02:48 PM UTC
Duration
36m
Timeline · 2 updates
  1. investigating Nov 25, 2024, 02:12 PM UTC

    We are currently investigating this issue.

  2. resolved Nov 25, 2024, 02:48 PM UTC

    The issue was due to our upstream provider. The incident has been resolved.

Read the full incident report →

Notice November 12, 2024

Clusters Stuck on Creating State

Detected by Pingoru
Nov 12, 2024, 04:05 PM UTC
Resolved
Nov 12, 2024, 04:05 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 12, 2024, 04:05 PM UTC

    On Nov 12 at 12:30 UTC until 14:00 UTC, we have detected an issue on our cluster provisioning which caused clusters to be stuck on creating due to a bad deployment. This should not affect any scheduled jobs but may have caused delayed start time of the said jobs. This issue has now been resolved and we apologize for the inconvenience caused.

Read the full incident report →

Critical October 19, 2024

Dashboard and API issues

Detected by Pingoru
Oct 19, 2024, 02:22 PM UTC
Resolved
Oct 20, 2024, 12:22 AM UTC
Duration
9h 59m
Affected: dashboard.xplenty.comAPIapi.xplenty.com
Timeline · 3 updates
  1. investigating Oct 19, 2024, 02:22 PM UTC

    We are currently having Dashboard and API not loading because of an issue with our upstream provider

  2. monitoring Oct 19, 2024, 06:30 PM UTC

    Dashboard is now up and we are currently monitoring.

  3. resolved Oct 20, 2024, 12:22 AM UTC

    The incident has been resolved.

Read the full incident report →