1536861 - Can't access bit.ly IP addresses from the Paris office

Status: RESOLVED INVALID

(Infrastructure & Operations Graveyard :: NetOps: Office Other, task)

Description

[Julien Wajsberg [:julienw]]

Here is a possible URL you can try: https://perfht.ml/2Y7SjLh

This doesn't work using curl like this:
curl -I https://perfht.ml/2Y7SjLh

IPs for this domain are:
67.199.248.13
67.199.248.12

(same for mzl.la which probably doesn't work).

bit.ly doesn't work either, their IPs are:
67.199.248.10
67.199.248.11

Here are traceroutes from my machine:

$ /usr/sbin/traceroute 67.199.248.10
traceroute to 67.199.248.10 (67.199.248.10), 30 hops max, 60 byte packets
1 gateway (10.243.24.1) 5.655 ms 6.413 ms 6.379 ms
2 10.243.255.1 (10.243.255.1) 5.182 ms 5.176 ms 5.139 ms
3 185.155.181.21 (185.155.181.21) 5.564 ms 5.554 ms 5.514 ms
4 81.31.15.153 (81.31.15.153) 5.748 ms 5.716 ms 5.675 ms
5 ae19-100.cr0-par9.ip4.gtt.net (77.67.95.73) 7.929 ms 7.897 ms 7.856 ms
6 ae-12.r02.parsfr02.fr.bb.gin.ntt.net (46.33.84.54) 6.507 ms 14.383 ms 14.340 ms
7 185.84.18.62 (185.84.18.62) 14.264 ms 14.244 ms 14.389 ms
8 po110.bs-b.sech-par.netarch.akamai.com (23.57.101.245) 14.326 ms po110.bs-a.sech-par.netarch.akamai.com (23.57.101.243) 14.300 ms 14.056 ms
9 * * *
10 ae120.access-a.sech-par.netarch.akamai.com (23.57.101.249) 3.898 ms ae121.access-a.sech-par.netarch.akamai.com (23.57.101.251) 3.866 ms 3.824 ms
11 * * *
12 * * *
13 a209-200-169-112.deploy.static.akamaitechnologies.com (209.200.169.112) 164.855 ms a209-200-173-222.deploy.static.akamaitechnologies.com (209.200.173.222) 159.042 ms *
14 ae5.cbs01.eq01.sjc02.networklayer.com (50.97.17.72) 166.248 ms * *
15 * * ae1.cbs02.cs01.den01.networklayer.com (50.97.17.88) 165.693 ms
16 ae0.cbs02.eq01.chi01.networklayer.com (50.97.17.47) 161.188 ms * *
17 ae1.cbs02.cs01.wdc05.networklayer.com (169.45.19.110) 239.004 ms * *
18 ae3.dar03.wdc04.networklayer.com (169.45.18.239) 205.502 ms * *
19 87.76.3fa9.ip4.static.sl-reverse.com (169.63.118.135) 202.683 ms 8d.76.3fa9.ip4.static.sl-reverse.com (169.63.118.141) 165.991 ms 161.434 ms
20 * * *
21 bit.ly (67.199.248.10) 166.402 ms !X 164.793 ms !X 160.449 ms !X

$ /usr/sbin/traceroute 67.199.248.14
traceroute to 67.199.248.14 (67.199.248.14), 30 hops max, 60 byte packets
1 gateway (10.243.24.1) 5.765 ms 5.682 ms 5.851 ms
2 10.243.255.1 (10.243.255.1) 5.250 ms 5.236 ms 5.201 ms
3 185.155.181.21 (185.155.181.21) 5.173 ms 5.138 ms 6.058 ms
4 81.31.15.153 (81.31.15.153) 6.028 ms 5.990 ms 6.199 ms
5 ae19-100.cr0-par9.ip4.gtt.net (77.67.95.73) 7.826 ms 7.799 ms 7.759 ms
6 ae-12.r02.parsfr02.fr.bb.gin.ntt.net (46.33.84.54) 9.485 ms 4.496 ms 6.690 ms
7 185.84.18.62 (185.84.18.62) 4.363 ms 4.604 ms 6.518 ms
8 po110.bs-a.sech-par.netarch.akamai.com (23.57.101.243) 3.550 ms po110.bs-b.sech-par.netarch.akamai.com (23.57.101.245) 5.474 ms po110.bs-a.sech-par.netarch.akamai.com (23.57.101.243) 5.359 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * *^C

Note this works from a server of mine outside of Mozilla.

Thanks!

Comment 1

[Chris Brentano [:ctb]]

This was discussed in Slack and determined to be an intermittent issue on bit.ly's end. Some attempts to connect with curl were successful for some endpoint IPs, and others were not. Julien reached out to bit.ly on Twitter for comment/support.