4 months ago
~20% of the egress requests to api.mapbox.com are failing with the DNS errors, yet the same request in a second returns successfully:
2025-11-20T16:48:06.285109Z DEBUG reqwest::connect: starting new connection: https://api.mapbox.com/
2025-11-20T16:48:06.291795Z ERROR heavy_trucks_router_backend::routes::directions: Error while requesting directions: error sending request for url (https://api.mapbox.com/directions/v5/mapbox/driving/27.555782,53.895074;27.561823,53.902472?overview=full&geometries=polyline6&banner_instructions=true&roundabout_exits=true&alternatives=false&annotations=congestion%2Cdistance%2Cmaxspeed%2Cspeed&steps=true&access_token=REDACTED&voice_instructions=true&voice_units=metric&language=ru&continue_straight=true)
Caused by:
0: client error (Connect)
1: dns error
2: failed to lookup address information: Name does not resolve
2025-11-20T16:48:06.291881Z DEBUG heavy_trucks_router_backend::utils::logger: 500 /api/v1/directions/v5/mapbox/driving/27.555782%2C53.895074%3B27.561823%2C53.902472
2025-11-20T16:48:12.660816Z DEBUG reqwest::connect: starting new connection: https://api.mapbox.com/
2025-11-20T16:48:12.672926Z DEBUG hyper_util::client::legacy::connect::http: connecting to 18.239.69.67:443
2025-11-20T16:48:12.677065Z DEBUG hyper_util::client::legacy::connect::http: connected to 18.239.69.67:443
2025-11-20T16:48:12.802393Z DEBUG sqlx::query: summary="INSERT INTO directions ( …" db.statement="\n\n\n INSERT INTO directions (\n user_uuid,\n resolution_uuid,\n success,\n waypoints,\n params,\n response\n ) VALUES ($1, $2, $3, $4, $5, $6)\n RETURNING uuid\n \n" rows_affected=1 rows_returned=1 elapsed=20.817393ms elapsed_secs=0.020817393
2025-11-20T16:48:12.803092Z DEBUG heavy_trucks_router_backend::utils::logger: 200 /api/v1/directions/v5/mapbox/driving/27.561823%2C53.902472%3B27.555782%2C53.895074No problems reported for api.mapbox.com itself, looks like issue is only with egress traffic from Railway :(
Also tried to run dig api.mapbox.com in a loop every 1s for 1h. Not a single request failed with cloudflare's 1.1.1.1 DNS
6 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
4 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
4 months ago
Hey!
We have a fix being worked on which should resolve this! Will update here when we roll this out although we don't have a solid ETA on that time.
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
Hey, thanks for the update. Looking forward to hear some good news on the fix!
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Hey! Bit of an update on this,
We just rolled out a fix which should resolve those DNS issues. Please let me know how things look!
Status changed to Awaiting User Response Railway • 4 months ago
3 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 months ago
3 months ago
✅ The ticket Connectivity issues with external services has been marked as completed.

