Service Level Agreement
Effective April 14, 2025
1. Applicability
This Service Level Agreement (“SLA”) applies as follows:
Core Services:
For Customers on Standard, Enterprise or Business Critical Fivetran, Fivetran guarantees that the Core Services will be available and operational at least 99.9% of the time.
Data Delivery Services:
For Customers on Enterprise and Business Critical Fivetran plans, Fivetran guarantees to reliably load data on schedule at least 99.9% of the time.
This only applies once each table from a data source has proven capable of syncing to the Customer's target destination by successfully syncing the applicable data for 5 consecutive days.
How this SLA applies to the Fivetran Products:
SaaS Product - Core Services & Data Delivery Services
Hybrid Deployment - Core Services: (a) Web Application and (b) API as defined below; Data Delivery Services apply unless failure results from Customer`s Replication Servers.
If Fivetran does not achieve and maintain the service levels for a Core Service or Data Delivery Service (each a “Service”) as described in this SLA, then Customer may be eligible for a Service Credit (as defined below).
Fivetran may update the terms of this SLA from time to time. The then-current terms of this SLA are available at https://www.fivetran.com/legal/sla.
2. Definitions
Capitalized terms used but not defined in this SLA shall have the meanings ascribed to such terms the Master Subscription Agreement or other agreement for Customer’s use of the Fivetran Products (the “Agreement”) or, if not defined in the Agreement, in the Master Subscription Agreement located at https://www.fivetran.com/legal, or such successor URL as may be designated by Fivetran.
The following terms, when used in this SLA, will have the following meanings:
“Applicable Monthly Service Fees” means the total fees actually paid by Customer for the relevant Fivetran Product that are applied to the month in which a Service Credit is owed.
"Available Monthly Minutes" means the total amount of minutes in a full month where Downtime for a Core Service occurred.
“Connection” means a single instance of a data pipeline that replicates data from a source to a destination. For example, a MySQL connection moves data from a MySQL database to a destination.
“Connectors” let Customers create connections between sources and destinations. Connectors are pre-built components that can be used to create individual connections. For example, using the Salesforce connector to create a connection to replicate data from Salesforce to the Snowflake data warehouse.
“Core Services” means (a) Fivetran’s Web Application for accessing, viewing, and controlling Fivetran Products, (b) Fivetran’s API - Fivetran’s REST API for programmatically controlling Fivetran Products, and (c) Replication Servers that run Fivetran data replication services.
“Customer” means Customer as defined in the applicable Order Form for the Fivetran Products.
“Data Delivery Services” means Customer’s connections, which connect, process, and sync data from a source to a destination. Depending on the Customer’s configuration of a connection, this can happen every 1 min to every 24 hours.
“Downtime” means a period of time, measured in minutes for:
(a) Core Services, when a Core Service is unavailable.
For example, Fivetran’s Web Application is considered unavailable and accrues Downtime if a user tries to access it and receives a 404 page, or the Web Application will not load. Downtime for a Core Service may only be accrued for Customers that have been subscribed to Fivetran Product(s) for the entire month in which the Downtime occurred.
(b) Data Delivery Services, between when a connector fails to sync data and the next successful sync of data.
Downtime for Data Delivery Services is monitored via Fivetran logs using the Fivetran Platform Connector (see https://fivetran.com/docs/logs/fivetran-platform, or via Fivetran’s log service (see https://fivetran.com/docs/logs/external-logs) that exports service logs to Customer’s designated log service, such as AWS Cloudwatch, or via the Status tab on the Connection Details page in your Fivetran dashboard at https://fivetran.com/dashboard.
A description of log events can be found here: https://fivetran.com/docs/logs.
“Hybrid Deployment” means a Fivetran Product architecture option whereby certain components are downloaded and installed in the Customer’s environment and communicate securely with the Fivetran Cloud Platform to provide the Fivetran Product’s data integration capabilities.
“Monthly Connection Minutes” means all of the minutes that a single Fivetran connector is turned on or activated during the month when Downtime occurs.
“On-Prem Software” means a downloadable data integration software component or product installed on premise or in Customer’s private cloud environment provided by Fivetran to Customer.
“SaaS Product” means a SaaS-based data integration product provided by Fivetran to Customer.
"Service Credit" means the percentage of the Applicable Monthly Service Fees credited back to Customer following Fivetran’s claim approval.
“Service Credit Percentage” means the percentage of the Applicable Monthly Service Fees applied back to Customer, for every 60 minutes of Downtime, in the form of a Service Credit.
3. Claims
Customer must submit claims to Fivetran customer support at support.fivetran.com along with all information reasonably necessary for Fivetran to validate each claim, including: (a) a detailed description of the incident; (b) information regarding the time and duration of the Downtime; (c) the number and location(s) of affected users (if applicable); and (d) descriptions of Customer’s attempts to resolve the incident.
Fivetran must receive the claim within two months of the end of the month in which the incident occurred. Fivetran will evaluate all reasonably available information and make a good faith determination of whether a Service Credit is owed. Fivetran will use commercially reasonable efforts to process claims within 45 days of receipt.
If Customer experiences Downtime for multiple connectors, it must submit a separate claim for each connector. For example, if Customer experienced Downtime for both Salesforce Data Replication and MySQL Data Replication, Customer could be eligible for two separate Service Credits for Data Delivery (one for each connector), by submitting two claims under this SLA.
4. Service Credits
Service Credits are Customer’s sole and exclusive remedy for any performance or availability issues for the connectors described in this SLA. Customers may not unilaterally offset Applicable Monthly Service Fees for any performance or availability issues. Service Credits will be credited to Customer's account against Applicable Monthly Service Fees. Service Credits may not be redeemed for cash.
Core Services
Monthly Uptime Percentage and Service Credit Percentage for each Core Service
CORE SERVICE | MONTHLY UPTIME PERCENTAGE | SERVICE CREDIT PERCENTAGE |
Web Application | 99.9% | 1% |
API | 99.9% | 1% |
Replication Servers | 99.9% | 1% |
If one Core Service experiences Downtime, Customer will receive a Service Credit as outlined above even if the other Core Services are working. If more than one Core Service is down concurrently, Customer will receive the same Service Credit, not multiple credits.
Service Credits given for Downtime related to Core Services may not exceed 25% of the Applicable Monthly Service Fees paid to Fivetran in the month that the incident occurred, and may not exceed 10% of annualized fees paid for the current term. These lower limits are due to the fact that Data Delivery Services can still perform while the API or Web Application are experiencing downtime.
Note: With Fivetran, not all Core Services are directly correlated with Data Delivery Services. For example, Fivetran’s Web Application and APIs could be down and Fivetran could still be delivering data on schedule. In addition, Fivetran’s replication servers could be available, but data is not being delivered due to load errors, source API issues, etc. If Customer has chosen e.g. AWS US as the hosting provider region and the AWS UK region is down, then Customer would not be impacted.
Data Delivery Services
The Monthly Uptime Percentage and Service Credit Percentage for Data Delivery Services
MONTHLY UPTIME PERCENTAGE | SERVICE CREDIT PERCENTAGE | |
Data Delivery Services | 99.9% | 0.25% |
If a Data Delivery Service experiences Downtime, Customer will receive a Service Credit as outlined above for each connector affected by Downtime, for example a specific connector like Salesforce, or Mailchimp.
Service Credits given for Downtime related to Data Delivery may not exceed 50% of the Applicable Monthly Service Fees paid to Fivetran for the affected connection in the month that the incident occurred.
5. Service Credit Calculation
If a Core Service’s or Data Delivery Service`s Connection`s Downtime results in a Monthly Uptime Percentage below our 99.9% commitment, Customer will accrue Service Credits. Service Credits are calculated as follows:
SERVICE CREDITS = (DOWNTIME / 60) * APPLICABLE MONTHLY SERVICE FEES * SERVICE CREDIT PERCENTAGE
“Monthly Uptime Percentage” for
(a) Data Delivery Services is calculated as Monthly Connection Minutes for the affected connector less Downtime divided by Monthly Connection Minutes for that affected connection. Monthly Uptime Percentage is represented by the following formula:
MONTHLY UPTIME % = (MONTHLY CONNECTION MINUTES - DOWNTIME) / MONTHLY CONNECTION MINUTES
Example Downtime Calculation:
The example below outlines how to calculate Downtime for a connection turned on for the entire month of March (31 days/744 hours/44,640 minutes) with an expected configured schedule to sync data every hour. The times below are presented in a “sync_start” - “sync_end” format. Sync time: 1:01pm - 1:35pm. "status" : "SUCCESSFUL" Sync time: 2:00pm - 2:15pm. "status" : "SUCCESSFUL" Sync time: 3:02pm - 3:05pm. "status" : "FAILURE" Sync time: 4:01pm - 4:33pm. "status" : "SUCCESSFUL" Sync time: 5:00pm - 5:22pm. "status" : "FAILURE" Sync time: 6:03pm - 6:32pm. "status" : "FAILURE" Sync time: 7:01pm - 7:40pm. "status" : "SUCCESSFUL" Downtime: (4:33pm - 3:05pm) + (7:40pm - 5:22pm) = 3.77 hours (226 minutes) |
Building on the March example calculation above, Monthly Uptime % = (44,640 minutes - 226 minutes) / 44,640 minutes = 99.49%
Example Calculation:
In March, Customer consumed $1,847 in Applicable Monthly Service Fees to sync data for one of Customer’s Salesforce connections. During that month, the Customer's Salesforce connection experienced a sync error, and was unable to sync data for 226 minutes. For every 60 minutes of the 226 minutes (3.77 hours) of Downtime experienced for Customer’s Salesforce connection, Customer is credited back 0.25% of the $1,847 against Customer’s usage of Fivetran Products in April or future months for a total of $17.39. $17.39 (Service Credits) = (226 min / 60 )(Downtime) * $1,847 (Applicable Monthly Service Fees) * 0.25% (Service Credit Percentage) |
(b) Core Services is calculated as: Monthly Connection Minutes less Downtime divided by the Available Monthly Minutes. Monthly Uptime Percentage is represented by the following formula:
MONTHLY UPTIME % = (MONTHLY CONNECTION MINUTES - DOWNTIME) / AVAILABLE MONTHLY MINUTES
Example Calculation:
In April, Customer uses a total of $100 in Applicable Monthly Service Fees. During that month, Fivetran’s Web Application was unavailable for 256 minutes (4.27 hours) due to a server failure. For every 60 minutes of the 256 minutes of Downtime that Core Services experienced in April, Customer is credited back 1% of the $100 against Customer’s usage of Fivetran services in May, or future months, for a total of $4.27 Service Credit. $4.27 (Service Credits) = (256 min / 60) (Downtime for Core Services ) * $100 (Applicable Monthly Service Fees) * 1% (Service Credit Percentage) |
6. Limitations
Downtime does not include Data Delivery Services and Core Services unavailability due to the following:
Maintenance requested by Customer or scheduled maintenance, either by Fivetran or by third-party providers. Fivetran will provide seven days’ advance notice in writing or by e-mail of scheduled maintenance, not to exceed 24 hours per month.
Failure of equipment, software or other parts of the Fivetran Products not listed as a Core Service or Data Delivery Service.
Outages of third party connections or utilities or any other reasons beyond Fivetran’s reasonable control.
If Fivetran’s cloud vendor (GCP, AWS, or Microsoft Azure) experiences downtime, Customer does not accrue Downtime for Core Services during this downtime period.
Customer uses equipment, software or Fivetran Products in a way that is not recommended by Fivetran Documentation.
Customer has delayed, hindered or prevented Fivetran from providing the Services, such as removing Fivetran’s access to Customer’s data sources or destinations.
The Connector has become unavailable as a result of unsupported equipment, software or other third-party services which are not fully functional, which includes but is not limited to undocumented API changes, API limits, or sync failures due to new or changed data that disrupts the schema mapping rules.
Fivetran's suspension or termination of Customer’s access to the Fivetran Products in accordance with the Agreement.
Customer's breach of the Agreement or applicable Order Form for the Fivetran Product.
Customer's failure to reasonably respond to or cooperate with Fivetran to fix the issue.
The applicable Fivetran Product is a Trial Product.
Any downtime issues resulting from Customer-developed code that applies to Connector SDK and Function connectors.