All Systems Operational
Fivetran Services Operational
90 days ago
99.99 % uptime
Today
Web App ? Operational
90 days ago
99.99 % uptime
Today
API ? Operational
90 days ago
100.0 % uptime
Today
Replication Servers ? Operational
90 days ago
99.98 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Mar 3, 2021

No incidents reported today.

Mar 2, 2021

No incidents reported.

Mar 1, 2021

No incidents reported.

Feb 28, 2021

No incidents reported.

Feb 27, 2021

No incidents reported.

Feb 26, 2021
Resolved - The issue is now resolved.
Feb 26, 18:34 UTC
Investigating - Twilio is currently experiencing an outage due to which our Twilio connectors are failing. We are waiting for them to resolve the issue.
Feb 26, 15:17 UTC
Resolved - This incident has been resolved.
Feb 26, 10:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 26, 09:57 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 26, 07:18 UTC
Investigating - All square connectors are failing with the "Failed to execute request" error message while querying the Locations endpoint. We are currently investigating the issue.
Feb 26, 06:17 UTC
Feb 25, 2021

No incidents reported.

Feb 24, 2021

No incidents reported.

Feb 23, 2021
Resolved - This incident has been resolved.
Feb 23, 03:50 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 22, 18:30 UTC
Investigating - The "Support" Button on the top-right of the Fivetran Dashboard is currently non-operational. We are investigating this issue.

In the meanwhile, please reach out to support@fivetran.com or submit a ticket through https://support.fivetran.com if you have any support-related queries.
Feb 22, 16:45 UTC
Feb 22, 2021
Feb 21, 2021

No incidents reported.

Feb 20, 2021

No incidents reported.

Feb 19, 2021
Resolved - We have sent out a separate email communication mentioning the current status and next action items related to this incident.
Feb 19, 08:18 UTC
Update - 1. For those customers that are unable to login to their Apple ID, or their account has been deactivated:
Please reach out to Apple through their chat feature by navigating to https://getsupport.apple.com/, and they will restore your account.

2. App Analytics is not syncing:
Due to changes in Apple’s API, we will temporarily not be syncing the endpoint for App Analytics and Reviews. At present, the connector will continue to sync sales and finance-related reports.
Feb 16, 22:02 UTC
Update - Some iTunes connectors are seeing this error:

Invalid username and password.{code=108, message='Invalid username and password. Change values and try again.'}

Please generate a new app specific password on the apple side and update it the fivetran setup form. The invalid username and password here is referencing the invalid username and app specific password. See this Apple support doc on how to reset the app specific password:
https://support.apple.com/en-in/HT204397
Feb 13, 21:34 UTC
Update - We are working with Apple support to gain more understanding about the error messages being received.
Feb 11, 03:47 UTC
Update - The error "MessageBodyReader" is occurring because we expect a JSON response on hitting the endpoint "analytics/api/v1/app-info/app", but Apple has started sending a HTML response and we are unable to fetch all the app details.

We are getting in touch with Apple support team to understand the issue
Feb 10, 11:32 UTC
Investigating - Apple App Store connectors that are using 2FA are failing on the error "MessageBodyReader not found for media" and are getting rescheduled with "Too many verification codes submitted" message. We are currently investigating this
Feb 10, 09:38 UTC
Feb 18, 2021

No incidents reported.

Feb 17, 2021
Resolved - All Connectors are running fine. This incident has been resolved
Feb 17, 13:00 UTC
Monitoring - Sendgrid had some network issues which resulted in "504 Gateway timeout" errors. This has been resolved on their end and the connectors are back up and running fine. We are monitoring the connections.
Feb 17, 08:38 UTC