16 days 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.
2 Replies
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
No, it's on all endpoints. I found 2 posts with similar issues but no clear resolution.
https://station.railway.com/questions/getting-random-503-error-not-related-to-f00048fa
https://station.railway.com/questions/production-api-unreachable-requests-no-6d15c4fb
Status changed to Awaiting Railway Response Railway • 16 days ago
Status changed to Solved will-zys • 16 days ago