routing issues to ridewithgps.com

[romper]

Hi,

I cannot connect to the above website from my exetel service unless I use a service like TOR or proxy packets with sshuttle. Additionally isup.me shows the website as available and I can access it via a 3G connection and via an Internode service.

A traceroute shows the following:

root@colossus:~/Documents# tcptraceroute ridewithgps.com
traceroute to ridewithgps.com (216.218.192.36), 30 hops max, 60 byte packets
1 harpy.wamble.net (192.168.7.254) 3.588 ms 3.570 ms 3.552 ms
2 * * *
3 208.8.96.58.static.exetel.com.au (58.96.8.208) 479.575 ms 485.557 ms 492.017 ms
4 193.6.96.58.static.exetel.com.au (58.96.6.193) 492.791 ms 498.000 ms 503.851 ms
5 161.43.102.1 (161.43.102.1) 504.548 ms 504.900 ms 504.904 ms
6 * * *
7 * 59.154.57.72 (59.154.57.72) 320.445 ms 59.154.57.76 (59.154.57.76) 315.362 ms
8 61.88.221.247 (61.88.221.247) 309.114 ms 309.349 ms 61.88.221.249 (61.88.221.249) 304.159 ms
9 203.208.192.241 (203.208.192.241) 631.615 ms 636.554 ms 636.935 ms
10 203.208.172.246 (203.208.172.246) 642.442 ms 203.208.172.238 (203.208.172.238) 593.922 ms 203.208.172.242 (203.208.172.242) 594.185 ms
11 30gigabitethernet2-1.core1.pao1.he.net (198.32.176.20) 593.961 ms 592.940 ms 598.479 ms
12 10gigabitethernet1-4.core1.pdx1.he.net (184.105.222.26) 667.612 ms 684.411 ms 682.957 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

[stevecJ]

Hi,

I cannot connect to the above website from my exetel service unless I use a service like TOR or proxy packets with sshuttle. Additionally isup.me shows the website as available and I can access it via a 3G connection and via an Internode service.

A traceroute shows the following:

root@colossus:~/Documents# tcptraceroute ridewithgps.com
traceroute to ridewithgps.com (216.218.192.36), 30 hops max, 60 byte packets
1 harpy.wamble.net (192.168.7.254) 3.588 ms 3.570 ms 3.552 ms
2 * * *
3 208.8.96.58.static.exetel.com.au (58.96.8.208) 479.575 ms 485.557 ms 492.017 ms
4 193.6.96.58.static.exetel.com.au (58.96.6.193) 492.791 ms 498.000 ms 503.851 ms
5 161.43.102.1 (161.43.102.1) 504.548 ms 504.900 ms 504.904 ms
6 * * *
7 * 59.154.57.72 (59.154.57.72) 320.445 ms 59.154.57.76 (59.154.57.76) 315.362 ms
8 61.88.221.247 (61.88.221.247) 309.114 ms 309.349 ms 61.88.221.249 (61.88.221.249) 304.159 ms
9 203.208.192.241 (203.208.192.241) 631.615 ms 636.554 ms 636.935 ms
10 203.208.172.246 (203.208.172.246) 642.442 ms 203.208.172.238 (203.208.172.238) 593.922 ms 203.208.172.242 (203.208.172.242) 594.185 ms
11 30gigabitethernet2-1.core1.pao1.he.net (198.32.176.20) 593.961 ms 592.940 ms 598.479 ms
12 10gigabitethernet1-4.core1.pdx1.he.net (184.105.222.26) 667.612 ms 684.411 ms 682.957 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Hi,

I will look in to this and drop you an email with the relevant details.

Ticket ID: 7199435

[Dazzled]

I did a TCP traceroute and an ICMP traceroute and got there both times on hop 13 (the site's up in the browser too). Times were better. I'm from a different IP range than you though.

Code: Select all

.........
11  30gigabitethernet2-1.core1.pao1.he.net (198.32.176.20)  196.322 ms  194.885 ms  193.959 ms
12  10gigabitethernet1-4.core1.pdx1.he.net (184.105.222.26)  206.940 ms  206.750 ms  205.163 ms
13  ridewithgps.com (216.218.192.36)  206.833 ms  205.785 ms  205.849 ms

[romper]

The site administrators note that one of their co-hosted customers was hit by a DDOS over the last few days. I am continuing a conversation to see if any bad actors at Exetel might have caused a block of your addresses to be blacklisted and I would appreciate it if you could check connectivity to the site from an address in a range that includes mine, rather than from a totally separate range as appears to have been done.

BTW, I have also noticed that I am getting timeouts to twitter and am wondering if that might be related - basically loading their website in a browser and timeline pulls from my mobile client fail and have to be retried a couple of times before I get the data.