a month ago
Railway Network Diagnostics
Generated : Saturday, Aug 29 2026 11:24:16 CEST
Endpoint : routing-info-production.up.railway.app
Client IP Info
{
"ip": "188.26.195.29",
"hostname": "188-26-195-29.digimobil.es",
"city": "Arganda",
"region": "Madrid",
"country": "ES",
"loc": "40.3008,-3.4372",
"org": "AS57269 DIGI SPAIN TELECOM S.A",
"postal": "28500",
"timezone": "Europe/Madrid",
"readme": "https://ipinfo.io/missingauth"
}
HTTP HEAD request
Status: 200 OK
Status Code: 200
Protocol: HTTP/2.0
Response Headers:
X-Railway-Edge: otp1
Content-Type: text/html
Date: Sat, 29 Aug 2026 09:24:19 GMT
Server: railway-hikari
X-Railway-Request-Id: _x6ckHgSROS1R2B4ALIuDA
X-Hikari-Trace: otp1.xryw
DNS lookup (using system DNS)
Respuesta no autoritativa:
Servidor: UnKnown
Address: 2a0c:5a80:0:2::1
Nombre: routing-info-production.up.railway.app
Address: 69.46.46.119
DNS lookup (using Cloudflare)
Respuesta no autoritativa:
Servidor: one.one.one.one
Address: 1.1.1.1
Nombre: routing-info-production.up.railway.app
Address: 69.46.46.119
Traceroute
Traza a la direcci�n routing-info-production.up.railway.app [69.46.46.119]
sobre un m�ximo de 30 saltos:
1 <1 ms <1 ms <1 ms 192.168.56.1
2 1 ms 1 ms 1 ms 10.0.2.134
3 1 ms 1 ms 1 ms 172.16.1.129
4 2 ms 1 ms 1 ms 10.220.97.106
5 * 1 ms 1 ms 82.77.228.8
6 62 ms 62 ms 62 ms 10.221.97.78
7 57 ms 57 ms 57 ms digi-buc.cdn77.com [185.229.189.8]
8 64 ms 64 ms 63 ms vl201.buc-nxd2-dist-1.cdn77.com [185.156.45.43]
9 57 ms 57 ms 57 ms 69.46.46.119
Traza completa.
Ping (n=10)
Haciendo ping a routing-info-production.up.railway.app [69.46.46.119] con 32 bytes de datos:
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Respuesta desde 69.46.46.119: bytes=32 tiempo=57ms TTL=54
Estad�sticas de ping para 69.46.46.119:
Paquetes: enviados = 10, recibidos = 10, perdidos = 0
(0% perdidos),Tiempos aproximados de ida y vuelta en milisegundos:
M�nimo = 57ms, M�ximo = 57ms, Media = 57msCompleted
2 Replies
a month ago
The diagnostics you posted show everything healthy: DNS resolves correctly, the HTTP request returns 200, ping has 0% packet loss at a consistent 57 ms, and the traceroute completes normally. Could you let us know what specific issue you're experiencing or what question you have?
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
not ok becouse im in Madrid Spain not Romania: Railway’s edge responded in 61 ms. The full round trip to your service took 96 ms across
2 hops
From Bucharest, Romania, the request entered Railway in Bucharest and reached this demo in Amsterdam, the nearest of four regions running it.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago