The 503 you saw was Typesense's built-in back-pressure mechanism. Here's how to handle this: https://typesense.org/docs/guide/syncing-data-into-typesense.html#handling-http-503s I don't think it's due to exports, because I do see a big batch of writes that came into the cluster around 30 minutes ago, which is what caused the 503