Hello everyone, I have deployed an astro js site using multiple regions, specifically 1 for each of the 4 available in railway, 1 replica each. I noticed that the same user connection was randomly being rerouted to different regions. I added logs in my middleware so every time a navigate between pages it looks like this:

const region = process.env.RAILWAY_REPLICA_REGION || "default";
console.log(`[REGION] - ${region}`);

with result:

[REGION] - us-west2
[REGION] - us-west2
[REGION] - europe-west4-drams3a
[REGION] - europe-west4-drams3a
[REGION] - europe-west4-drams3a
[REGION] - us-west2
[REGION] - asia-southeast1-eqsg3a
[REGION] - us-east4-eqdc4a

As far as I understand, railway edge networking automatically detects and routes to the nearest edge location. In fact when i try to curl my site for grep -i X-Railway-Edge I always get the EU west edge which is closest to my location. In my site however it almost looks like it's swapping replicas per request. That wasn't the case at all when I first deployed.

The problem emerged unexpectedly without me changing any deployments in any environment or service. This leads me to believe that it is related to infrastructure, and having tested with different networks and users, seems to yield the same issue. Is this normal, or maybe something wrong with my system ? Is RAILWAY_REPLICA_REGION the correct variable to at least verify which region is being hit ? What could be causing this all of a sudden ?

FYI i noticed the issue first around 17:00 EST, March 6.

Thank you in advance.