Fivetran incident
3rd Party: Hubspot connection syncs are failing with "HTTP 500 Internal Server Error" and message: "Your HubSpot source is not available at this time. We'll retry the sync later."
Fivetran experienced a minor incident on May 8, 2026 affecting HubSpot, lasting 1h 9m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 08, 2026, 01:15 AM UTC
The issue has been identified and we are working to resolve it.
- identified May 08, 2026, 01:27 AM UTC
Syncs are failing due to an issue on the third-party side, due to "HTTP 500 Internal Server Error" for the events endpoint. At this time, there are no reported incidents or updates on the HubSpot status page related to this behaviour. We have reached out to HubSpot support for more details on these failures. HubSpot status page link: https://status.hubspot.com/
- identified May 08, 2026, 02:13 AM UTC
HubSpot has updated their status page, confirming the regional degradation due to the AWS outage. We are also observing that sync failure rates are decreasing. We are monitoring the situation closely. https://status.hubspot.com/incidents/f0s8vh3hsftw ("HubSpot is experiencing a regional degradation causing issues with loading related to an AWS outage")
- monitoring May 08, 2026, 02:15 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 08, 2026, 03:25 AM UTC
This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connections are syncing successfully. Incident Summary Description: We identified an issue with the HubSpot connection, which resulted in syncs failing with "HTTP 500 Internal Server Error" Timeline: This issue began on 8th May 2026 at 12:07 AM UTC and was resolved on 8th May 2026 at 01:32 AM UTC. Cause: The issue was caused by the third-party, event-definitions endpoint failing with "HTTP 500 Internal Server Error". HubSpot has also updated their status page, confirming the regional degradation due to the AWS outage. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.