Identified - We have identified an issue where some syncs are being delayed in the AWS us-east-1 region due to issues with the underlying cloud service provider. We are currently investigating in more detail and will provide additional updates accordingly.
Oct 20, 2025 - 14:30 UTC
Update - While we work with Shopify to restore the Fivetran app’s availability in the Shopify App Store, you can still create new Shopify connections using our REST API.
Existing Shopify connections continue to run as expected.
Oct 07, 2025 - 20:09 UTC
Update - We are actively working with the Shopify team and are currently awaiting their update to resolve the issue. We will share further updates as soon as more information becomes available.
Oct 06, 2025 - 15:02 UTC
Identified - We are aware that the Fivetran app is currently unavailable in the Shopify App Store. This impacts the creation of new Shopify connections, while existing connections remain unaffected. Our Engineering team is actively working with the Shopify team to resolve the issue. We will share further updates as soon as more information becomes available.
Oct 01, 2025 - 09:23 UTC
Database connectors
Operational
90 days ago
99.99
% uptime
Today
Amazon Aurora MySQL
Operational
90 days ago
100.0
% uptime
Today
Amazon Aurora PostgreSQL
Operational
90 days ago
100.0
% uptime
Today
Azure Database for MariaDB
Operational
90 days ago
100.0
% uptime
Today
Azure Database for MySQL
Operational
90 days ago
100.0
% uptime
Today
Azure Database for PostgreSQL
Operational
90 days ago
100.0
% uptime
Today
Azure SQL Database
Operational
90 days ago
100.0
% uptime
Today
Azure SQL Managed Instance
Operational
90 days ago
100.0
% uptime
Today
Amazon DynamoDB
Operational
90 days ago
100.0
% uptime
Today
Google Cloud SQL for MySQL
Operational
90 days ago
100.0
% uptime
Today
Google Cloud SQL for PostgreSQL
Operational
90 days ago
100.0
% uptime
Today
Google Cloud SQL for SQL Server
Operational
90 days ago
100.0
% uptime
Today
Heroku PostgreSQL
Operational
90 days ago
100.0
% uptime
Today
Magento MySQL
Operational
90 days ago
100.0
% uptime
Today
Magento MySQL RDS
Operational
90 days ago
100.0
% uptime
Today
MariaDB
Operational
90 days ago
100.0
% uptime
Today
Amazon RDS for MariaDB
Operational
90 days ago
100.0
% uptime
Today
MongoDB
Operational
90 days ago
100.0
% uptime
Today
MongoDB Sharded
Operational
90 days ago
100.0
% uptime
Today
MySQL
Operational
90 days ago
100.0
% uptime
Today
MySQL RDS
Operational
90 days ago
100.0
% uptime
Today
Oracle
Operational
90 days ago
100.0
% uptime
Today
Oracle EBS
Operational
90 days ago
100.0
% uptime
Today
Oracle RAC
Operational
90 days ago
100.0
% uptime
Today
Oracle RDS
Operational
90 days ago
99.96
% uptime
Today
PostgreSQL
Operational
90 days ago
100.0
% uptime
Today
Amazon RDS for PostgreSQL
Operational
90 days ago
100.0
% uptime
Today
SAP HANA
Operational
90 days ago
100.0
% uptime
Today
SQL Server
Operational
90 days ago
99.98
% uptime
Today
Amazon RDS for SQL Server
Operational
90 days ago
100.0
% uptime
Today
Amazon DocumentDB
Operational
90 days ago
100.0
% uptime
Today
High-Volume Agent Oracle
Operational
90 days ago
100.0
% uptime
Today
High Volume Agent Db2 for i
Operational
90 days ago
100.0
% uptime
Today
High-Volume Agent SQL Server
Operational
90 days ago
100.0
% uptime
Today
Snowflake
Operational
90 days ago
100.0
% uptime
Today
High-Volume Agent SAP ECC on Oracle
Operational
90 days ago
100.0
% uptime
Today
Elastic Cloud
Operational
90 days ago
100.0
% uptime
Today
Self Hosted Elasticsearch
Operational
90 days ago
100.0
% uptime
Today
Open Distro
Operational
90 days ago
100.0
% uptime
Today
Opensearch
Operational
90 days ago
100.0
% uptime
Today
High-Volume Agent SAP ECC on Oracle with NetWeaver
Operational
90 days ago
100.0
% uptime
Today
Azure Cosmos DB for NoSQL
Operational
90 days ago
100.0
% uptime
Today
High-Volume Agent SAP ECC on Db2 for i
Operational
Resolved -
We are resolving this incident as sync rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary
Description: One of our public cloud service provider experienced operational issue and this had impacted our syncs that are dependent on this cloud service provider
Timeline: We noticed sync failures from October 20, 2025 at 07:11 UTC and our syncs reverted to normal state effective October 20, 2025 at 11:30 UTC.
Resolved -
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary
Description: We identified an issue for Instagram Business connector which resulted in syncs failing with an error "An unexpected error has occurred. Please retry your request later".
Timeline: This issue began on October 16, 2025 at 17:30 UTC and was resolved on October 17, 2025 at 12:30 UTC.
Cause: We have received temporary error response from the source API.
Resolution: A fix has been implemented to skip the problematic entities which produced error responses
Oct 17, 15:11 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Oct 17, 11:25 UTC
Identified -
The issue has been identified and we are working to resolve it.
Oct 17, 07:50 UTC
Description: Anaplan connection syncs were failing with 522 errors due to an outage on the Anaplan service.
Timeline: The issue began on 15 Oct at 11:12 AM UTC and was resolved at 05:41 PM UTC.
Cause: The failures occurred due to a service outage on the Anaplan platform.
Resolution: The Anaplan team has resolved the outage and restored the service. Following this, the connections were automatically restored, and subsequent sync jobs are now completing successfully.
Oct 15, 20:05 UTC
Monitoring -
The Anaplan source has confirmed that service has now been restored, and we are monitoring the results.
Oct 15, 19:15 UTC
Update -
Anaplan team is actively working on a resolution. We are monitoring the situation and will provide updates as more information becomes available.
Oct 15, 13:08 UTC
Identified -
This is due to a confirmed outage with Anaplan.
Resolved -
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully.
Incident Summary Description: Failures are occurring in setup tests and schema change actions across all Hybrid Deployment connections.
Timeline: This issue began on 2025-10-09 at 18:26 UTC and was resolved on 2025-10-13 at 01:20 UTC.
Cause: A recent code change affected setup tests and schema change actions for Hybrid
Resolution: Reverted the change and applied the fix.
Oct 13, 03:59 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Oct 13, 02:08 UTC
Identified -
We have identified the root cause, where a recent code change affected setup tests and schema change actions for Hybrid Deployment connections. A fix has been deployed, and the rollout is currently in progress.
We are closely monitoring the deployment and expect setup tests and schema change actions to return to normal operation once the rollout is complete.
Oct 13, 00:22 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Oct 13, 00:20 UTC
Identified -
The issue has been identified and we are working to resolve it.
Oct 13, 00:06 UTC
Resolved -
Description: We identified an issue with the Google Ads connector that caused syncs to fail with the error: "Unknown failure. Failed to create GoogleAdsClient."
Timeline: The issue began on October 9th at 16:00 UTC and was resolved on October 9th at 16:50 UTC.
Cause: A code enhancement for the Google Ads connector was deployed. A delay in the deployment to the server temporarily caused these failures.
Resolution: The code deployment was completed successfully, and the issue has now been resolved.
Oct 9, 17:30 UTC
Resolved -
Description: We identified an issue for connectors with managed_data_lake and new_s3_datalake destination services, which resulted in intermittent sync failures.
Timeline: This issue began on 2025-09-29 at 16:19:00 UTC and was resolved on 2025-10-08 17:06:00 UTC.
Cause: The connectors encountered an error while trying to write data to a directory that was inadvertently removed during a recent update.
Resolution: The issue was resolved by restoring the directory through a rollback of the recent code change that had deleted it.
Oct 8, 11:30 UTC
Resolved -
Description: We identified an issue for LinkedIn Company Pages, which resulted in syncs failing with the error:
javax.ws.rs.InternalServerErrorException: HTTP 500 Server Error.
Timeline: This issue began on 6th October 14:00 UTC and was resolved on 6th October 16:00 UTC.
Cause: We received an HTTP 500 Error for our requests from the LinkedIn APIs.
Resolution: The issue was automatically resolved on the source side. We stopped receiving errors after 16:00 UTC, indicating that the source system restored normal operations.
Oct 6, 14:00 UTC
Resolved -
Description: We identified an issue for LinkedIn Ads which resulted in syncs failing with the error:
javax.ws.rs.InternalServerErrorException: HTTP 500 Server Error.
Timeline: This issue began on 6th October 14:00 UTC and was resolved on 6th October 16:00 UTC.
Cause: We received an HTTP 500 Error for our requests from the LinkedIn Ads APIs.
Resolution: The issue was automatically resolved on the source side. We stopped receiving errors after 16:00 UTC, indicating that the source system restored normal operations.
Oct 6, 14:00 UTC