Routing issue with router-pit server

It appears that the router-pit NextDNS server is actually located somewhere closer to Phoenix which is across the country. I've noticed some slow browsing on certain websites from my location and it seems to occur when I'm being sent to the router-pit server instead of a closer server. Not sure if this is truly a routing issue or if something odd happened with NextDNS's provider that the Pittsburgh server is actually in Arizona, but the ultra-low routing could use improvement and the router-pit server does just seem to be slow to resolve even at the 80ms ping. If the server was actually in Pittsburgh's area, this may not be an issue.

Diag: https://nextdns.io/diag/0e8839b0-fdb5-11ed-9941-6b87826f0eb6