My US West 1 App is stuck with Netherlands IP?

2 years ago

I have an app deployed on the Hobby plan and notice HUGE latency issues here in central Canada. When I check, it gets an IP from the Netherlands when I shouldn't have anything hosted there???

I tried deleting the project and deploying the repo again, with the same results. Am I doing something wrong here? This is the only one of my projects doing this.

39 Replies

2 years ago

e83f98ee-a559-424e-ab2e-ce343f725cee


2 years ago

Should be closer to 30-50ms for what im doing

1248718707388059600


2 years ago

it's strange that you are hitting the Netherlands edge proxy, are you perhaps on a VPN?


2 years ago

I am not on a VPN, no


2 years ago

Same issue still. So one project resolves to US while the other resolves to Netherlands while I am querying from the same machine, back to back, without a VPN, while in Canada.


2 years ago

Remade the project: 1323c37e-445d-4f99-81a8-086cbc0c7302


2 years ago

do you have the edge proxy enabled?


2 years ago

I do yeah


2 years ago

can you send the domain?


2 years ago

For both



2 years ago

Just the root domain


2 years ago

The one that works fine is pollo.atri.dad


2 years ago

for whatever service is being routed via the netherlands


2 years ago

Ahhh


2 years ago

This one then


2 years ago

im in ontario canada and im getting that ip in the Netherlands too


2 years ago

Huh


2 years ago

It’s weird too because


2 years ago

Redeploying other projects of mine work fine


2 years ago

This one is stubborn


2 years ago

And I’m not sure if it’s the project, domain, or something else


2 years ago

what region is the actual service in though


2 years ago

US west


2 years ago

how have you verified that


2 years ago

1252105200907456500


2 years ago

I just assumed off this


2 years ago

That it should deploy there


2 years ago

Whether or not that’s actually the case, I don’t know anymore lol


2 years ago

even so, your request routes through edge proxies, so the ip you resolve from the domain is not the ip of the service itself


2 years ago

its strange that its hitting the netherlands proxy though


2 years ago

Yeah absolutely. I guess I’m curious if it’s a deploy issue or a routing issue


2 years ago

More likely the latter


2 years ago

how are you checking that its netherlands?


2 years ago

show me your dns settings please


2 years ago

you use njalla, they are based in finland, they dont support root level cnames, they set your domain to the ip it resolved to in finland, that would be the edge proxy in the netherlands, you need to use nameservers that do support root level cnames properly like cloudflare


2 years ago

Ohhhhh


2 years ago

That’ll do it…


2 years ago

indeed it will


Loading...