Your service's latest deployment shows as successful, but the 502 responses with X-Railway-Fallback: true indicate the proxy cannot reach your running service. This is consistent with a known platform-wide disruption that is currently being worked on. Your service should recover once the issue is resolved on our end, and no action is needed from you.

But I've had clients complaining for two days now, what can I tell them? How do I respond? We need a date because we're losing money.

We understand the impact this is having on your business and we're sorry. Your API service is still unable to reach its PostGIS database as of 14:02 UTC today, which is part of the broader platform disruption that began on May 19. The team published a postmortem at blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage with details on what happened and the recovery effort. We don't have a specific ETA to share, but recovery is actively underway. Once your database becomes reachable again, redeploying your API service should restore connectivity.

Is Railway still down? My services are still not working.

Your API service is still unable to reach the BinntuPostGIS database as of 13:32 UTC today, which is consistent with the ongoing recovery from the May 19 disruption. Your database service hasn't been redeployed since before the incident, so please try opening the BinntuPostGIS service, pressing Cmd+K (or Ctrl+K), and selecting "Redeploy source image" to re-pull a fresh image. After the database is back, redeploy the API service as well. Recovery is actively underway and we're sorry for the extended impact on your business.