3rd Party: Few Ramp connections failing with 500 Internal Server Error'

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 Ramp connections, which resulted in sync failures with a 500 internal server error.

Timeline:
This issue began on December 31, 2025, at 02:30 AM UTC and was resolved on December 31, 2025, at 09:30 AM UTC

Cause:
A subset of connections experienced failures due to 500 Internal Server Error responses from the business_entity table, originating from a third-party source.

Resolution:
A workaround was implemented by raising an alert and temporarily skipping the business_entity table during syncs, which restored connection stability. As this is a third-party issue, we have reached out to the source team for clarification and a permanent fix.

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

This issue is caused by a third-party API error on Ramp’s side, and we have reached out to Ramp Source Support for clarification and resolution.

In the meantime, we are adding an alert message for affected connections and will skip syncing the business_entity table. Customers who need an immediate workaround may temporarily de-select the business_entity table.
We’ll continue to share updates as more information becomes available.

We’ve identified the cause of the sync failures affecting the Ramp connector. The issue is due to an internal error from Ramp’s Entities endpoint, which is impacting the business_entity table and its related child tables.

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