Unable to troubleshoot system-wide latency issues

Hi team - we recently moved our backend service to Render, and all of its clients took a latency hit (~3x).
Our backend service used to be on AWS us-west-1, our DB is on AWS us-west-1.
The front-end clients that we also migrated to Render saw latency regression.

A typical investigation would require looking at the latencies e2e, from the network/LB layer all the way down to the DB, but we don’t have that capability here (also, we don’t know where Render hosts our services).

Can you help us investigate?

1 Like

Any help? We are paused on migrating more workloads over to Render until we have confidence we can root cause and fix the latency issues…

Hi Vasanth,

Thanks for reaching out.

There are a lot of potential variables involved here. First and foremost is that you’ve noted your database is in a region (us-west-1) different to your Render services (us-west-2). Cross-AWS-region latency would likely be part of the issue you’re seeing.

However, if we can get some more details/specific examples of the issue you are experiencing that may help us troubleshoot it with you, e.g. detailed logs/errors/output/timings, specific URLs, service ID(s), etc.

If you prefer not to share these details on the community forum, please feel free to raise a ticket with support@render.com

Kind regards


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.