#My US West 1 App is stuck with Netherlands IP?

39 messages · Page 1 of 1 (latest)

vast sparrow
#

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.

plucky finchBOT
#

Project ID: e83f98ee-a559-424e-ab2e-ce343f725cee

vast sparrow
#

e83f98ee-a559-424e-ab2e-ce343f725cee

#

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

foggy comet
#

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

vast sparrow
#

I am not on a VPN, no

vast sparrow
#

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.

#

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

foggy comet
#

do you have the edge proxy enabled?

vast sparrow
#

I do yeah

foggy comet
#

can you send the domain?

vast sparrow
#

For both

#

atri.dad

#

Just the root domain

#

The one that works fine is pollo.atri.dad

foggy comet
#

for whatever service is being routed via the netherlands

vast sparrow
#

Ahhh

vast sparrow
foggy comet
#

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

vast sparrow
#

Huh

#

It’s weird too because

#

Redeploying other projects of mine work fine

#

This one is stubborn

#

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

foggy comet
#

what region is the actual service in though

vast sparrow
#

US west

foggy comet
#

how have you verified that

vast sparrow
#

I just assumed off this

#

That it should deploy there

#

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

foggy comet
#

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

#

its strange that its hitting the netherlands proxy though

vast sparrow
#

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

#

More likely the latter

foggy comet
#

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

vast sparrow
#

Ohhhhh

#

That’ll do it…

foggy comet
#

indeed it will