3rd Party: Some Ramp connections failing with 529 response errors

Update timeline

1. identified Jul 10, 2026, 07:10 PM UTC

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

2. identified Jul 10, 2026, 07:38 PM UTC

   We have identified that the source API is repeatedly returning HTTP 529 responses, causing sync failures. We are actively working with the third-party source to resolve the issue and will continue to provide updates. Next Expected Update: 1 hour

3. monitoring Jul 10, 2026, 08:30 PM UTC

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

4. resolved Jul 10, 2026, 08:39 PM UTC

   This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected Ramp connections are syncing successfully. Incident Summary Description: We identified an issue affecting Ramp connections that caused sync failures due to repeated HTTP 529 responses from the source API. Timeline: The issue began on 2026-07-10 at 16:50 UTC and was resolved on 2026-07-10 at 19:30 UTC. Cause: The source API was repeatedly returning HTTP 529 responses across multiple endpoints, resulting in sync failures. Resolution: No action was required from our side. The issue was resolved by the source, and affected connections recovered automatically once the source API resumed returning successful responses.