My US West 1 App is stuck with Netherlands IP?
atridadl
HOBBYOP

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

atridadl
HOBBYOP

2 years ago

e83f98ee-a559-424e-ab2e-ce343f725cee


atridadl
HOBBYOP

2 years ago

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

1248718707388059600


brody
EMPLOYEE

2 years ago

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


atridadl
HOBBYOP

2 years ago

I am not on a VPN, no


atridadl
HOBBYOP

a year 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.


atridadl
HOBBYOP

a year ago

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


brody
EMPLOYEE

a year ago

do you have the edge proxy enabled?


atridadl
HOBBYOP

a year ago

I do yeah


brody
EMPLOYEE

a year ago

can you send the domain?


atridadl
HOBBYOP

a year ago

For both



atridadl
HOBBYOP

a year ago

Just the root domain


atridadl
HOBBYOP

a year ago

The one that works fine is pollo.atri.dad


brody
EMPLOYEE

a year ago

for whatever service is being routed via the netherlands


atridadl
HOBBYOP

a year ago

Ahhh


atridadl
HOBBYOP

a year ago

This one then


brody
EMPLOYEE

a year ago

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


atridadl
HOBBYOP

a year ago

Huh


atridadl
HOBBYOP

a year ago

It’s weird too because


atridadl
HOBBYOP

a year ago

Redeploying other projects of mine work fine


atridadl
HOBBYOP

a year ago

This one is stubborn


atridadl
HOBBYOP

a year ago

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


brody
EMPLOYEE

a year ago

what region is the actual service in though


atridadl
HOBBYOP

a year ago

US west


brody
EMPLOYEE

a year ago

how have you verified that


atridadl
HOBBYOP

a year ago

1252105200907456500


atridadl
HOBBYOP

a year ago

I just assumed off this


atridadl
HOBBYOP

a year ago

That it should deploy there


atridadl
HOBBYOP

a year ago

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


brody
EMPLOYEE

a year 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


brody
EMPLOYEE

a year ago

its strange that its hitting the netherlands proxy though


atridadl
HOBBYOP

a year ago

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


atridadl
HOBBYOP

a year ago

More likely the latter


brody
EMPLOYEE

a year ago

how are you checking that its netherlands?


brody
EMPLOYEE

a year ago

show me your dns settings please


brody
EMPLOYEE

a year 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


atridadl
HOBBYOP

a year ago

Ohhhhh


atridadl
HOBBYOP

a year ago

That’ll do it…


brody
EMPLOYEE

a year ago

indeed it will


Loading...