APIs of my app getting 502 status

TypeError: fetch failed

[cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: madeometer.com:443, timeout: 10000ms)

[cause]: Error: read ECONNRESET

Solved$20 Bounty

11 Replies

image.png

image.png


Getting these issues from today morning.

My app is live and getting a lot of bad feedback. Anyone from railway team, tell me what's issue related to netwwork? This was working perfectly.


24 days ago

Hey, it's likely that these networking issues were related to our outage on May 19th.

If you're still seeing errors, a fresh redeploy (not a restart) should clear any lingering issues on affected services.

If you're still having issues here, can you link specific services that are affected so we can dig in and see if this is something on our side?


Status changed to Awaiting User Response Railway 24 days ago



Status changed to Awaiting Railway Response Railway 24 days ago



I've redeployed all services. Still getting same issue.


Railway
BOT

24 days ago

Your madeometer-v2 service shows a successful deployment at 09:23 UTC today and the custom domain madeometer.com has a valid certificate with propagated DNS, so everything looks healthy on our end now. The errors in your screenshots (ECONNRESET, ConnectTimeoutError) were likely lingering effects from the May 19 service disruption that resolved at 07:57 UTC. If you're still seeing 502s or connection timeouts, please let us know.


Railway
BOT

24 days ago

This thread has been marked as private. Any further activity in this thread will only be visible to you and Railway employees.

Status changed to Awaiting User Response Railway 24 days ago


Railway

Your `madeometer-v2` service shows a successful deployment at 09:23 UTC today and the custom domain `madeometer.com` has a valid certificate with propagated DNS, so everything looks healthy on our end now. The errors in your screenshots (ECONNRESET, ConnectTimeoutError) were likely lingering effects from [the May 19 service disruption](https://status.railway.com/incident/I23M92U0) that resolved at 07:57 UTC. If you're still seeing 502s or connection timeouts, please let us know.

Yes, still getting the issue.


Status changed to Awaiting Railway Response Railway 24 days ago


Railway
BOT

24 days 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 24 days ago


You can see the logs.

image.png

Attachments


usef
HOBBY

24 days ago

I am having the same issues, been getting 502 out of nowhere suddenly..


sonia_
FREETop 5% Contributor

22 days ago

Your issue is related to Railway Google Cloud Account Suspension. Although it was recovered on 06:14 UTC on May 20, but due to the dependency of railway edge network on GCP, All edge APIs are responding 502,503 errors. Due to queued deploys it overwhelmed the platform along with Github OAuth.

  • Check in logs if apis stills not working.
  • Redeploy the services will fix the issue now.
  • If you have other service in railway as the dependency of current service, redeploy them also.

I hope these will fix your issues now.

Incident blog: https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage

Railway is also planning to remove GCP and use it on failover. So this will not happen in future once railway infrastructure is created.


Status changed to Open dev 14 days ago


Status changed to Solved dev 14 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...