Fivetran: OpenAI connections failing with 429 rate limit errors for the newly added cost_api_key table
View the provider incident record →Current answer
Fivetran experienced a minor incident: Fivetran: OpenAI connections failing with 429 rate limit errors for the newly added cost_api_key table. Resolved on Aug 26, 2026.
The notice publication date does not establish the outage start. Provider resolved: .
Looking for an update now? Check the current status, or follow Fivetran for future changes.
Provider notice timeline
Affected Components
OpenAI
Incident Timeline
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:
OpenAI connections failed with 429 rate limit errors for the newly added cost_api_key table.
Timeline:
This issue began on 25 August at around 10:30 AM UTC and was resolved on 26 August at around 2:30 AM UTC.
Cause:
The issue was caused by API rate limiting affecting syncs for the newly added cost_api_key table.
Resolution:
After the fix was deployed to address the rate-limiting behaviour, the affected connections began recovering, and syncs resumed successfully.
Incident Summary
Description:
OpenAI connections failed with 429 rate limit errors for the newly added cost_api_key table.
Timeline:
This issue began on 25 August at around 10:30 AM UTC and was resolved on 26 August at around 2:30 AM UTC.
Cause:
The issue was caused by API rate limiting affecting syncs for the newly added cost_api_key table.
Resolution:
After the fix was deployed to address the rate-limiting behaviour, the affected connections began recovering, and syncs resumed successfully.
Aug 26, 2026 at 3:53 AM UTC
Monitoring
The fix has been deployed. We will continue to monitor all affected connectors until they resume their normal sync functionality.
Aug 26, 2026 at 3:36 AM UTC
Identified
We have identified an issue causing some syncs to fail due to API rate limiting.We have prepared a fix and it is awaiting deployment. Once deployed, the affected connections should begin recovering. We will continue to provide updates as deployment progresses.
Aug 25, 2026 at 11:48 PM UTC
Identified
The issue has been identified and we are working to resolve it.
Aug 25, 2026 at 6:40 PM UTC
Was your business affected by this Fivetran outage?
Follow Fivetran and route available status alerts to email or a team channel.