Fivetran: Stripe Connector Rescheduled due to Rate Limit Exceeded

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:
We identified an issue for the Stripe service which resulted in syncs failing with a Request rate limit exceeded error. Users may have seen failures for endpoints such as /v1/coupons and other similar requests.

Timeline:
This issue began on May 31, 2025 at 08:30 UTC and was resolved on May 31, 2025 at 09:15 UTC.

Cause:
Stripe enforced rate limits on a high volume of API requests made by our connector instances, resulting in sync failures across multiple customer connections.


Resolution:
We implemented throttling and rate management adjustments on our end, allowing traffic to align with Stripe’s rate limits. Once these changes took effect, sync failures subsided, and connectors began syncing successfully.

A fix has been implemented, and we are monitoring the results.

The issue has been identified and we are working to resolve it.

We are continuing to investigate this issue.

We are currently investigating the cause of the rate limit error impacting the Stripe connector.