Facebook showing China login when using Warp from San Francisco?

Zero Trust 1.1.1.1
1

hitting facebook.comn via Warp gives you a login location of Beijing CN (and CN langset in incognito), without warp you get the correct location of SF, CA. Is Facebook’s GeoIP database off? Login alert emails from FB show Beijing.

Traceroute doesn’t show this but usually GeoIP databases aren’t inaccurate by country and region (eg ARIN vs APNIC).

facebookCN
facebookCN1089×892 129 KB 

$traceroute to facebook.com (157.240.3.35), 64 hops max, 52 byte packets
 1  console.gl-inet.com (192.168.8.1)  7.901 ms  1.381 ms  1.235 ms
 2  172.16.0.1 (172.16.0.1)  36.439 ms  35.506 ms  33.276 ms
 3  8.45.42.1 (8.45.42.1)  33.283 ms  33.457 ms  33.879 ms
 4  172.68.188.125 (172.68.188.125)  61.434 ms
    198.41.140.84 (198.41.140.84)  60.526 ms  75.041 ms
 5  108.162.243.66 (108.162.243.66)  70.920 ms  70.603 ms  69.338 ms
 6  ae9.pr06.sea1.tfbnw.net (157.240.78.12)  48.283 ms  52.299 ms  49.627 ms
 7  po106.psw01.sea1.tfbnw.net (157.240.48.67)  49.703 ms  53.173 ms  58.592 ms
 8  173.252.67.127 (173.252.67.127)  52.089 ms
    173.252.67.75 (173.252.67.75)  65.390 ms
    157.240.38.199 (157.240.38.199)  51.323 ms
 9  edge-star-mini-shv-01-sea1.facebook.com (157.240.3.35)  59.599 ms  48.710 ms  58.864 ms
$ traceroute facebook.com
traceroute to facebook.com (157.240.3.35), 64 hops max, 52 byte packets
 1  console.gl-inet.com (192.168.8.1)  2.147 ms  1.440 ms  1.552 ms
 2  192.168.48.73 (192.168.48.73)  4.925 ms  3.431 ms  2.382 ms
 3  172.26.96.169 (172.26.96.169)  20.892 ms  16.920 ms  21.091 ms
 4  172.16.126.124 (172.16.126.124)  20.824 ms  26.180 ms
    172.16.126.100 (172.16.126.100)  40.457 ms
 5  12.249.2.49 (12.249.2.49)  31.878 ms  23.471 ms  63.725 ms
 6  12.83.180.82 (12.83.180.82)  47.051 ms  66.236 ms  48.281 ms
 7  sffca22crs.ip.att.net (12.122.3.70)  49.469 ms
    ptdor21crs.ip.att.net (12.122.28.177)  48.585 ms  53.740 ms
 8  st6wa21crs.ip.att.net (12.122.1.77)  55.477 ms  49.016 ms
    ptdor22crs.ip.att.net (12.122.30.142)  51.420 ms
 9  12.122.85.209 (12.122.85.209)  43.646 ms  45.623 ms  49.735 ms
10  12.247.240.62 (12.247.240.62)  45.602 ms
    12.122.85.213 (12.122.85.213)  43.635 ms  41.566 ms
11  12.247.240.62 (12.247.240.62)  43.410 ms  43.170 ms  50.851 ms
12  157.240.38.225 (157.240.38.225)  60.184 ms
    173.252.67.85 (173.252.67.85)  45.054 ms
    157.240.38.221 (157.240.38.221)  64.954 ms
13  157.240.38.245 (157.240.38.245)  52.236 ms
    edge-star-mini-shv-01-sea1.facebook.com (157.240.3.35)  46.504 ms
    173.252.67.7 (173.252.67.7)  44.688 ms
2

Facebook probably has algorithms to determine where an IP is geo-located and they need tuning. It’s entirely possible Warp users n/around Mainland China could egress from a US West coast based Cloudflare colo and their logic sees those logins as eaning the egress IP is in/near a place it isn’t

3

Sounds familiar. I believe Google thought I was in Vietnam instead of California when I used WARP.

4

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.