Hello,

I'm trying to diagnose a performance issue on a self-hosted Forest Admin instance running on Railway.

Architecture:

• Forest Admin self-hosted on Railway
• PostgreSQL database hosted on Supabase
• Forest Admin UI accessed through Forest Admin Cloud
• Both Railway and Supabase are hosted in the EU West (Europe) region
• No deployments or code changes have been made in approximately 3 weeks

Symptoms:

• Since yesterday, several users have reported significant slowness when using Forest Admin.

• On Railway, I can see response times occasionally spiking to around 30 seconds.

• The service remains online and does not appear to be restarting or crashing.

• Users report slow page loads and slow interactions within the admin panel.

• No significant increase in traffic or data volume has been identified so far.

My questions:

1. What metrics would you investigate first to determine whether the issue comes from Railway, Forest Admin, Supabase, or the network between them?
2. Is there a recommended way to identify which Forest Admin routes or actions are slow?
3. How do you usually correlate Forest Admin response times with PostgreSQL query execution times?
4. Have you experienced similar performance issues on Forest Admin without any recent deployment or code changes?
5. Are there any Railway or Supabase metrics that are particularly useful for diagnosing intermittent latency spikes?

Any advice, troubleshooting methodology, or similar experiences would be greatly appreciated.

Thank you!