3 months ago
I have my analytics template (umami) and it's been working for a while without any issue. Today stopped working. I can't even log in because it gets freezed. Tried to redeploy umami umage and postgresql (who had a issue apparently, said by the agent). None of this worked...
It is crucial to solve since there are client analytics...
7 Replies
3 months ago
Your Umami service is currently stuck in the initializing phase, which is related to a platform-wide service disruption that occurred earlier today and an ongoing build slowdown we are actively working to resolve. Your database connection and migrations look healthy, so the service itself is fine. As we clear the backlog, your deployment should complete. Please try redeploying once more, and if it remains stuck, wait a bit for the queue to clear and try again.
Status changed to Awaiting User Response Railway • 3 months ago
Railway
Your Umami service is currently stuck in the initializing phase, which is related to a [platform-wide service disruption](https://status.railway.com/incident/I23M92U0) that occurred earlier today and an [ongoing build slowdown](https://status.railway.com/incident/KVZ1Z8GY) we are actively working to resolve. Your database connection and migrations look healthy, so the service itself is fine. As we clear the backlog, your deployment should complete. Please try redeploying once more, and if it remains stuck, wait a bit for the queue to clear and try again.
3 months ago
it is not about building, it happened before this.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
We had a major service disruption earlier today from 02:25 UTC to 07:57 UTC that affected all traffic and DNS across all regions, which is separate from (and earlier than) the build slowdown. This is likely when your Umami stopped working. Your latest deployment is currently running (SUCCESS as of 12:18 UTC), and the database connection and migrations are all healthy. Your Umami logs show it was repeatedly crashing after starting successfully, but the most recent deployment appears stable. Can you check if it's accessible now?
Status changed to Awaiting User Response Railway • 3 months ago
Railway
We had a [major service disruption](https://status.railway.com/incident/I23M92U0) earlier today from 02:25 UTC to 07:57 UTC that affected all traffic and DNS across all regions, which is separate from (and earlier than) the build slowdown. This is likely when your Umami stopped working. Your latest deployment is currently running (SUCCESS as of 12:18 UTC), and the database connection and migrations are all healthy. Your Umami logs show it was repeatedly crashing after starting successfully, but the most recent deployment appears stable. Can you check if it's accessible now?
3 months ago
unable to access. can't login properly...
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 3 months ago
3 months ago
And in addition to that, the agent removed my database backup, fantastic....
3 months ago
I have the same issue
3 months ago
My solution was create a new umami template from scratch, but who is the responsible of deleting my customer's data? Is there any way of claiming?