No, they are not lying. GeoLocation often goes by ASN Path. And since QuadraNet's ASN origin is LA, GeoLocation will report LA.
$ traceroute 204.44.122.16
traceroute to 204.44.122.16 (204.44.122.16), 64 hops max, 52 byte packets
1 (192.168.1.1) 1.197 ms 1.042 ms 0.919 ms
2 10.4.128.1 (10.4.128.1) 11.855 ms 10.124 ms 11.936 ms
3 ip72-214-194-57.ga.at.cox.net (72.214.194.57) 10.321 ms 8.881 ms 10.544 ms
4 maribprj01-ae1.0.rd.at.cox.net (68.1.0.41) 23.614 ms 24.847 ms 23.427 ms
5 telx.10ge.atl.bboi.net (198.32.132.12) 25.401 ms 24.025 ms 24.856 ms
6 nsh-ten1-1-atl-ten3-2.bboi.net (64.127.130.58) 30.134 ms 31.146 ms 32.686 ms
7 dal-ten2-1-nsh-ten1-4.bboi.net (64.127.130.50) 40.659 ms 38.926 ms 40.598 ms
8 8011-on-net-cust.bboi.net (64.127.129.118) 44.550 ms 48.939 ms 46.456 ms
9 204.44.122.2.static.quadranet.com (204.44.122.2) 46.985 ms 44.286 ms 44.584 ms
10 204.44.122.16.static.quadranet.com (204.44.122.16) 43.370 ms 45.373 ms 47.437 ms
$ ping 204.44.122.16
PING 204.44.122.16 (204.44.122.16): 56 data bytes
64 bytes from 204.44.122.16: icmp_seq=0 ttl=54 time=46.784 ms
64 bytes from 204.44.122.16: icmp_seq=1 ttl=54 time=46.477 ms
64 bytes from 204.44.122.16: icmp_seq=2 ttl=54 time=46.675 ms
I'm on the East Coast, and this traceroute and ping can't be hitting LA, this is indeed Dallas.
Comments
Yes, it's in Dallas, the ASN points to LA, but the traceroute goes to Dallas.
Who is the provider?
It is in Dallas:
11 165 ms 148 ms 141 ms dal-ten2-1-nsh-ten1-4.bboi.net [64.127.130.50]
12 142 ms 141 ms 141 ms 8011-on-net-cust.bboi.net [64.127.129.118]
QuadraNet have a Dallas location too. IPs may be SWIPed to LA as that's their flagship location.
No, they are not lying. GeoLocation often goes by ASN Path. And since QuadraNet's ASN origin is LA, GeoLocation will report LA.
I'm on the East Coast, and this traceroute and ping can't be hitting LA, this is indeed Dallas.
I'm seeing a 1ms ping from Incero in Dallas, so It's indeed in Dallas.
Bingo :-)
Number one 1 pet peeve
I hate explaining geolocation and will get mad posted if you argue against tracert logic
Provider is WeLoveServer. Not sure what is going on! I failed to understand the Traceroute report
Isn't that clear enough?
The hardware and network are in Dallas. IPs are just registered in LA because that's their flagship location.
If your hosting provider fails to understand a traceroute output,
Re-read it, he said he doesn't understand the traceroute.