a month ago
https://railway.instatus.com/
Error: An internal error occurred with Vercel.
Your connection is working correctly.
Vercel is NOT working correctly.
This is an error with the platform itself, not the application.
502: BAD_GATEWAYCode: ROUTER_FILESYSTEM_LOOKUP_ERRORID: fra1::4xm9s-1760948114788-364f5de75c28
If you are a visitor, please try again later.
If you are the owner, no action is needed.
3 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
🧵 Can’t reach Next.js service from other containers using internal URL (only works with public URL)
🧵 Hi, we need help migrating our infrastructure from AWS to railway.
If you find the answer from one of these, please let us know by solving the thread!
a month ago
Now it's back but there seem to be build issues, I guess due to docker problems via AWS, can you please check and update status page?
a month ago
Hi there, Dockerhub is impacted by the AWS outage — we've opened an incident for this on our status page https://status.railway.com/cmgywlgzr03ljgnpzvfz4q6td
Status changed to Awaiting User Response Railway • 28 days ago
14 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 14 days ago