Our backend server started returning 503 errors
will-zys
PROOP

4 months ago

Following a regular deploy this morning, we started getting the following 503 error when HTTP requests are sent to our backend server:

Pop visit count exceeded max threshold on cache-sin-wsss1830076-SIN: scJ4iSV4UkyHDI2juJNzrcUzYk/oO1PMCyYg4bz5Utg!CHC!cache-chc950028-CHC, scJ4iSV4UkyHDI2juJNzrcUzYk/oO1PMCyYg4bz5Utg!SIN!cache-sin-wsss1830030-SIN, scJ4iSV4UkyHDI2juJNzrcUzYk/oO1PMCyYg4bz5Utg!SIN!cache-sin-wsss1830047-SIN, scJ4iSV4UkyHDI2juJNzrcUzYk/oO1PMCyYg4bz5Utg!SIN!cache-sin-wsss1830056-SIN, scJ4iSV4UkyHDI2juJNzrcUzYk/oO1PMCyYg4bz5Utg!QPG!cache-qpg1220-QPG, scJ4iSV4UkyHDI2juJNzrcUzYk/oO1PMCyYg4bz5Utg!SIN!cache-sin-wsss1830070-SIN

I've tried turning off Metal, increasing replica, changing region, all with no success.

Solved

2 Replies

4 months ago

Is this on a specific endpoint? if so, what endpoint and what does it do?


Status changed to Awaiting User Response Railway 4 months ago


will-zys
PROOP

4 months ago


Status changed to Awaiting Railway Response Railway 4 months ago


Status changed to Solved will-zys 4 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...