|
|
|
|
|
by quentindanjou
25 days ago
|
|
Railway say the incident is resolved but many are still down (returning 502): on our side, we had to manually trigger a redeploy to fix it but I believe it should have been triggered automatically by Railway and I can't understand how they can mark this as resolved while many are still down. In total, down for >11 hours on our side. |
|