All Systems Operational
Connectors Operational
90 days ago
99.23 % uptime
Today
Logs ? Operational
90 days ago
99.89 % uptime
Today
Files Operational
90 days ago
99.76 % uptime
Today
Sales Operational
90 days ago
99.19 % uptime
Today
BI Tools (Managed BigQuery) ? Operational
90 days ago
99.89 % uptime
Today
Events Operational
90 days ago
99.76 % uptime
Today
Finance Operational
90 days ago
95.73 % uptime
Today
Support Operational
90 days ago
99.8 % uptime
Today
Databases Operational
90 days ago
99.46 % uptime
Today
Functions Operational
90 days ago
99.89 % uptime
Today
Marketing Operational
90 days ago
97.33 % uptime
Today
Engineering Operational
90 days ago
99.89 % uptime
Today
Productivity Operational
90 days ago
99.89 % uptime
Today
Human Resources Operational
90 days ago
99.51 % uptime
Today
Destinations ? Operational
90 days ago
100.0 % uptime
Today
Dashboard UI ? Operational
90 days ago
99.87 % uptime
Today
Transformations ? Operational
90 days ago
99.96 % uptime
Today
Fivetran API ? Operational
90 days ago
99.98 % uptime
Today
Replication Servers ? Operational
90 days ago
99.96 % 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
Nov 30, 2021

No incidents reported today.

Nov 29, 2021

No incidents reported.

Nov 28, 2021

No incidents reported.

Nov 27, 2021

No incidents reported.

Nov 26, 2021

No incidents reported.

Nov 25, 2021
Resolved - We have resolved this incident.
Nov 25, 21:36 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 25, 18:36 UTC
Identified - The issue has been identified and we are working to resolve it.
Nov 25, 18:18 UTC
Nov 24, 2021

No incidents reported.

Nov 23, 2021

No incidents reported.

Nov 22, 2021

No incidents reported.

Nov 21, 2021

No incidents reported.

Nov 20, 2021

No incidents reported.

Nov 19, 2021
Resolved - This incident has been resolved.
Nov 19, 23:50 UTC
Monitoring - A fix has been deployed for the issue. We are monitoring the fix.
Nov 19, 19:32 UTC
Identified - The issue has been identified and we are working to resolve it.
Nov 19, 17:15 UTC
Resolved - - Some ongoing syncs were killed due to sync duplication.
- This was an intermittent issue and has since been resolved. There is no further action needed.
Nov 19, 08:30 UTC
Nov 18, 2021

No incidents reported.

Nov 17, 2021
Resolved - We have resolved this incident.
Nov 17, 21:21 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 17, 18:21 UTC
Update - Sage Intacct team responded that RECORDNO field is now obsolete and removed from API response. In place of RECORDNO field Title or CompanyID could be considered as Primary Key.

We are continuing to work towards a resolution and Fivetran engineering team is currently working on a fix to modify the Primary Key field.

Thank you for your continued patience while we work on fixing this.
Nov 17, 10:59 UTC
Update - We are continuing to work with the Sage Intacct team to understand the root cause of this behavior. In the meantime, we have received confirmation that deselecting the COMPANY table will allow syncs to resume. Once a stable solution is in place, you can re-enable the COMPANY table from the Fivetran Schema tab.
Nov 16, 10:10 UTC
Update - We are continuing to work with the Sage Intacct team to understand the root cause of this behavior. In the meantime, we have received confirmation that deselecting the COMPANY table will allow syncs to resume. Once a stable solution is in place, you can re-enable the COMPANY table from the Fivetran Schema tab.
Nov 16, 01:36 UTC
Update - Engineering team identified that COMPANY endpoint is not receiving RECORDNO field through API response from source and Fivetran considers RECORDNO as a primary key. Missing primary key in API response is causing the PrimaryKeyContainsNull exception.

We are continuing to work with Sage Intacct to understand the possible causes. As a workaround, deselect the COMPANY endpoint on Schema Config to make the connector succeed.

Thank you for your continued patience while we work on fixing this.
Nov 15, 12:39 UTC
Update - We are receiving NULL primary key values from Sage Intacct for the RECORDNO field in the Company endpoint. We are continuing to work with Sage Intacct to resolve the underlying cause of this issue. In the meantime, engineering team is investigating potential workarounds that will mitigate the impact of this incident.
Nov 15, 11:02 UTC
Update - We are continuing to work towards a resolution to this issue. Thank you for your understanding.
Nov 15, 03:30 UTC
Update - We are still trying to identify potential workarounds for customers impacted by this issue while simultaneously working with Sage Intacct's Support team. Thank you for your continued patience.
Nov 14, 03:32 UTC
Update - We are continuing to work with Sage Intacct to resolve the underlying cause of this issue. In the meantime, we are investigating potential workarounds that will mitigate the impact of this incident.
Nov 13, 18:31 UTC
Update - We are receiving NULL primary key values from Sage Intacct for the RECORDNO field in the Company endpoint.
We are in contact with Sage surrounding this issue.
Nov 13, 11:29 UTC
Identified - The issue has been identified and we are working to resolve it.
Nov 13, 09:36 UTC
Resolved - We have resolved this incident.
Nov 17, 07:06 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 17, 07:06 UTC
Identified - The issue has been identified and we are working to resolve it.
Nov 17, 07:06 UTC
Nov 16, 2021
Resolved - We have resolved this incident.
Nov 16, 23:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 16, 18:49 UTC
Update - We are continuing to work on a fix for this issue.
Nov 16, 18:46 UTC
Identified - Caused by an incident with GCP: https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh
Nov 16, 18:22 UTC
Monitoring - Affected services are starting to recover, however GCP is still stating that outages may occur.
Nov 16, 18:20 UTC
Update - Caused by an incident with GCP: https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh
Nov 16, 18:19 UTC
Identified - The issue has been identified and we are working to resolve it.
Nov 16, 18:18 UTC