13 days ago
Hello Railway Support,
I would like to clarify that the issue is still ongoing and the application is not accessible.
When accessing the production URL, users are still receiving the following error:
https://seminadfull-production.up.railway.app
Error message:
“Application failed to respond”
This error appears to be caused by the application itself or the deployment, and it is preventing all users from accessing the system.
Request ID (example):
VmBJ8yEDQiav9bueCx5-qw
Impact:
Users are currently unable to access the system
The application is completely unreachable in production
The issue is reproducible consistently when accessing the URL
Please investigate this as the issue is still active even after the previous ticket was marked as solved.
If needed, I can provide additional logs or information.
Thank you for your support.
Pinned Solution
12 days ago
Yes. Try redeploying all your service.
9 Replies
Status changed to Open Railway • 13 days ago
13 days ago
(The status page shows that the incident is still active... https://status.railway.com/incident/I23M92U0)
0x5b62656e5d
(The status page shows that the incident is still active... https://status.railway.com/incident/I23M92U0)
13 days ago
Hello Railway team.
My service is down and my customers are being impacted, including those with active subscription plans.
Could you please inform me of the estimated time of return (ETA) or the current status of the outage?
I need this information urgently to pass on to my customers.
Thank you.
12 days ago
the problem persists
12 days ago
PROJECT ID: a1b8379d-59d8-472a-b9d3-814c007fb5ac
SERVICES: seminad_full (Django app), MySQL, Redis
ISSUE:
Application cannot reach MySQL at mysql.railway.internal:3306
Private network DNS resolution is failing
Issue persists after multiple service restarts
All services show "online" but cannot communicate
TIMELINE:
- May 19 20:41 UTC: Last successful request logged
- May 20 10:03 UTC: New deployment triggered (deploy pause lifted)
- May 20 10:08-10:18 UTC: App logs show 60+ failed connection attempts to mysql.railway.internal:3306
- Multiple restart attempts: No improvement
EVIDENCE:
- MySQL service is running and online
- Redis service is running and online
- App container cannot resolve or connect to mysql.railway.internal:3306
- Cascading restarts did not restore connectivity
- Issue correlates with GCP incident on May 19
REQUEST:
Please investigate private network connectivity between containers
Check network namespace/routing configuration
Perform infrastructure-level network diagnostics
IMPACT:
- Production environment completely unavailable
- Paying customers unable to access system
- Data is safe but application cannot function
12 days ago
I already redeployed the application, but it still didn't come back. Can I redeploy the MySQL database?
12 days ago
It worked, thank you! I was afraid to redeploy the data in the database and lose it, but it didn't happen, thank you!
Status changed to Open 0x5b62656e5d • 12 days ago
Status changed to Solved leonardohmira • 12 days ago
leonardohmira
It worked, thank you! I was afraid to redeploy the data in the database and lose it, but it didn't happen, thank you!
12 days ago
The data is stored in the volume. Unless there's some kind of severe corruption, data loss usually shouldn't happen.
Status changed to Awaiting Railway Response Railway • 12 days ago
Status changed to Solved 0x5b62656e5d • 12 days ago