Metal anycast edge network - slower than the current one
dome
PROOP

10 months ago

hi I noticed when enrolling my domain into the metal anycast edge network the latency will be very high. When using the normal variant everything works as fast as it can get. Yes I know it says beta, but still, will this be addressed? Before u ask, yes, the services are deployed on the new metal infrastructure.

28 Replies

dome
PROOP

10 months ago

5f0bbd5a-7be4-4318-905d-f3157b1057d9


brody
EMPLOYEE

10 months ago

Hello!

  • Please visit and paste the response body here + your current location.

  • Do a traceroute to 66.33.22.11 and included it in your response.


dome
PROOP

10 months ago

Response:

edge=railway/europe-west4-drams3a zone=europe-west4-drams3a ip=::ffff:100.64.0.2 forwarded=77.25.15.248 hs=f09480be9e4a req=SdvRiqUOSsO-IMNSbxTyFw_3554946428

Location:

Germany

Traceroute:

traceroute to 66.33.22.11 (66.33.22.11), 64 hops max, 40 byte packets 1 [fritz.box](fritz.box) (192.168.178.1) 1.825 ms 1.020 ms 1.574 ms 2 * * * 3 [ip5886ea33.static.kabel-deutschland.de](ip5886ea33.static.kabel-deutschland.de) (88.134.234.51) 14.147 ms 15.304 ms [ip5886ea2f.static.kabel-deutschland.de](ip5886ea2f.static.kabel-deutschland.de) (88.134.234.47) 11.903 ms 4 145.254.3.170 (145.254.3.170) 24.912 ms 145.254.3.168 (145.254.3.168) 16.288 ms 17.370 ms 5 145.254.2.209 (145.254.2.209) 12.672 ms 145.254.2.207 (145.254.2.207) 23.428 ms 145.254.2.209 (145.254.2.209) 16.667 ms 6 [ae17.edge8.frf1.sp.lumen.tech](ae17.edge8.frf1.sp.lumen.tech) (4.68.72.213) 14.044 ms 14.135 ms 14.121 ms 7 * * * 8 [lumen-techn.ear7.amsterdam1.level3.net](lumen-techn.ear7.amsterdam1.level3.net) (212.133.96.222) 35.664 ms 19.388 ms 20.910 ms


brody
EMPLOYEE

10 months ago

where is the service itself located?


dome
PROOP

10 months ago

amsterdam (metal)


dome
PROOP

10 months ago

It only occurs when using this:

1355653192041627600


dome
PROOP

10 months ago

Do u need any more information?


dome
PROOP

10 months ago

Domain is using Cloudflare, it also detects the Cloudflare proxy


brody
EMPLOYEE

10 months ago

try turning the Cloudflare proxy off?


dome
PROOP

10 months ago

doesnt matter, seems still pretty slow


dome
PROOP

10 months ago

when using the metal anycast edge network it seems that it routes through the US, when using it without it routes through amsterdam


dome
PROOP

10 months ago

im not a networking pro but that seems off for me


brody
EMPLOYEE

10 months ago

cc @Phineas - more anycast shenanigans


phin
EMPLOYEE

10 months ago

this traceroute and header is correct


phin
EMPLOYEE

10 months ago

are you proxying your railway deployment via cloudflare by any chance?


phin
EMPLOYEE

10 months ago

your route to the metal edge network is correct, so there must be something in front of your deployment that is messing with routing


phin
EMPLOYEE

10 months ago

there is currently a known issue with the cloudflare proxy that we're working on


dome
PROOP

10 months ago

yes im using the cloudflare proxy. But even after disabling the proxy (switching the cloud off) and only let cf handle the dns it remains slow


dome
PROOP

10 months ago

idk if something was cached


phin
EMPLOYEE

10 months ago

When you disable the Cloudflare proxy it changes DNS so please give a few minutes for it to propagate


dome
PROOP

10 months ago

yeah I did, I alsp checked if the changes applied


phin
EMPLOYEE

10 months ago

If you’re no longer seeing server: cloudflare in your responses that’s how you’ll know


dome
PROOP

10 months ago

also*


dome
PROOP

10 months ago

yeah I saw that on other posts after posting my issue


dome
PROOP

10 months ago

lemme know if u need something to be tested, thank u for ur support


phin
EMPLOYEE

10 months ago

Please show me the response headers of a slow request if the issue persists


dome
PROOP

10 months ago

Will do, I will test it later


dome
PROOP

10 months ago

Okay I tested it again, Indeed with the proxy turned off and waiting a little bit its fast again.


Loading...